Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Oracle MM replication -- unable to drop non-master-def replication

Oracle MM replication -- unable to drop non-master-def replication

From: jay dee <jaydee350_at_yahoo.com>
Date: 15 Aug 2002 19:07:12 -0700
Message-ID: <3c179fbf.0208151807.4463311e@posting.google.com>


New to MM replication. I have two sites, test1 and test2, test1 is the master def site. I had previously defined and gotten replication working between these nodes. However I've managed to do something so that now when I try to remove replication support from both sites, only the master def is affected. That is, the replication group, etc, is properly deleted from the master def site, and the enterprise manager says there no replication configured at that node. But enterprise manager still shows the replication group, etc, in the other master site.

Rerunning the setup scripts (from the master def site of course) does not restablish communication between the sites. It fails on the step that attempts to create/recreate the master site (below), saying the master already exists

EXECUTE DBMS_REPCAT.ADD_MASTER_DATABASE( -  gname => 'REPGRP', -
 master => 'TEST2', -
 use_existing_objects => true, -
 copy_rows => false, -
 comment => 'TEST2 added on ' || sysdate, -  propagation_mode => 'ASYNCHRONOUS' -
);

Anyone know how to delete the MM replication environment at a non-master-def site when the normal dbms_repcat.drop_master_repgroup() doesn't work? Any hints as to why this may have occurred?

Thanks

JD Received on Thu Aug 15 2002 - 21:07:12 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US