How to proactively look for Out Of Sync (OOS) for all tables in replication.
The SharePlex Out-of-Sync (OOS) detection only reports an OOS at the moment it is encountered by Post (or compare/repair utilities).
SharePlex does not maintain a historical record of OOS unless an operation explicitly detects the OOS.
show sync only displays OOS conditions that have already been detected by SharePlex.
If the Post process has not yet processed the row or operation that produces the mismatch, then no OOS is raised, and show sync appears clean.
This means there can be hidden OOS on the Target that SharePlex won't detect unless Post reaches that specific point in the replication stream.
A proactive way to guarantee that all tables involved in replication are consistently checked for OOS is to generate one or more SharePlex configuration files that explicitly list every table being replicated.
You can achieve this in two ways:
1. Single Comprehensive Configuration File
Create one config file that includes all tables currently in replication.
2. Multiple Config Files for Large Environments
If replication consists of a very large number of tables, consider splitting them into multiple config files.
Each config file should contain a manageable subset.
Ensure the subsets collectively include every replicating table.
Then issue the command “compare using <config file>” or “compare using <config file> quickcheck” on Source, to identify the tables that are OOS.
On Source:
sp_ctrl> compare using <config file>
or
sp_ctrl> compare using <config file> quickcheck
Using the quickcheck option causes the compare process to stop as soon as the first OOS row is found.
This avoids scanning the entire table unnecessarily and can significantly reduce runtime when large discrepancies exist early in the table.
Note:
The config file used for compare/repair does not need to be the active configuration.
You may define standalone config files specifically for compare/repair tasks.
