Best Practices for Oracle JDBC Drivers to Be Used with ODI Including Resolutions for Issues Encountered Due to an Inappropriate Version of JDBC Driver
(Doc ID 423733.1)
Last updated on JANUARY 02, 2024
Applies to:
Oracle Data Integrator - Version 10.1.3.2.0 and later Oracle Data Integrator on Marketplace - Version 1.0.2 and later Information in this document applies to any platform.
Purpose
The purpose of this document is to:
Help you in the identification and resolution of problems that are encountered when using Oracle JDBC Drivers with Oracle Data Integrator (ODI).
Provide a response to the question "which is faster between the THIN and OCI drivers?".
The article applies to all releases of ODI like the current 12C as well as to previous releases.
Scope
Oracle recommends the use of the most recent version of its JDBC Driver.
However, problems may be signaled during their use with Oracle Data Integrator (ODI). These problems are due to an inappropriate version of JDBC Driver.
Case 1. The Network Adapter could not establish the connection
When opening an Integration Interface, the following message is displayed:
No error is thrown when using the same JDBC driver to load this Date from Oracle 10g to Oracle10g.
Case 12. Wrong reverse engineering of the length of CHAR and VARCHAR2 datatypes
The Oracle JDBC driver reverse engineers CHAR and VARCHAR2 data types with a length four times larger than the expected one. For example, a VARCHAR2 (10) is reversed engineered as VARCHAR2(40), which is not correct.
This bug is responsible or a wrong reverse of the length of CHAR and VARCHAR datatypes
Details
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
