Monitoring Conflict Resolution with DBMS_REPCAT

Oracle can audit successful calls to your conflict resolution handlers so that you have insight into the frequency and nature of the conflicts that occur.

About Monitoring

If you enable the auditing of successful calls to your conflict resolution handlers, you can review this information in the DBA_REPRESOLUTION_STATISTICS data dictionary view.

Use the following programs to enable, disable, and purge these statistics:

DBMS_REPCAT.REGISTER_STATISTICS
DBMS_REPCAT.CANCEL_STATISTICS
DBMS_REPCAT.PURGE_STATISTICS

The DBMS_REPCAT.REGISTER_STATISTICS procedure

The REGISTER_STATISTICS procedure enables the collection of data about the successful resolution of update, uniqueness, and delete conflicts. This information is visible in the DBA_REPRESOLUTION_STATISTICS data dictionary view. Here is the specification for this procedure:

PROCEDURE DBMS_REPCAT.REGISTER_STATISTICS
   (sname IN VARCHAR2,
    oname IN VARCHAR2);

Parameters are summarized in the following table.

Name

Description

sname

Name of the schema to which the replicated table belongs

oname

Name of the replicated table

There are no restrictions on calling REGISTER_STATISTICS.

Exceptions

The REGISTER_STATISTICS procedure may raise the following exceptions:

Name

Number

Description

missingobject

-23308

Table oname does not exist

missingschema

-23306

Schema sname does not exist

Example

This call enables the gathering of conflict resolution statistics for the products table:

BEGIN DBMS_REPCAT.REGISTER_STATISTICS ...

Get Oracle Built-in Packages now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.