Number(13,3) has invalid value in trail file when uses OUTPUTFORMAT TEXT in AIX platform
(Doc ID 2525007.1)
Last updated on MAY 08, 2019
Applies to:
Oracle GoldenGate - Version 12.3.0.1.3 and laterIBM AIX on POWER Systems (64-bit)
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or
Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
Data gets corrupted.
TABLE <schema>.<table_name> have row with field NUM NUMBER(13,3) default 0 not null:
select ID, NUM from <schema>.<table_name>;
ID NUM
1 25
2 35
3 0
4 45
but NUM filed on trail file gets corrupted value. Check the value in file below :
cat ts000000000
B,2019-02-20:15:48:01.000000,1550677681,2440,
I,A,GGADMIN.TST,ID,'1',NUM,16718206241729413.120
C,
B,2019-02-20:15:48:05.000000,1550677685,2440,
I,A,GGADMIN.TST,ID,'2',NUM,14989949884725985.280
C,
B,2019-02-20:15:48:09.000000,1550677689,2440,
I,A,GGADMIN.TST,ID,'3',NUM,13261693527722557.440
C,
B,2019-02-20:16:36:22.000000,1550680582,2441,
I,A,GGADMIN.TST,ID,'4',NUM,11533437170719129.600
C,
[
extract parameters:
EXTRACT <extract_name>
--OUTPUTFORMAT TEXT
FORMATASCII
EXTTRAIL <trail file name with path>
TABLE <schema>.<table_name>;
ADD EXTRACT ext_ts, EXTTRAILSOURCE <trail file name with path>
ADD EXTTRAIL <trail file name with path>, EXTRACT <extract_name>, MEGABYTES 10
START EXTRACT <extract_name>
Changes
New configuration
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 |
| Changes |
| Cause |
| Solution |
| References |