Bug 16234725 - LCR LOSES COMMIT TIME ATTRIBUTE WHEN TRANSACTION IS RE-APPLIED AFTER FAILURE
(Doc ID 1950545.1)
Last updated on JANUARY 11, 2023
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 10.2.0.4 to 12.1.0.1 [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
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
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
Lcr.ADD_COLUMN('new','COMMIT_TIME',anydata.ConvertDate(Lcr.GET_COMMIT_TIME()));
being inserted as empty. Other additional columns are properly assigned, e.g.:
Lcr.ADD_COLUMN('new','COMMIT_SCN',anydata.ConvertNumber(Lcr.GET_COMMIT_SCN()));
Changes
When commit_time gets NULL value after querying the apply error table, then this bug is hit.
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 |
References |