Name
DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY
Synopsis
You may have noticed that many of the DBMS_REPCAT procedures require you to quiesce the environment before using them. Quiescence, as it is called, accomplishes two things:
It applies all outstanding DML for the replication group at all master sites.
It prevents any additional DML on any of the replicated objects at all master sites.
In other words, quiescence ensures that all sites are up to date and forces the replicated environment to stand still.
Do not attempt to quiesce an environment that has unresolved errors or any other serious problems. If you cannot complete outstanding transactions, you will not be able to quiesce the environment.
The SUSPEND_MASTER_ACTIVITY procedure quiesces an environment. It propagates all deferred transactions and RPCs and then disables all replication activity. Although this procedure allows you to specify a replication group in Version 7.x databases, all replication groups whose master definition site is the invoking site are quiesced. Group-level quiescence is available with Oracle8. This call can take some time to complete if you have many master sites or many outstanding transactions. You can monitor the progress by querying the status field in the DBA_REPCATLOG data dictionary view.
The specifications differ for Oracle7 and Oracle8 as follows.
Oracle7 specification:
PROCEDURE DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY (gname IN VARCHAR2 := '', execute_as_user IN BOOLEAN := FALSE, sname IN VARCHAR2 := ''); ...
Get Oracle Distributed Systems now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
