X

Proactive insights, news and tips from Oracle WebLogic Server Support. Learn Oracle from Oracle.

  • March 9, 2015

WLS JDBC Driver Patching

Stephen Felts
Manager

The handling of Oracle driver jar patches is
complicated but getting sorted out. This
article tries to gather the information in one place with pointers to more
details.  There are a few patches that are still not available, marked as TBA (To Be Available) in the tables below.  As these files become available, this page will be updated.

WLS 10.3.6, 12.1.1, and 12.1.1 shipped Database 11.2.0.3 jar files.  However these are non-standard versions of the jars with additional bug fixes and enhancements to support WLS.  That means that you can't
just drop in an 11.2.0.3 patch or upgrade to 11.2.0.4 using standard released jar files. Although support is required to provide
11.2.0.3 patches as needed, it will be difficult and the recommendation is to
upgrade to a special 11.2.0.4 patch that contains 11.2.0.4 and all of the
patches and enhancements in the 11.2.0.3 database jar files shipped with WLS. It's further complicated because WLS started
using the Oracle Universal Installer in 12.1.2, requiring a different patch
format.

WLS 10.3.6, 12.1.1, 12.1.2, and 12.1.3 also support running with
Oracle Database 12c client jar files. For WLS 10.3.6
through 12.1.2, the jar files must be manually installed; there is no installer
or patch to automate this upgrade. To
get patches, you must be running with the Database 12.1.0.2 jar files; WLS patches will not be generated
for the Database 12.1.0.1 jar files. WLS 12.1.3 ships with a
pre-release version of Database 12.1.0.2 driver jar files and a patch will be available to upgrade to the production version of these files. After this upgrade, standard database Oracle
patch files will work as expected for WLS 12.1.3 (and WLS 12.1.2 with a manual
upgrade to database 12.1.0.2 jar files).

Patching the installed Oracle Driver

WLS Release

Oracle Driver Install

Database Jar

Patch Strategy

Documentation

10.3.6

11.2.0.3.0AS11.1.1.6.0

11.2.0.4 WLS patch

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1970437.1

12.1.1

11.2.0.3.0AS11.1.1.6.0

11.2.0.4 WLS patch

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1970437.1

12.1.2

11.2.0.3.0AS12.1.2.0.0

11.2.0.4 opatch

Patch Request 18557114 for bug
19477203

12.1.3

Pre-12.1.0.2

12.1.0.2 opatch to bring up
to shipping 12.1.0.2; standard opatch for additional bug fixes

Patch 20741228: 12.1.3 WLS UPGRADE TO 12.1.0.2 JDBC RELEASE


























Running with the Database 12c Driver

WLS Release

12.1.0.2 installation

Database Jar Patch Strategy

Documentation
for Installation

Documentation for patching

10.3.6

Manual
installation of 12.1.0.2

12.1.0.2
WLS patch

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1564509.1

TBA

12.1.1

Manual
installation of 12.1.0.2

12.1.0.2
WLS patch

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1564509.1

TBA

12.1.2

Manual
installation of 12.1.0.2

12.1.0.2
opatch

https://docs.oracle.com/middleware/1212/wls/JDBCA/ds_12cdriver.htm#JDBCA272

Standard
patch procedure

12.1.3

Pre-12.1.0.2
installed; Patch to bring up to shipping 12.1.0.2

12.1.0.2
opatch

https://docs.oracle.com/middleware/1213/wls/JDBCA/ds_12cdriver.htm#JDBCA272

Patch 20741228: 12.1.3 WLS UPGRADE TO 12.1.0.2 JDBC RELEASE

Standard
patch procedure

On a related topic, updating non-Oracle driver jar
files is covered by the following note.


https://support.oracle.com/epmos/faces/DocumentDisplay?id=1

This includes the DataDirect and MySQL drivers
that are shipped in the kit. The jar
file is backed up and removed, the new file installed, and the CLASSPATH adjusted
if the jar name changes.

You'll notice that releases earlier than WLS 10.3.6 are not discussed.  For releases earlier than WLS 10.3.4, they depend only on the ojdbcN.jar file.  It's possible that they will work with the 11.2.0.4 jar file but that hasn't been certified and they are not still in error correction support.  For WLS 10.3.4 or 10.3.5, it depends not only on a specific ojdbc jar file but also ONS/UCP jars that have the package names renamed.  They will likely not work correctly with the 11.2.0.4 jar file (certainly not Active GridLink).  Since these releases ended error correction support in May 2012, you will need to upgrade to WLS 10.3.6 or 12.1.x to use later driver jar files.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.