My Oracle Support Banner

After Doing Import With veridata_import.sh SCALE Defined On TIMESTAMP Columns Gets Missing (Doc ID 2871598.1)

Last updated on MAY 23, 2022

Applies to:

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

Symptoms

After doing import with veridata_import.sh, SCALE defined on TIMESTAMP columns gets missing:

In order to refresh or deploy new config between environments, customer uses "veridata_export.sh" and "veridata_import.sh" scripts.

Issue:

Step 1) After export is done with "veridata_export.sh", it can be verified that "scale" config of some "timestamp" columns are exported correctly.
Step 2) After IMPORT is done with "veridata_import.sh" from the file from Step 1), it is found that attribute "scale" are missing or are ignored by import.
Step 3) It can also be verified in GUI or with simple export again, that there are no "scale" attribute now in the timestamp columns.

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.