Replication Server supports disabling trigger execution for Oracle at the session or connection level. You can control trigger firing each time Replication Server executes PL/SQL commands against the replicate database. Controlling trigger execution at the replicate database eliminates data duplication and data inaccuracy errors that were caused by the absence of trigger control at the replicate database side.
To control trigger firing, RS_TRIGGER_CONTROL package has been provided, which is automatically installed when a connection to the replicate Oracle database is created through connection profiles. For every trigger to be controlled at the replicate database, re-create the trigger and add the trigger control statement at the beginning of your trigger action.
Set the connection parameter dsi_keep_triggers to off so that Replication Server sets the RS_TRIGGERS_CONTROL enable flag when connecting to the replicate database.
Add the trigger control PL/SQL code to the first line of your trigger action:
if RS_TRIGGER_CONTROL.IS_ENABLED then return;end if;
This indicates that a trigger is fired by Replication Server and prevents the trigger from executing the actual application logic.
See the Replication Server Reference Manual.
