OGGBD- DATE Columns In Source Mapped To TIMESTAMP In BigQuery Causing Errors
(Doc ID 2918546.1)
Last updated on JULY 20, 2024
Applies to:
Oracle GoldenGate Big Data and Application Adapters - Version 21.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Source: MySQL 5.5
Target: GCP BigQuery
Even with OGGBD 21.7.x , the DATE columns in the source(Mysql) mapped to
TIMESTAMP in BigQuery causing errors
[TaskEngine_4(FlushTask)] - Error executing
batch for target table <tablename>
=ERROR 2022-09-04 03:46:52.000022 [TaskEngine_4(FlushTask)] - id: null
location: expiration message: Could not parse '2027-08-08' as a timestamp.
Required format is YYYY-MM-DD HH
:MM[:SS[.SSSSSS]] reason: invalid
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 |