Oracle GoldenGate causes imp to have a ORA-32588 Error

Oracle GoldenGate causes imp to have a ORA-32588 Error

The customer said that the following error was reported when importing data to the source database after GG was implemented:

From this error, we can see that adding logs of all column type to the table causes data import failure.

Looking back to the implementation steps of Oracle GoldenGate, Oracle GoldenGate will add the appropriate Supplemental log based on the table when performing the following operations:

Add trandata .;

Because some tables in the customer's database do not have a primary key or a unique key to identify the uniqueness of the table row, Oracle GoldenGate automatically adds ALL columns and other types of supplemental logs to this table, use the entire row to identify the uniqueness of the table's row data, which is a normal behavior of Oracle GoldenGate.

Refer to Oracle's explanation of this error:

ORA-32588: supplemental logging attribute string exists

Cause: specified supplemental logging attribute exits.

Action: retry the alter/create ddl after removing this supplemental logging attribute.

Run the alter table xxx drop supplemental log data (ALL) COLUMNS command to delete the supplemental log corresponding to the TABLE and then try to import it again.

Of course, the best and easiest way is to execute the following GoldenGate command to accurately uninstall the supplemental logs corresponding to the table:

GGSCI> delete trandata .;

-- End --

GoldenGate unidirectional table DML Synchronization

Oracle GoldenGate series: restoration principles of Extract processes

Oracle GoldenGate installation Configuration

OGG-01004 OGG-1296 error for Oracle goldengate

Oracle GoldenGate Quick Start Tutorial: Basic Concepts and configurations

Build a GoldenGate bidirectional replication environment from Oracle to Oracle