Users determine that the row count differs across source and target tables but “show sync” shows that the table is in sync. This appears to be counterintuitive.
If the counts do not match across source and target table, though the "show sync" does not show that the table is out of sync, then there are 2 possibilities:
1. The table is in sync as there is data in the queue for that table that has yet to post to the target and once that posts to the target table, the counts will match.
2. The target table is out of sync. SharePlex only reports out of sync when it runs into one. So it is just that SharePlex has not yet run into the out of sync that exist on target table and hence it is not reporting them in "show sync".
Run a Compare to determine if the table is truly out of sync and then run another repair to fix that if the Compare shows that the table is out of sync. You can also run just a repair to fix out of sync, if any, on that table if you do not wish to ascertain the state of the sync of the table first. This is usually done if the user wants to save time and does not wish to undergo a compare first and then repair. For both compare and repair may take a similar amount of time and just running a repair would fix the problem and save the time by half.