Bug 16234725 - LCR LOSES COMMIT TIME ATTRIBUTE WHEN TRANSACTION IS RE-APPLIED AFTER FAILURE (Doc ID 1950545.1)

Last updated on MARCH 12, 2015

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 to 12.1.0.1 [Release 10.2 to 12.1]
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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms