There are few out of sync introduced on target on a table that is huge. There are several scenario that would help running compare on specific rowid:
1. Some rows are lost when discarding messages from queue to resolve replication problems.
2. On routine monitoring for out of sync on target table by running "show sync", a small # of out of sync are observed on certain table(s)
The table(s) affected is/are huge so running compare without options may not work as it would time out. Compare needs to be run on limited # of rows. This works in our favor as we can use the "where" clause in compare to limit the # of rows to be compared, thereby avoiding compare errors. Remember only one compare can be issued per rowid.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.