You can now control trigger firing at the session level or connection level, each time a PL/SQL command is executed against an Oracle replicate database. Controlling trigger execution at the replicate database eliminates duplication and inaccuracy that were caused in earlier versions due to the absence of trigger control at the replicate database.
The RS_TRIGGER_CONTROL package supports this feature and is automatically installed when a connection to the replicate Oracle database is created through connection profiles. The rs_triggers_reset system function has also been modified to support this feature, and you can now set the dsi_keep _triggers connection parameter to off to disable triggers in Oracle. Re-create every trigger needed to be controlled at the replicate database, adding the trigger control statement at the beginning of your trigger action.
Oracle 10g and 11g
See “Settings for trigger firing,” in Chapter 10, “Oracle Replicate Data Server Issues” in the Replication Server Heterogeneous Replication Guide.
