Unable to use ArrayDescriptor.createDescriptor with emulated datasource inside EJB (Doc ID 363466.1)

Last updated on JUNE 14, 2023

Applies to:

Symptoms

- Unable to use ArrayDescriptor.createDescriptor  inside EJB. When used with Emulated DataSource, it  fails with error              

06/03/31 10:22:19 Fail to construct descriptor: Invalid arguments
06/03/31 10:22:19 java.sql.SQLException: Fail to construct descriptor: Invalid arguments
06/03/31 10:22:19 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
06/03/31 10:22:19 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:175)
06/03/31 10:22:19 at oracle.jdbc.driver.DatabaseError.check_error(DatabaseError.java:874)
06/03/31 10:22:19 at oracle.sql.ArrayDescriptor.createDescriptor(ArrayDescriptor.java:98)
06/03/31 10:22:19 at framework.server.domainlayer.daofactory.oracle.OracleDBQuery.buildCallableStatement(OracleDBQuery.java:531)
....

- The datasource used is "com.evermind.sql.DriverManagerDataSource"

- If Native datasource "oracle.jdbc.pool.OracleDataSource" was used,  the deployment fails with error

Deployment failed: Nested exception
Resolution:
Base Exception:
java.rmi.RemoteException
deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Error initializing ejb-module;
Exception jdbc/<DSNAME> did not contain a cmt-dataSource/ejb-datasource. deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Error initializing ejb-module;
Exception jdbc/<DSNAME> did not contain a cmt-dataSource/ejb-datasource

Changes

Cause

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