My Oracle Support Banner

DST with INCLUDEREGIONID / INCLUDEREGIONIDWITHOFFSET (Doc ID 2430038.1)

Last updated on FEBRUARY 27, 2019

Applies to:

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

Symptoms

When setting INCLUDEREGIONID or INCLUDEREGIONIDWITHOFFSET, timestamp data is written into trail file which DST is considered.
But in following document, only INCLUDEREGIONIDWITHOFFSET mentions about DST (Daylight Saving Time).

Oracle Fusion Middleware Reference for Oracle GoldenGate 12c (12.3.0.1) E81608-06 June 2018

6.165 TRANLOGOPTIONS

INCLUDEREGIONID
Use when replicating from an Oracle source to an Oracle target of the same version or later.
When INCLUDEREGIONID is specified, Extract adds a column index and the two-byte TMZ
value as a time-zone mapping token and outputs it to the trail in the UTC format of
YYYY-MM-DD HH:MI.SS.FFFFFF +00:00.

INCLUDEREGIONIDWITHOFFSET

Use when replicating TIMESTAMP WITH TIME ZONE as TZR from an Oracle source that is v10g
or later to an Oracle target that is earlier than 10g, or from an Oracle source to a target that is
not an Oracle database. When INCLUDEREGIONIDWITHOFFSET is specified, Extract converts
the time zone region value to a time offset that takes Daylight Saving Time into account based
on the date and time. The timestamp data is written to the trail in local time in the format of
YYYY-MM-DD HH:MI.SS.FFFFFF TZH:TZM, where TZH:TZM is the region ID converted time offset.

 

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
Cause
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.