GoldenGate – Support for parameter SUPPRESSTRIGGERS is not available in the RDBMS version you are using

I hit a rather annoying little problem a little while ago when using GoldenGate for an Exadata migration project. The replicat process was failing to start and the following error was shown in the report file –

OGG-01746 Support for parameter SUPPRESSTRIGGERS is not available in the RDBMS version you are using

This was initially confusing because the target database was 11.2.0.3 which definitely supports the use of this parameter.

In the end, it turned out that the parameter was placed in the replicat parameter file ABOVE the DBLOGIN parameter. This is actually where the 11.1.1 documentation tells you to put it but I think that is a documentation bug. In the 11.1.1.1.1 documentation, it clarifies that the SUPPRESSTRIGGERS parameter must come BELOW the DBLOGIN parameter.

The other point worth mentioning about using this parameter, is that it will only suppress valid triggers. This seems quite a pointless distinction because invalid triggers won’t trigger anyway, right? Well, enabled invalid triggers will actually cause the replicat to fail as soon as it tries to do an insert on that table – even with the SUPPRESSTRIGGERS parameter in use. The error encountered is –

OGG-01154 SQL error 4098 mapping <SCHEMA>.<TABLE> to <SCHEMA>.<TABLE> OCI Error ORA-04098: trigger ‘<SCHEMA>.<TRIGGER>’ is invalid and failed re-validation

Fix and recompile the trigger, and replicat should continue.

Advertisements
Post a comment or leave a trackback: Trackback URL.

Comments

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: