Oracle Distributed Systems

Name

DBMS_REPCAT.REPCAT_IMPORT_CHECK

Synopsis

From time to time, you may need to rebuild a master site from an export dump file as either a recovery or maintenance procedure. Because object ID numbers (as seen in SYS.OBJ$.OBJ# and DBA_OBJECTS.OBJECT_ID) change during these rebuilds, Oracle supplies a procedure (REPCAT_IMPORT_CHECK) that you must run immediately after an import of any master site to synchronize the new ID numbers with the data stored in the table SYSTEM.REPCAT$_REPOBJECT. Objects with a status of VALID in REPCAT$_REPOBJECT are not affected.

The specifications differ for Oracle7 and Oracle8 as follows.

Oracle7 specification:

PROCEDURE DBMS_REPCAT.REPCAT_IMPORT_CHECK
   (gname IN VARCHAR2 := '',
    master IN BOOLEAN,
    sname IN VARCHAR2 := '');

Oracle8 specification:

PROCEDURE DBMS_REPCAT.REPCAT_IMPORT_CHECK
   (gname IN VARCHAR2 := '',
    master IN BOOLEAN);

There are no restrictions on calling REPCAT_IMPORT_CHECK.

Call REPCAT_IMPORT_CHECK with sname and master set to NULL (or with no parameters) to validate all replication groups at the site.

Parameters

Parameter Name	Description
gname	Name of the replication group being revalidated
master	Set to TRUE if site is a master, FALSE if it is a snapshot site
sname (Oracle7 only)	Schema name (provided for pre-Oracle 7.3 compatibility)

Exceptions

Exception Name	Number	Description
missingobject	–23308	Object with a status of VALID in REPCAT$_REPOBJECT does not exist.
missingschema	–23306	Schema sname does not exist.
nonmaster	–23312	Master is set to TRUE, but the ...