Name
DBMS_REPCAT.DROP_MASTER_REPGROUP
Synopsis
The DROP_MASTER_REPGROUP procedure drops one or more replication groups (and optionally all of its contents) at the master definition site. Changes do not take effect until GENERATE_REPLICATION_SUPPORT is called.
Before calling DROP_MASTER_REPGROUP, call REMOVE_MASTER_DATABASES from the master definition site to remove all masters for which you plan to drop the group and that do not contain any other replication groups. In addition, you can avoid the fullqueue error by quiescing the replication group before attempting to drop the replication group.
PROCEDURE DBMS_REPCAT.DROP_MASTER_REPGROUP (gname IN VARCHAR2, drop_contents IN BOOLEAN := FALSE, all_sites IN BOOLEAN := FALSE);
Parameters
Parameter Name | Description |
---|---|
all_sites | If TRUE and call is the master definition site, then drop the replication group from all sites in the environment. |
drop_contents | If TRUE, drop the objects in the replication group as well as the group itself. |
gname | Name of the new replication group. |
Exceptions
Exception Name | Number | Description |
---|---|---|
commfailure | –23317 | Unable to communicate with all masters, and all_sites is TRUE. |
fullqueue | –23353 | Outstanding transactions queued for replication group gname. |
missingrepgroup | –23373 | gname is not specified correctly. |
nonmaster | –23313 | Calling site is not a master site. |
nonmasterdef | –23312 | Calling site is not a master definition site, and all_sites is TRUE. |
Restrictions
You must be connected to the replication administrator account (typically REPADMIN) to call ...
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.