How to Resolve: Extract Abending With OGG-00730 Oracle GoldenGate Capture for Oracle, elemental logging was ... and lsupplemental logging is ON
(Doc ID 1617738.1)
Last updated on MARCH 07, 2019
Applies to:Oracle GoldenGate - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Qn1:ERROR OGG-00730 Oracle GoldenGate Capture for Oracle, elemental logging was on <>: No minimum supplement
al logging is enabled. This may cause extract process to handle key update incorrectly if key column is not in first row piece.
However, supplemental logging is on.
This is an issue in which other or previous uses of supplemental logging cause the issue.
Current known causes of this issue are:
Extract can still find data compressed on a table even when the table itself says its not compressed:
1) If table data was compressed before, table was altered later on to disable compression.
In this case, compressed data is not decompressed when table is altered.
Any dml on previously compressed data will still show up as compressed data.
2)Table is partitioned, and one or more of the partition is compressed.
3)The table is not compressed, but the tablespace its stored in is compressed.
Data stored in tablespace with compression clause will show up as
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document