My Oracle Support Banner

Committimestamp value is different is local and remote trail (Doc ID 1460934.1)

Last updated on AUGUST 11, 2021

Applies to:

Oracle GoldenGate - Version 11.1.1.1.1 and later
Information in this document applies to any platform.

Goal

 When using @GETENV("GGHEADER", "COMMITTIMESTAMP") on replicat, committimestamp is not same as commit timestamp of the source record. Source record will not have milli seconds, but record in target trail has milli seconds.

To understand why does source record does not have milliseconds, refer to GoldenGate Extract Trails do not Record Milliseconds for Source Oracle Commit Timestamps (Doc ID 1374957.1)

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.