How to monitor the status of
replication
The repcheck_mdef.sql
file is created along with the rest of the replication setup scripts
in order to provide a means of monitoring the replication process. The
repcheck.sql file creates a PL/SQL procedure named replication_check
which is owned by the repadmin account on the Master Def site. The repcheck_no_mdef.sql
file is an alternate version of the replication_check procedure which
is designed to be run at a non-Master Definition site. This site requires
manually created database links to each of the master sites.
Run the repcheck_mdef.sql file via the repadmin account
at the Master Def site in order to install the replication_check plsql
procedure. Schedule the automatic execution of this job on at least
a daily basis via a job submitted thru the OEM Console. This procedure
needs to run on an Oracle 8.1.6 or higher version database in order
to send email directory from the database to the DBA if problems are
found with the replication process.
The replication_check procedure sends an email message
to each of the email addresses listed in the DBA Email field on the
General folder tab of the graphical interface. The replication status
email is only sent if the number of records within each table differ
by more than 2 records. Additionally, if the number of records in the
deferror or deftran queues exceed 2 records, the email is also sent.
The v_max_limit PL/SQL constant may be changed by the
DBA to change the number of records which can differ between the master
sites to trigger the sending of the status email.
A complete status report is generated including:
A listing of every replicated table, at every master site, along with
the number of records contained within the table.
A listing of the number of records within the following
replication related views at each master site is provided:
deferror
deftrandest
deftran
dba_2pc_pending
dba_2pc_neighbors
