Bad Data Via @GETENV('RECORD', 'TIMESTAMP') After DB2 V11 Upgrade (Doc ID 2217678.1)

Last updated on APRIL 19, 2017

Applies to:

Oracle GoldenGate - Version 12.1.2.1.1 to 12.2.0.1.0 [Release 12.1 to 12.2]
IBM z/OS on System z

Symptoms

---------------------------------------------------
Bad data via @GETENV('RECORD', 'TIMESTAMP') after DB2 V11 upgrade

Problem Description
---------------------------------------------------
“Since the upgrade started at 2016-12-10 22:32:11.161632, the value for the commit timestamp of when each record was written to the database log has been populated with the static value of “1899-12-31 19:00:00.000000”.

The Golden Gate code for the token is:

tk_prcs_ts = @GETENV('RECORD', 'TIMESTAMP')

The value is different from the transaction commit timestamp as it unique for every record and not every transaction.

The impact of this causes us to not be able to process any OM data as typically process the data utilizing this value for a particulate window in time.”

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