Re: Replicating triggers and procedures

If you are implementing row-based replication then in most cases you would alter the triggers to include code so that the triggers don't fire when data is being inserted via replication. However if the trigger writes to a table which is not being replicated, you might not want the code which prevents its code execution.

However, in short, you would be looking at the case 1)

I'm assuming that the procedures you talk about are ones associated with the trigger (i.e. you are not talking about procedural based replication).

Anurag

"Ralf Fernan" <ralphfernan.nospam_at_yahoo.com> wrote in message news:GUV2a.35176$rq4.2667406_at_bgtnsc05-news.ops.worldnet.att.net...
> Is it necessary to include the triggers or stored procedures in the
> replication group, if the data structures (tables) they affect are in that
> replication group?
>
> So, in a (multimaster) replication environment, if the DB application
> executes a trigger or procedure which results in data modifications on one
> master site, will Oracle propogate these changes to the other master sites,
> if 1) the affected tables are included in the replication group, but the
> affecting triggers and procedures are not; or, 2) the affected tables, and
> affecting triggers and procedures are included in the replication group.
>
>
Received on Thu Feb 13 2003 - 18:29:47 CST