DBOPTIONS SUPPRESSTRIGGERS for delete cascade constraint on the target side (REPLICAT) in 18.104.22.168 is missing.
Ct was using OGG ver 10.4 initially for replicating from 22.214.171.124 on Sun Solaris to 126.96.36.199 on AIX.
Ct ran into issues as they had 232 tables with 250 DELETE CASCADE constraints while replicating delete records.
We gave the recommendation of disabling the constraint which obviously worked but the ct does not want
to disable the constraint and involves lot of manual work.
In working thru’ the issues with GG support, it was mentioned that OGG ver 11.1. would have a parameter
that was to be set in the REPLICAT which would fix this issue.
In reading thru’ the Release notes
the parameter SUPPRESSTRIGGERS is not available for 11gR1, 188.8.131.52.
I was adivsed to open an SR with GG support to check if there will be an additional build
on top of 11.1.1 so that this parameter becomes available for 11gR1. Otherwise the ct will not be
very happy as initially, we were told the ct that the parameter will be available for 184.108.40.206, but it didnt make it as per the doc.
If we can build the same for 220.127.116.11 it will go a long way in maintaining this high profile ct.
check the OGG v11 guides and ensure that you are looking for SUPPRESSTRIGGERS or DEFERREFCONST.
Valid for Replicat for Oracle. Prevents triggers from firing on target objects that are configured for replication with Oracle GoldenGate. You can use this parameter for Oracle 10.2.0.5 and later patches, and for Oracle 18.104.22.168 and later, instead of manually
disabling the triggers.
Valid for Replicat for Oracle. Delays referential integrity constraint checking and enforcement by the database until the Replicat transaction is committed. You can use this parameter instead of disabling the constraints on the target tables if the database is
Oracle version 22.214.171.124 and later.
When coming to SUPPRESSTRIGGERS, we have some packages added to 10.2.0.5 or 126.96.36.199 and above. Those packages are needed for this to work.
For 10.2.0.5, we need to use dbms_streams_auth.grant_admin_privilege and For 188.8.131.52, we use dbms_goldengate_auth.grant_admin_privilege.