Name
DBMS_REPCAT.WAIT_MASTER_LOG
Synopsis
You can use the WAIT_MASTER_LOG procedure to ascertain whether the changes in the repcatlog queue have reached the master sites. However, you might find it more convenient to query the DBA_REPCATLOG data dictionary view directly. This procedure has an OUT parameter, true_count, which the procedure populates with the number of outstanding (incomplete) tasks. The specifications differ for Oracle7 and Oracle8 as follows.
Oracle7 specification:
PROCEDURE DBMS_REPCAT.WAIT_MASTER_LOG
(gname IN VARCHAR2 := '',
record_count IN NATURAL,
timeout IN NATURAL,
true_count OUT NATURAL,
sname IN VARCHAR2 := '');Oracle8 specification:
PROCEDUREDBMS_REPCAT.WAIT_MASTER_LOG
(gname IN VARCHAR2,
record_count IN NATURAL,
timeout IN NATURAL,
true_count OUT NATURAL);There are no restrictions on calling WAIT_MASTER_LOG.
Parameters
Parameter Name | Description |
|---|---|
gname | Name of the replication group |
record_count | Number of records to allow to be entered in the DBA_REPCATLOG data dictionary view before returning |
timeout | Number of seconds to wait before returning |
true_count | Output variable containing the actual number of incomplete activities queued in the DBA_REPCATLOG data dictionary view |
sname (Oracle7 only) | Schema name (provided for pre-Oracle 7.3 compatibility) |
Exceptions
Exception Name | Number | Description |
|---|---|---|
nonmaster | –23312 | Calling site is not a master site. |