Diagnosing Problems with Administrative Requests

When you administer a replication environment, you should monitor the administrative requests to make sure that everything is running smoothly. While monitoring your system, you might find that there are problems related to administrative requests. The following list includes some troubleshooting information for administrative request problems:

• If administrative requests are backed up at a site, but are not backed up because of an error condition, ensure that there is not a problem with the local job running DBMS_REPCAT.DO_DEFERRED_REPCAT_ADMIN.

  See Diagnosing Problems with Jobs for more information about diagnosing job queue problems.

  Note: Additionally, check the LOG_USER column in the DBA_JOBS view to ensure that the replication job is being run on behalf of the replication administrator (typically REPADMIN user). Check the USERID column of the DBA_REPCATLOG view to ensure that the replication administrator was the user that submitted the request. DBMS_REPCAT.DO_DEFERRED_REPCAT_ADMIN only performs those administrative requests submitted by the user that calls this procedure.

• Ensure the relevant databases are running and communication is possible.

• Ensure that the necessary private database links are available for the replication environment, and that the user designated in the CONNECT TO clause (generally the replication administrator) has the necessary privileges. If you used the Replication Setup Wizard to set up your sites, you should not have any problems.