Compare needs special consideration when run in a master-master replication environment. In certain setups the trusted source (primary) may have odd numbered key values populated via sequence generator and the secondary may have even numbered key values or vice versa. Running compare on such a setup can result in the removal of rows on secondary with key values that do not match the key values from the primary. This is despite following the guidelines listed in the Reference Guide section titled Using compare config with peer-to-peer replication
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center