We ran into an issue where replicate was complaining that it would need "all collumn supplemental logging" for our tables with change data capture.
After fiddling around for a while, wondering why it was not working as we had our primary keys and logging was enabled properly, we contacted the support and the colleague there pointet us to the user guide. We found out that this is normal behaviour for Replicate as soon as the Option: "Insert the missing target record" in Apply Conflicts for "No record found for applying an UPDATE" is set.
It is mentioned in the user guide, but I think a warning in the Logs would be helpful for new users of Replicate, similar to the warning that LOB's are not supported as soon as the option: "Duplicate key when applying INSERT:" is set to "UPDATE the existing target record", for instance.
