Oracle7 Server Distributed Systems Volume II: Replicated Data
Auditing the Successful Resolution of Conflicts
Whenever the symmetric replication facility detects and successfully resolves an update, delete, or uniqueness conflict, you can view information about what method was used to resolve the conflict by querying the RepResolution_Statistics view. This view is only updated if you have chosen to turn on conflict resolution statistics gathering for the table involved in the conflict.
Gathering Conflict Resolution Statistics
Use the REGISTER_STATISTICS procedure in the DBMS_REPCAT package to collect information about the successful resolution of update, delete, and uniqueness conflicts for a table. The following example gathers statistics for the EMP table in the ACCT_REC schema:
DBMS_REPCAT.REGISTER_STATISTICS( sname => 'acct_rec',
oname => 'emp');
Additional Information: The parameters for the REGISTER_STATISTICS procedure are described in Table 12 - 157, and the exceptions are listed in Table 12 - 158
Viewing Conflict Resolution Statistics
After you call REGISTER_STATISTICS for a table, each conflict that is successfully resolved for that table is logged in the RepResolution_Statistics view. Information about unresolved conflicts is always logged to the DefError view, whether the object is registered or not.
Additional Information: The RepResolution_Statistics view is described in Table 13 - 18 and the DefError view is described in Table 13 - 23.
Canceling Conflict Resolution Statistics Gathering
Use the CANCEL_STATISTICS procedure in the DBMS_REPCAT package if you no longer want to collect information about the successful resolution of update, delete, and uniqueness conflicts for a table. The following example cancels statistics gathering on the EMP table in the ACCT_REC schema:
DBMS_REPCAT.CANCEL_STATISTICS( sname => 'acct_rec',
oname => 'emp');
Additional Information: The parameters for the CANCEL_STATISTICS procedure are described in Table 12 - 86, and the exceptions are listed in Table 12 - 87.
Removing Statistics Information
If you registered a table to log information about the successful resolution of update, delete, and uniqueness conflicts, you can remove this information from the RepResolution_Statistics view by calling the PURGE_STATISTICS procedure in the DBMS_REPCAT package.
The following example purges the statistics gathered about conflicts resolved due to inserts, updates, and deletes on the EMP table between January 1 and March 31:
DBMS_REPCAT.PURGE_STATISTICS( sname => 'acct_rec',
oname => 'emp',
start_date => '01-JAN-95',
end_date => '31-MAR-95);
Additional Information: The parameters for the PURGE_STATISTICS procedure are described in Table 12 - 153, and the exceptions are listed in Table 12 - 154.