Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: "Could not create pool connection" ELFCLASS64 error (WebSphere with Oracle)

Updated on August 28, 2019

Symptom

When using WebSphere with Oracle, you may receive the following error when you start the application server:

<January 23, 2007 11:14:05 CDT> <Error> <JDBC> <BEA-001150> <Connection Pool “pega_rep1” deployment failed with the following error:
0:Could not create pool connection. The DBMS driver exception was: /u01/app/oracle/product/10.2.02/lib/libocijdbc/10.so: ld.so.1:java: fatal: /u01/app/oracle/product/10.2.02/lib/libocijdbc/10.so: wrong ELF class: ELFCLASS64.>
<January 23, 2007 11:14:05 CDT> <info> <JDBC> <BEA-01156> <Stack trace associated with message 01150 follows:
weblogic.common.resourcepool.ResourceSystemException: Could not create pool connection. The DBMS driver exception was:
u01/app/oracle/product/10.2.02/lib/libocijdbc10.so: ld.so: java:
fatal: /u01/app/oracle/product/10.2.02/lib/libocijdbc.so: wrong ELF class: ELFCLASS64 at weblogic.jdbc.common.internal.ConnectionEnvFactory.MakeConnection (ConnectionEnvFactory.java:214)
at weblogic.jdbc.common.internal..ConnectionEnvFactory.createResource (ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources (ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources (ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start (ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart (ConnectionPool.java:1018)

This error may appear when you: 

  • Install or upgrade to a new version of Process Commander.
  • Upgrade from Oracle 9i to Oracle 10g.

Note: These are two examples of when this error can occur; you may receive this error under other circumstances.

 

Solution

Resolution

This error occurs because the LD_LIBRARY_PATH Unix environment variable points to the 64-bit Oracle library files. It should point to the 32-bit Oracle library files, as follows:

LD_LIBRARY_PATH=$ORACLE_HOME/lib32

From the Oracle command line, change the environment variable as follows:

For C shell users:

setenv LD_LIBRARY_PATH=$ORACLE_HOME/lib32

For Bourne or Korn shell users

$ LD_LIBRARY_PATH=$ORACLE_HOME/lib32

For more information, see the Oracle Metalink note 301956.1 at:

WWWhttps://metalink.oracle.com/metalink/plsql/f?
p=130:14:12742755642302416577::::p14_database_id,p14_docid ,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,301956.1,1,1,1,helvetica

Article originally written 2/9/2007. 

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us