HOW DO I KEEP A USER-DEFINED TRIGGER FROM FIRING DURING REPLICATION
Last updated on FEBRUARY 06, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
How do I keep a user-defined trigger from firing during propagation.
You have a user-defined trigger on a replicated table, T1. During a
local transaction, this trigger will fire to populate another
replicated table, T2. Both transactions will be pushed to their
corresponding tables on the remote site. But when the transaction
to T1 is pushed, how do you keep the trigger from firing and populating
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms