HOW DO I KEEP A USER-DEFINED TRIGGER FROM FIRING DURING REPLICATION (Doc ID 1058873.6)

Last updated on FEBRUARY 06, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 7.0.16.0 and later
Information in this document applies to any platform.

Symptoms

How do I keep a user-defined trigger from firing during propagation.

Changes

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
T2 AGAIN?

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms