Troubleshooting Oracle to BigQuery connection with TIMESTAMP WITH TIMEZONE data type

Summary

When configuring the connection between Oracle and BigQuery, encountering issues with the TIMESTAMP WITH TIMEZONE data type causing error code 504. Warning found in Kubernetes pod related to this data type. Seeking solution without altering types in the origin.


Question

Hi family! I have problems when I am trying to configure the connection between Oracle to BigQuery. I think it is caused by data type TIMESTAMP WITH TIMEZONE. When I tried with other schema which has not any table with this data type, it did not give me this problem. The error code is 504. If I look into the kubernetes pod, I can find a warning about this data type. How can I solve it without alter types in origin?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["oracle", "bigquery", "timestamp-with-timezone", "error-504", "kubernetes", "data-type"]