Database Utilities (MOSC)

MOSC Banner

Milliseconds of precision in TIMESTAMP WITH TIME ZONE is lost during import to Oracle 12.1.0.1.0 fro

edited Jul 22, 2015 11:07AM in Database Utilities (MOSC) 17 commentsAnswered

We're experiencing an issue in testing migration of data to 12c in our lab.  I was wondering if there are any pointers or resolution suggestions for what we're seeing.

Observation:     

It appears that TIMESTAMP WITH TIME ZONE entries in a table that was generated in Oracle 11 (version  11.2.0.3) lose the milliseconds of precision during the import into Oracle 12 (version 12.1.0.1.0). 

We have created an example schema (in Oracle 11.2.0.3) to illustrate the problem as the following:

CREATE TABLE SIMPLE_TIMESTAMP

(

SIMPLE_TIMESTAMP_ID NUMBER(14)  NOT NULL,

CREATED_DATE TIMESTAMP(3) WITH TIME ZONE  NOT NULL ,

CONSTRAINT  XPKSIMPLE_TIMESTAMP PRIMARY KEY (SIMPLE_TIMESTAMP_ID)

);

We have added two rows that contain some milliseconds precision time and verified that exporting from Oracle

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center