For a logical replicate database, you can drop a subscription using the drop subscription command with the with purge option. A drop subscription marker follows the dematerialization data from the DSI queue to the active database, and then travels to the standby database. After the marker has been received at both databases, subscription data is deleted from both databases.
You can execute the switch active command at the replicate Replication Server while you drop a subscription using the drop subscription command with the with purge option. Replication Server suspends DSI threads and temporarily suspends dematerialization. After switch active completes, the DSI threads are resumed and dematerialization restarts.
Dropping a subscription using the with purge option for a logical replicate database may lead to a suspect drop subscription if:
The subscription is materializing in the active database, and
You switch the active and standby databases, then
You drop the subscription while it is materializing in the new active database.
Dematerialization restarts and proceeds normally for the new active database, but the new standby (old active) database may retain some subscription data that is not purged. To resolve the discrepancy, you can reconcile the active and the standby database using the rs_subcmp program, or you can drop and re-create the standby database.
For example, you may see a warning message like this when you try to execute drop subscription:
W. 95/10/02 20:59:15. WARNING #28171 DSI(111 SYDNEY_DS.pubs2) - /sub_dsi.c(1231) REPLICATE RS: Dropped subscription publishers_sub for replication definition publishers_rep at standby replicate for <SYDNEY_DS.pubs2> before it completed materialization at the Active Replicate. Standby replicate may have some subscription data rows left in the database
