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

Last updated on SEPTEMBER 11, 2023

Applies to:

Symptoms

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:

java.lang.NoSuchMethodError:
oracle.i18n.text.OraBoot.getCharsetMaxCharLen(Ljava/lang/String;)Ljava/lang/String;
at oracle.sql.converter.Orai18nCharacterSetMetaData.getMaxCharLength(Orai18nCharacterSetMetaData.java:53)
at oracle.sql.converter.CharacterSetMetaData.getRatio(CharacterSetMetaData.java:1214)
at oracle.jdbc.driver.DBConversion.init(DBConversion.java:162)
at oracle.jdbc.driver.DBConversion.<init>(DBConversion.java:113)
at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1119)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:303)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:640)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:205)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:554)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:185)

Changes

Upgrade of JDBC driver version to 11g

Cause

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