Oracle7 Server Distributed Systems Volume II: Replicated Data

Contents Index Home Previous Next

DBMS_REPCAT.DROP_MASTER_REPGROUP

Purpose

To drop a replicated object group from your current site. To drop the replicated object group from all master sites, including the master definition site, you can call this procedure at the master definition site, and set the final argument to TRUE. For additional information, refer to [*].

Syntax

The parameters for the DROP_MASTER_REPGROUP procedure are described in Table 12 - 121, and the exceptions are listed in Table 12 - 122. The syntax for this procedure is shown below:

DBMS_REPCAT.DROP_MASTER_REPGROUP(
			gname		IN	VARCHAR2, 
			drop_contents	IN	BOOLEAN := FALSE, 
			all_sites	IN	BOOLEAN := FALSE)

Parameter Description
gname The name of the replicated object group that you want to drop from the current master site.
drop_contents By default, when you drop the object group at a master site, all of the objects remain in the schema. They simply are no longer replicated; that is, the replicated objects in the object group no longer send changes to, or receive changes from, other master sites. If you set this argument to TRUE, any replicated objects in the replicated object group are dropped from their associated schemas.
all_sites If ALL_SITES is TRUE and the invocation site is the master definition site, the procedure synchronously multicasts the request to all masters. In this case, execution is immediate at the master definition site and may be deferred at all other master sites.
Table 12 - 121. Parameters for DROP_MASTER_REPGROUP

Exception Description
nonmaster The invocation site is not a master site.
nonmasterdef The invocation site is not the master definition site and ALL_SITES is TRUE.
commfailure At least one master site is not accessible and ALL_SITES is TRUE.
fullqueue The deferred RPC queue has entries for the repschema
Table 12 - 122. Exceptions for DROP_MASTER_REPGROUP


Contents Index Home Previous Next