My Oracle Support Banner

IE & CE Abend With OGG-02297 On Executing Alter Table To Add Identity Column (Doc ID 2780232.1)

Last updated on JUNE 07, 2021

Applies to:

Oracle GoldenGate - Version 12.3.0.1.3 to 19.1.0.0.4 [Release 12.3]
Information in this document applies to any platform.

Symptoms

With Sequence replication:

On source DB, if a new column is added into a table with a DDL like this

ALTER TABLE <SCHEMA>.<TABLE>
ADD (ID NUMBER DEFAULT "<SCHEMA>"."COL_SEQ"."NEXTVAL" CONSTRAINT COL NOT NULL);

Then it abends an extract…

Below workaround works ok.
1.
ALTER TABLE MDAWS.EM_AWS_LOAD_TST
ADD (ID NUMBER DEFAULT 1 CONSTRAINT EM_AWS_LOAD_BOOKING_ID_NN_TST NOT NULL);
2.
ALTER TABLE MDAWS.EM_AWS_LOAD_TST
modify (ID DEFAULT "MDAWS"."EM_AWS_LOAD_BOOKING_TST_SEQ"."NEXTVAL");

All other sequence DDLs and sequence values changes are replicating well.

 This is an unsupported ALTER TABLE statement for table <SCHEMA>.<TABLE>

Changes

 With Sequence replication:

On source DB, if a new column is added into a table with a DDL like this

ALTER TABLE <SCHEMA>.<TABLE>
ADD (ID NUMBER DEFAULT "<SCHEMA>"."COL_SEQ"."NEXTVAL" CONSTRAINT COL NOT NULL);

Then it abends an extract… Rest of the sequence DDL and values work fine

Cause

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
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.