GoldenGate

I find myself in a slightly perplexing situation. In trying to replicate data to a SQLServer 2008 database I have no problems doing so for a date column on the Oracle side to either a DATE or DATETIME2 datatype on the SQLServer side. However, upon trying a DATETIME column I'm given the errors below. Essentially a -2147217887 but Goldengate marks it as a data overflow error. The thing is, a datetime2 is more like a TIMESTAMP column in Oracle and the DATETIME is essentially a DATE. Why it would work with a DATE (less precise) or DATETIME2 (more precise) yet not a DATETIME (same precision) is a bit of a head scratcher. The same defs file is used for each of the options.

Before anyone suggests using either destination datatype that works, I've no choice; it has to be a DATETIME column. The customer is always right, even when they are infuriatingly wrong.

Anyone seen this before or have any suggestions?

Thanks very much in advance!!

Cheers,
Chris



trace
10:55:36.538 (366244) * --- entering READ_EXTRACT_RECORD --- *
10:55:36.538 (366244) exited READ_EXTRACT_RECORD (stat=0, seqno=-1, rba=-1156485006)
10:55:36.538 (366244) processing record for QA1_DW_MS_MAY04.LIEN
10:55:36.538 (366244) mapping record
10:55:36.538 (366244) entering perform_sql_statements (normal)
10:55:36.538 (366244) entering execute_statement (op_type=5,AWO_CUBE.LIEN)
10:55:36.599 (366305) executed stmt (sql_err=-2147217887)
10:55:36.599 (366305) exited perform_sql_statements (sql_err=-2147217887,recs output=6018)
10:55:36.599 (366305) aborting grouped transaction
10:55:36.619 (366325) aborted grouped transaction
10:55:36.619 (366325) committing work
10:55:36.619 (366325) Successfully committed transaction, status = 0
10:55:36.619 (366325) work committed
10:55:36.619 (366325) writing checkpoint
10:55:36.619 (366325) * --- entering READ_EXTRACT_RECORD --- *
10:55:36.619 (366325) exited READ_EXTRACT_RECORD (stat=400, seqno=-1, rba=-1156490736)


ggserr.log:
2012-06-02 10:55:36 WARNING OGG-00869 Oracle GoldenGate Delivery for ODBC, lien.prm: Parameter #: 1 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 2 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 3 Data Type: 129 DB Part: 7 Length: 5 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 4 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 5 Data Type: 129 DB Part: 7 Length: 8 Max Length: 56 Status: 8 Precision: 56 Scale: 0 Unavailable Parameter #: 6 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 7 Data Type: 129 DB Part: 7 Length: 9 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 8 Data Type: 129 DB Part: 7 Length: 8 Max Length: 15 Status: 8 Precision: 15 Scale: 0 Unavailable Parameter #: 9 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 10 Data Type: 129 DB Part: 5 Length: 5 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 11 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 6 Precision: 23 Scale: 3 Data Overflow Parameter #: 12 Data Type: 129 DB Part: 7 Length: 13 Max Length: 512 Status: 8 Precision: 0 Scale: 0 Unavailable Parameter #: 13 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 14 Data Type: 129 DB Part: 7 Length: 1 Max Length: 1 Status: 8 Precision: 1 Scale: 0 Unavailable Native Error: 0, 0 State: 0, 22007 Class: 0 Source: Line Number: 0 Description: Invalid date format.
2012-06-02 10:55:36 WARNING OGG-01004 Oracle GoldenGate Delivery for ODBC, lien.prm: Aborted grouped transaction on 'AWO_CUBE.LIEN', Database error -2147217887 ([SQL error -2147217887 (0x80040e21)] Parameter #: 1 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 2 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 3 Data Type: 129 DB Part: 7 Length: 5 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 4 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 5 Data Type: 129 DB Part: 7 Length: 8 Max Length: 56 Status: 8 Precision: 56 Scale: 0 Unavailable Parameter #: 6 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 7 Data Type: 129 DB Part: 7 Length: 9 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 8 Data Type: 129 DB Part: 7 Length: 8 Max Length: 15 Status: 8 Precision: 15 Scale: 0 Unavailable Parameter #: 9 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 10 Data Type: 129 DB Part: 5 Length: 5 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 11 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 6 Precision: 23 Scale: 3 Data Overflow Parameter #: 12 Data Type: 129 DB Part: 7 Length: 13 Max Length: 512 Status: 8 Precision: 0 Scale: 0 Unavailable Parameter #: 13 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 14 Data Type: 129 DB Part: 7 Length: 1 Max Length: 1 Status: 8 Precision: 1 Scale: 0 Unavailable Native Error: 0, 0 State: 0, 22007 Class: 0 Source: Line Number: 0 Description: Invalid date format ).


report:
2012-06-02 10:55:36 WARNING OGG-01004 Aborted grouped transaction on 'AWO_CUBE.LIEN', Database error -2147217887 ([SQL error -2147217887 (0x80040e21)]
Parameter #: 1 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 2 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 3 Data Type: 129 DB Part: 7 Length: 5 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable
Parameter #: 4 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 5 Data Type: 129 DB Part: 7 Length: 8 Max Length: 56 Status: 8 Precision: 56 Scale: 0 Unavailable
Parameter #: 6 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 7 Data Type: 129 DB Part: 7 Length: 9 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable
Parameter #: 8 Data Type: 129 DB Part: 7 Length: 8 Max Length: 15 Status: 8 Precision: 15 Scale: 0 Unavailable
Parameter #: 9 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable
Parameter #: 10 Data Type: 129 DB Part: 5 Length: 5 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 11 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 6 Precision: 23 Scale: 3 Data Overflow
Parameter #: 12 Data Type: 129 DB Part: 7 Length: 13 Max Length: 512 Status: 8 Precision: 0 Scale: 0 Unavailable
Parameter #: 13 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable
Parameter #: 14 Data Type: 129 DB Part: 7 Length: 1 Max Length: 1 Status: 8 Precision: 1 Scale: 0 Unavailable
Native Error: 0, 0
State: 0, 22007
Class: 0
Source: Line Number: 0
Description: Invalid date format

Edited by: chris.baron on Jun 3, 2012 10:36 AM