Re: How to stop replication absolutely

sealo wrote:
> Hello,
> I need to modify the record in one oracle. And this db is running
> replication with another.
> Then, I do the general routine of stop replication like follows.
> 1. Stop the PUSH job to both side
> 2. Execute DBMS_REPUTIL.REPLICATION_OFF at local side
> 3. Truncate table system.def$_aqcall and system.def\\$_aqerror;
>
> And, the replication was stopped. Then I add some records into the
> table locally, and the mate side don't change.
>
> The issue is , when I resume the replication
> 1. Start PUSH job to the both side
> 2. Execute DBMS_REPUTIL.REPLICATION_ON at local side
>
> The recent inserted record are replicated to the mate again! It's not
> my expectation.

-snip-

General routine?? Wait! This is a routine which you invented. I've never
seen anyone try to shoot themselves in the foot in such a way.

• Stop the PUSH job - This will just stop the push job. Its not stopping replication. There is rarely ever need to stop the push job, unless you are trying to sync to schemas which have gone horribly out of sync.
• execute dbms_reputil.replication_off ... this turns off replication only in the session that calls it!
• Truncate table system.def$_aqcall and system.def$_aqerror ... Why?? This will cause replication entries to vanish. By running this, you potentially are causing tables to go out of sync.

Couple of comments on what you are trying to do: * If you change a record only on one table (assuming you are not trying   a sync here), then you are essentially causing the table being   replicated to go out of sync!
* All you need to do to disable replication for a certain session is to   run exec dbms_reputil.replication_off before you run your update   in the same session.

Is there something else you are trying to do here .. which you did not bother to explain?

Anurag Received on Wed Jan 10 2007 - 09:51:08 CST