always remember

Nothing is foolproof to a sufficiently talented fool... Make something
idiot proof, and the world will simply make a bigger idiot.

OGG-00730 – No minimum Supplemental Logging is enabled

This issue was encountered whilst shipping an Oracle 12c schema to an MSSQL Server 2014 instance using OGG 12.3.

During the Change Data Capture configuration and EXTRACT setup and start processes, you may find your EXTRACT abends with:

OGG-00730  No minimum supplemental logging is enabled.

There are 2 reasons this may occur, the first is that you actually don’t have any supplemental logging enabled… The second is a documented Oracle bug, in which the GoldenGate process detects the presence of LOG DATA, but reports back on it incorrectly. Both scenarios are explained below.

CHECK TO SEE IF DATABASE LEVEL SUPPLEMENTAL LOGGING IS ENABLED OR NOT:

SQL> SELECT force_logging, supplemental_log_data_min FROM v$database;

FORCE_LOGGING             SUPPLEME
------------------------- --------
NO                        NO

SQL>

In this case, there is no logging, so OGG is correct. We can enable it with:

SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
Database altered.

Switch the LOG FILE in DB:

SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.

Modify your EXTRACT process to begin at a point where SUPPLEMENTAL LOGGING is enabled:

GGSCI> ALTER EXTRACT, EORA9001 BEGIN NOW
EXTRACT altered.

IF SUPPLEMENTAL LOGGING IS ENABLED, AND THE ERROR IS STILL PRESENT:

If the above check reported supplemental logging was already enabled, you can get around the OGG bug by instructing your EXTRACT to ignore the results of the SUPP LOG CHECK. You can do this by editing your Change Capture EXTRACT PARAM file and adding the line “TRANLOGOPTIONS DISABLESUPPLOGCHECK”.

Note that the above parameter is not documented piublicly by Oracle. You may wish to remove this once the change capture process has started successfully.

dave / July 27, 2018 / Code, Oracle