Bug 16234725 - LCR LOSES COMMIT TIME ATTRIBUTE WHEN TRANSACTION IS RE-APPLIED AFTER FAILURE
(Doc ID 1950545.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 to 126.96.36.199 [Release 10.2 to 12.1]
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.
In a streams configuration, LCR's are being handled by an PL/SQL procedure; we have discovered that if an LCR fails, re-trying it (after resolving the underlying problem) leads to one of the additional columns, which is filled with a call to
being inserted as empty. Other additional columns are properly assigned, e.g.:
When commit_time gets NULL value after querying the apply error table, then this bug is hit.
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