Streams Contains Incorrect Data in LCRs
(Doc ID 1361462.1)
Last updated on MARCH 13, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Issue occurs with tables created with COMPRESS for OLTP. When the table is
loaded using a PL/SQL BULK COLLECT and INSERT (as well as Peoplesoft script), some LCRS get generated with NULL values or wrong data for columns defined with a NOT-NULL constraint.
LCRS may fail to apply at the target database with an ORA-1400 which is expected if NOT-NULL constraint exist.
A print transaction of the LCR shows the corresponding column has a NULL value.
The logminer output for the corresponding transaction also shows the insert contains a NULL value for the column but the insert executed at the source insert the correct data on the table.
Data in redo logs are correct, just the handling by logminer is incorrect.
Use of bulk collect and/or insert on OLTP compressed table
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