My Oracle Support Banner

ORA-1000 and ORA-904 With JDBC (Doc ID 2048420.1)

Last updated on AUGUST 30, 2023

Applies to:

JDBC - Version and later
Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


On : version, Thin JDBC driver

WebLogic 12.1.3 ojdbc7.jar does not behave the same as earlier versions of WebLogic.
After upgrading an application which has been running in WebLogic 10.3.2 to WebLogic 12.1.3, the application is getting too many open cursors from the database.
This worked on WebLogic 12.1.2, and only fails when moving to WebLogic 12.1.3.
As a workaround, trying to move ojdbc6.jar file from WebLogic 10.3.2 to the 12.1.3 box and put it in the pre classpath for a test, generates exceptions.

Database error:

ORA-01000: maximum open cursors exceeded

In application (JDBC logging):

DEBUG 4175 StatementCreatorUtils.setNull Could not check database or driver name
java.sql.SQLSyntaxErrorException: ORA-00904: "F": invalid identifier

  at oracle.jdbc.driver.T4CTTIoer.processError(
  at oracle.jdbc.driver.T4CTTIoer.processError(
  at oracle.jdbc.driver.T4CTTIoer.processError(
  at oracle.jdbc.driver.T4CTTIfun.processError(
  at oracle.jdbc.driver.T4CTTIfun.receive(
  at oracle.jdbc.driver.T4CTTIfun.doRPC(
  at oracle.jdbc.driver.T4C8Odscrarr.doODNY(
  at oracle.jdbc.driver.T4CPreparedStatement.doDescribe(
  at oracle.jdbc.driver.OracleStatement.describe(
  at oracle.jdbc.driver.OracleResultSetMetaData.(
  at oracle.jdbc.driver.OracleStatement.getResultSetMetaData(
  at oracle.jdbc.driver.OraclePreparedStatement.getMetaData(
  at oracle.jdbc.driver.OraclePreparedStatementWrapper.getMetaData(
  at oracle.jdbc.driver.OracleParameterMetaData.getParameterMetaData(
  at oracle.jdbc.driver.OraclePreparedStatement.getParameterMetaData(
  at oracle.jdbc.driver.OraclePreparedStatementWrapper.getParameterMetaData(
  at weblogic.jdbc.wrapper.PreparedStatement.getParameterMetaData(
  at org.springframework.jdbc.core.StatementCreatorUtils.setNull(
  at org.springframework.jdbc.core.StatementCreatorUtils.setParameterValueInternal(
  at org.springframework.jdbc.core.StatementCreatorUtils.setParameterValue(
  at org.springframework.jdbc.core.ArgPreparedStatementSetter.doSetValue(
  at org.springframework.jdbc.core.ArgPreparedStatementSetter.setValues(
  at org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(
  at org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(
  at org.springframework.jdbc.core.JdbcTemplate.execute(
  at org.springframework.jdbc.core.JdbcTemplate.update(
  at org.springframework.jdbc.core.JdbcTemplate.update(
  at org.springframework.jdbc.core.JdbcTemplate.update(

The issue can be reproduced after :
1. Upgrading WebLogic from 10.3.2 to WebLogic 12.1.2
2. Then, upgrading from 12.1.2 to WebLogic 12.1.3.
3. Running application in this new version.

NOTE: This issue is not particular to WebLogic application server. It can happen with Oracle JDBC standalone or third-party application servers using JDBC


 Upgrade from WebLogic 10.3.2 to WebLogic 12.1.3.


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.