Hello everyone, we use the Oracle connector 0.5.7 to sync an Oracle DB (19c) with Snowflake. We get this error: 2025-12-22 160916 source INFO i.a.c.i.s.r.AbstractDbSource(lambda$read$1):184 Closing database connection pool. 2025-12-22 160916 source INFO c.z.h.HikariDataSource(close):349 HikariPool-1 - Shutdown initiated... 2025-12-22 160916 source INFO c.z.h.HikariDataSource(close):351 HikariPool-1 - Shutdown completed. 2025-12-22 160916 source INFO i.a.c.i.s.r.AbstractDbSource(lambda$read$1):186 Closed database connection pool. 2025-12-22 160916 source ERROR i.a.c.i.b.AirbyteExceptionHandler(uncaughtException):64 Something went wrong in the connector. See the logs for more details. java.lang.ArrayIndexOutOfBoundsException: Index 8 out of bounds for length 8 at oracle.jdbc.driver.T4CMAREngineNIO.buffer2Value(T4CMAREngineNIO.java:736) ~[ojdbc8-19.7.0.0.jar:19.7.0.0.0] at oracle.jdbc.driver.T4CMAREngineNIO.unmarshalSB4(T4CMAREngineNIO.java:518) ~[ojdbc8-19.7.0.0.jar:19.7.0.0.0] It is a LAN connection from airbyte on-prem to the db server. Any idea what could be the cause? Thanks a lot for your help

The knowledge sources don’t contain a direct explanation or fix for this specific

ArrayIndexOutOfBoundsException

coming from

ojdbc8

in the Oracle source connector, so I can only give partial guidance. A very similar pattern appears in other connectors: an internal Java exception in the connector or JDBC driver that is resolved by upgrading Airbyte and/or the connector versions. For example, a

ArrayIndexOutOfBoundsException

in a Stripe → BigQuery sync was fixed by upgrading Airbyte to a newer version, and the recommendation was simply to move to the latest Airbyte and connector builds.[[Stripe–BQ error](https://discuss.airbyte.io/t/1401)][[connector updates](https://github.com/airbytehq/airbyte/issues/54706)] Given what’s available in the docs and forum threads, here’s what is reasonably supported to try: 1. Upgrade Airbyte and the Oracle source connector - You’re already on Oracle source

0.5.7

, which is very recent, but the pattern in other issues is that internal Java errors are often fixed in newer platform/connector images. The official guidance is to keep connectors updated via the standard update mechanism.[[connector updates](https://github.com/airbytehq/airbyte/issues/54706)] - If your Airbyte core version is older, upgrade Airbyte itself and then re‑update the Oracle connector. 2. Check if the error is data‑dependent / table‑specific The docs don’t describe this exact driver bug, but other Oracle issues have been narrowed down by: - Reducing the number of tables or schemas involved (large schemas and many tables can trigger edge cases).[[Large schema issue](https://discuss.airbyte.io/t/2157)] - Trying a smaller subset of tables or a single table to see if the error only appears for specific data. 3. Try adjusting JDBC parameters (timeouts, prefetch) The Oracle source allows additional JDBC parameters such as

defaultRowPrefetch

and timeouts.[[Oracle source getting started](https://docs.airbyte.com/integrations/sources/oracle#getting-started-airbyte-open-source)] While the docs don’t state that these fix

ArrayIndexOutOfBoundsException

, they are the supported levers you can safely adjust: - Lower

defaultRowPrefetch

(e.g.

defaultRowPrefetch=10

or

20

) - Set reasonable

oracle.net.CONNECT_TIMEOUT

and

oracle.net.READ_TIMEOUT

Example (in the “JDBC URL Params” field for the Oracle source):

text    defaultRowPrefetch=20&oracle.net.CONNECT_TIMEOUT=10000&oracle.net.READ_TIMEOUT=30000

4. Confirm basic requirements and permissions Ensure your setup matches the documented requirements (Oracle 11g+ for the open‑source source connector, dedicated read‑only user, correct schema configuration).[[Oracle source getting started](https://docs.airbyte.com/integrations/sources/oracle#getting-started-airbyte-open-source)] Because the provided knowledge doesn’t document this exact stack trace or a known bug ID for it, if the above steps don’t change the behavior, the next supported step would be: - Collect the full connector logs for the failing sync. - Open an issue on the Airbyte GitHub repo or a thread on the Airbyte forum, attaching those logs and specifying: - Airbyte version - Oracle source version (

0.5.7

) - Oracle DB version (19c) - Whether it fails on all tables or only some, and whether a reduced schema still fails. That will allow the team to correlate it with any ongoing Oracle/JDBC driver issues and potentially ship a fix in a newer connector image.