Saturday 28 September 2013

GGS_Heartbit enable trigger on replicator when using DBOPTIONS SUPPRESSTRIGGER

Below procedure on DB level on replication side can make trigger fires on below two table which is important  for Golden Gate monitoring when we have disable trigger on DB side
DBMS_DDL.SET_TRIGGER_FIRING_PROPERTY('GGS_ADMIN','GGS_HEARTBEAT','FALSE')
DBMS_DDL.SET_TRIGGER_FIRING_PROPERTY('GGS_ADMIN','GGS_HEARTBEAT_HISTORY','FALSE')
Posted by
at
Labels: ,

1 comment:

  1. Rainbow2 July 2018 at 10:21

    Hi Dilip,
    I am assuming GGS_ADMIN is the GGS_ADMIN is the owner name of the trigger and GGS_HEARTBEAT is the trigger , Is that correct ?

    we have situation like when we are replicating the data from Golden gate what ever the trigger we have written is not working when we are running in the sql developer it is working fine ... i am hoping DBMS_DDL.SET_TRIGGER_FIRING_PROPERTY('GGS_ADMIN','GGS_HEARTBEAT_HISTORY','FALSE') will work for me .
    Plase advice.
    Regards,
    Sri

    ReplyDelete

Subscribe to: Post Comments (Atom)