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 JULY 24, 2024
Applies to:
Oracle Data Integrator - Version 10.1.3.2.0 and laterOracle 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.
Questions and Answers
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
| Purpose |
| Questions and Answers |
| Scope |
| Case 1. The Network Adapter could not establish the connection |
| Case 2. ORA-00600 |
| Case 3. No standard reverse engineering |
| Case 4. NULL values are not allowed |
| Case 5. Date fields lose precision |
| Case 6a. Issues related to TIMESTAMP data type |
| Case 6b. Issues related to TIMESTAMP data type (Microsoft SQLServer timestamp to Oracle timestamp) |
| Case 7. Timestamp fields lose precision |
| Case 8. Missing IN or OUT parameter at index |
| Case 9. IO exception with Oracle 10.2.0.3 Database |
| Case 10. Can not access a member of class oracle.jdbc.driver.OraclePreparedStatementWrapper with modifiers "public" |
| Case 11. java.lang.IllegalArgumentException when loading a Date value of 01/01/1900 |
| Case 12. Wrong reverse engineering of the length of CHAR and VARCHAR2 datatypes |
| Details |
| The Oracle JDBC driver must be in concordance with both the Oracle database and JVM |
| Which is faster, the THIN driver or the THICK (OCI-based) driver? |
| Case 1 (only). The Network Adapter could not establish the connection |
| Case 4 (only). NULL values are not allowed |
| Case 5 (only). Date fields lose precision |
| Case 6a (only). Issues related to TIMESTAMP data type |
| Case 6b (only). Issues related to TIMESTAMP data type (Microsoft SQLServer timestamp to Oracle timestamp) |
| Case 7 (only). Timestamp fields lose precision |
| Case 8 (only). Missing IN or OUT parameter at index |
| Case 9 (only). IO exception with Oracle 10.2.0.3 Database |
| Case 10 (only). Can not access a member of class oracle.jdbc.driver.OraclePreparedStatementWrapper with modifiers "public" |
| Case 11. java.lang.IllegalArgumentException when loading a Date value of 01/01/1900 |
| Case 12. Wrong reverse engineering of the length of CHAR and VARCHAR2 datatypes |
| References |