EXTRACT misparses DDL metadata causing extract/ replicat errors when processing DML after a DDL change
Last updated on FEBRUARY 20, 2018
Applies to:Oracle GoldenGate - Version 18.104.22.168.22 and later
Information in this document applies to any platform.
Incorrect DDL support implementation caused incorrect metadata info passed to Extract that will cause various issues when processing
DML after the table layout has been changed (DDL trigger based replication enabled).
The issue affects classic and integrated extract where trigger based DDL setup is in place. This issue does not occur if using IE with integrated DDL capture.
Some of the errors seen are
1) EXTRACT abending with
2014-08-26 15:55:36 ERROR OGG-01161 Bad column index xx specified for table <schema>.<table name>, max columns = nn.
2) Extract does not capture newly added columns
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms