My Oracle Support Banner

After Upgrading the JDBC Driver in OC4J to 11g the Connection Pool Could not be Created (Doc ID 866646.1)

Last updated on SEPTEMBER 07, 2021

Applies to:

JDBC - Version and later
Oracle Containers for J2EE - Version to [Release AS10gR3]
Information in this document applies to any platform.


After upgrading the JDBC driver shipped with Oracle Application Server 10.1.3.x to JDBC driver version 11g using following note:
<Note 420303.1> - How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container

the OC4J container fails to start.

The error reported is:

"Error initializing the Oracle JMS Resource provider for Queues:  Connection-cache is disabled"

When running a simple EAR file to determine JDBC driver version used in OAS 10.1.3 exceptions thrown:

at oracle.sql.converter.Orai18nCharacterSetMetaData.getMaxCharLength(
at oracle.sql.converter.CharacterSetMetaData.getRatio(
at oracle.jdbc.driver.DBConversion.init(
at oracle.jdbc.driver.DBConversion.<init>(
at oracle.jdbc.driver.T4CConnection.connect(
at oracle.jdbc.driver.T4CConnection.logon(
at oracle.jdbc.driver.PhysicalConnection.<init>(
at oracle.jdbc.driver.T4CConnection.<init>(
at oracle.jdbc.driver.T4CDriverExtension.getConnection(
at oracle.jdbc.driver.OracleDriver.connect(
at java.sql.DriverManager.getConnection(
at java.sql.DriverManager.getConnection(



Upgrade of JDBC driver version to 11g


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.