Wrong TIMEZONE On Teradata

(Doc ID 2255766.1)

Last updated on OCTOBER 11, 2017

Applies to:

Oracle GoldenGate - Version 12.2.0.1.0 to 12.2.0.1.0 [Release 12.2]
Information in this document applies to any platform.

Symptoms

We have a Oracle GoldenGate running on IBM AIX replicating transactions to our Teradata 15.00. In our Teradata we have a Table that has a column with TIMESTAMP(6) WITH TIME ZONE NOT NULL.
 
When we receive the records from the GoldenGate, the output for this column in this way:


29 I 2016-02-21 01:21:52.065024+00:00

30 I 2016-02-21 01:21:52.065024+00:00

Remember that the source(GoldenGate, there is no timezone).


But, the output should be this way:


29 I 2016-02-21 01:21:52.065024-03:00

30 I 2016-02-21 01:21:52.065024-03:00
 

On GoldenGate trail file is set DbTimestamp as -03:00 (from logdump)

TokenID x3c '<' DbObjNameMetadata Info x00 Length 20
 0000 0010 1414 1414 1414 1414 1414 1414 1114 1414 | ....................
TokenID x3d '=' DbTimeZone Info x00 Length 8
 0006 2d30 333a 3030 | ..-03:00


On GoldenGate replicat a tried:

SQLEXEC "SET TIME ZONE '-03:00';"
SQLEXEC "COMMIT;"

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