In the following example, this procedure waits until either 120 seconds have passed or there are at most 5 records in the local RepCatLog view that represent administrative activities for the ACCT replicated object group that have not completed before returning the actual number of incomplete activities.
Activities that have completed with or without an error are not considered. This allows you to determine if changes that were asynchronously propagated to a master site have been applied.
incomplete NATURAL; DBMS_REPCAT.WAIT_MASTER_LOG( gname => 'acct', record_count => 5, timeout => 120, true_count => incomplete);
If there are N master sites and one master definition site for a replicated object group, most asynchronous administrative requests eventually create N+1 log records at the master definition site and one log record at each master. ADD_MASTER_DATABASE is an exception, and may create a log record at the master definition site and a log record at the new master site for each object in the replicated object group.
Additional Information: The parameters for the WAIT_MASTER_LOG procedure are described in Table 12 - 173, and the exceptions are listed in Table 12 - 174.