Last updated on MAY 07, 2017
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms