OGGBD- TIME Columns In Source Mapped To TIMESTAMP In BigQuery Causing Errors
(Doc ID 2918548.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 TIME columns in the source(Mysql) mapped to TIMESTAMP in BigQuery causing errors
=ERROR 2022-10-13 20:12:27.000470 [main] - id: null location: col4 message: Could not parse '00:00:00.000000' as a timestamp. Required format is YYYY-MM-DD HH:MM[:SS[.SSSSSS]] reason: invalid
=ERROR 2022-10-13 20:12:27.000470 [main] - Flush failed for table [ <Tablename>].
Exception in thread "main" oracle.goldengate.util.GGException: Error detected handling transaction commit event.
at oracle.goldengate.datasource.UserExitDataSource.commitTransaction(UserExitDataSource.java:2494)
at oracle.goldengate.datasource.UserExitDataSource.commitTx(UserExitDataSource.java:2089)
=ERROR 2022-10-13 20:12:27.000470 [main] - Flush failed for table [ <Tablename>].
Exception in thread "main" oracle.goldengate.util.GGException: Error detected handling transaction commit event.
at oracle.goldengate.datasource.UserExitDataSource.commitTransaction(UserExitDataSource.java:2494)
at oracle.goldengate.datasource.UserExitDataSource.commitTx(UserExitDataSource.java:2089)
2022-10-13 20:12:27 ERROR OGG-15051 Java or JNI exception:
oracle.goldengate.util.GGException: Error detected handling transaction commit event.
oracle.goldengate.util.GGException: Error detected handling transaction commit event.
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 |