How to Use The Latest Thin JDBC Driver Across All Applications Within OC4J 10.1.3.x Container
(Doc ID 420303.1)
Last updated on AUGUST 07, 2020
Applies to:Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
JDBC - Version 10.1.0.5 to 126.96.36.199.0 [Release 10.1 to 11.2]
Information in this document applies to any platform.
This document describes how to upgrade the JDBC thin driver that all applications use within the container through a shared library for OC4J 10.1.3.x.
Unless there is a pressing need to switch from the default 10.1.0.5 JDBC driver you should be very careful about replacing the driver for all applications. In most cases just switching the JDBC driver for a single application may be all you need. See <Note 787689.1>, "Installing/Configuring OAS 10.1.3.x to use Different Oracle JDBC Driver Versions".
- Note this document is for OC4J use only, and is not applicable to Oracle applications installed and configured with the full Oracle Application Server installations.
- Once Oracle Database 11g became certified with Oracle Application Server 10g, there are specific instructions (as tested by QA) to use the 10.1.0.5 driver with a patch and specific settings:
<Note 887365.1> Oracle Database 11g Release 2 (11.2) Certification for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4)
<Note 740417.1> Oracle Database 11g Release 1 (11.1) Certification for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4)
- See also for an overall summary/history of JDBC driver support for Oracle Application Server (pre-WLS):
<Note 365120.1> JDBC Driver Support for Oracle Application Server (Fusion Middleware)
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