The results fired by a trigger at the primary database will normally be replicated to the standby database. In addition, the transaction that caused the trigger to fire will be replicated. This may result in duplicate information from both the trigger replicating to the standby database and the trigger firing at the standby database. To avoid potential duplication at the standby database, Replication Server attempts to set the dsi_keep_triggers configuration parameter to off at the standby database. However, Oracle does not support disabling trigger execution at the session or connection level.
Workaround: At the standby database, disable triggers that update tables while replication to the standby database is active.
