Interpreting the Consistency Report
The consistency report displays information about differences in replicated data within the replicate or replicate set.
Jan 17 2009 15:46:45 ------ Table scan for repl1 start --------
------ Statistics for repl1 ------
Node Rows Extra Missing Mismatch Processed
---------------- --------- --------- --------- --------- ---------
g_serv1 67 0 0 0 0
g_serv2 65 0 2 0 0
WARNING: replicate is not in sync
Jan 17 2009 15:46:50 ------ Table scan for repl1 end ---------
The
missing rows could be in the process of being replicated from g_serv1 to g_serv2. Jan 17 2009 15:46:45 ------ Table scan for repl1 start --------
------ Statistics for repl1 ------
Node Rows Extra Missing Mismatch Processed
---------------- --------- --------- --------- --------- ---------
g_serv1 67 0 0 0 2
g_serv2 65 0 2 0 0
Validation of repaired rows failed.
WARNING: replicate is not in sync
Jan 17 2009 15:46:50 ------ Table scan for repl1 end ---------
The
warning indicates that inconsistencies were discovered. The
report indicates whether the replicate became consistent after the
repair process. In this example, the Validation of repaired
rows failed.
message indicates that the replicate is not
consistent. This might occur because some replicated transactions
were still being replicated. Use the --inprogress option to
extend the validation time.
The verbose form of the consistency report also displays the differing values for each inconsistent row.
For more information about the contents of the consistency report, see cdr check replicate.