Oracle7 Server Distributed Systems Volume II: Replicated Data

Dropping a Replicated Object

This section describes how to drop an object from a replicated object group. This change ultimately affects all master and snapshot sites. Information on adding an object to the replicated object group is described

To drop a replicated object from a replicated object group, call the DROP_MASTER_REPOBJECT procedure in the DBMS_REPCAT package at the master definition site, as shown in the following example:

DBMS_REPCAT.DROP_MASTER_REPOBJECT(
    sname        => 'acct_rec', 
    oname        => 'emp', 
    type         => 'table', 
    drop_objects => FALSE);

In this example, when the procedure is executed, all automatically generated supporting objects, such as triggers and packages, used to replicate EMP will be dropped from each site. Because DROP_OBJECTS is set to FALSE, the default, the EMP table will continue to exist at all of the master sites. You can request that the object and any dependent objects be dropped at all sites by setting DROP_OBJECTS to TRUE.

This change is synchronously broadcast to each master site as described . Because this procedure is then executed asynchronously at each site, the RepCatLog view contains the interim status and any asynchronous error messages generated by the request.

Before dropping a replicated table, be certain that no snapshots depend on this object.

Additional Information: The parameters for the DROP_MASTER_REPOBJECT procedure are described in Table 12 - 123, and the exceptions are listed in Table 12 - 124.