My Oracle Support Banner

Different Date Timestamp is Stored when Loading Data to BICS Schema Instance in ODI 12.2.1.3 (Doc ID 2388624.1)

Last updated on AUGUST 18, 2023

Applies to:

Oracle Data Integrator - Version 12.2.1.3.0 to 12.2.1.3.181204 [Release 12c]
Information in this document applies to any platform.

Symptoms

When using the "IKM for Oracle BI Cloud Service" and executing an Oracle Data Integrator (ODI) 12c Mapping that loads data from Oracle DATE into BI Cloud Service (BICS) DATE, the timestamp is different in the **target** database when compared to the **source** for the DATE.

In the **target** database, the TIME portion of DATE gets reset to GMT, as shown in the example below:

Oracle Database Timezone(Source)

Source TIMEValue for the Date

The DUMP of the DATE column

(SELECT DUMP(DATE_COLUMN) FROM TABLE)

 BICS Timezone(Target)

Target TIMEValue for the Date

The DUMP of the DATE column

(SELECT DUMP(DATE_COLUMN) FROM TABLE)
America/Chicago Typ=12 Len=7: 120,118,3,2,14,50,54 America/Chicago Typ=12 Len=7: 120,118,3,2,22,50,54
America/Los_Angeles Typ=12 Len=7: 120,118,3,2,14,50,54 America/Chicago Typ=12 Len=7: 120,118,3,2,22,50,54

 

 

 

 

 

 

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!

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