Investigate JDBC Problems (Continued)

It is likely that the login or password is not valid. It is also possible that something else is invalid in the configuration or that the database is not available.

If you see an error message similar to this one, correct the database name:

<06.11.2003 14.21 Uhr CET> <Warning> 
  <JDBC> <BEA-001129> 
<Received exception while creating 
  connection for pool "myPool": 
E/A-Exception: Connection refused
  (DESCRIPTION=(TMP=)(VSNNUM=
  153092352)(ERR=12505)
(ERROR_STACK=(ERROR=(CODE=12505)
  (EMFI=4))))>
<06.11.2003 14.21 Uhr CET> <Error> 
  <JDBC> <BEA-001150> 
<Connection Pool "myPool" deployment 
  failed with the following error:
  0:Could not create pool connection. 
  The DBMS driver exception was: 
E/A-Exception: Connection refused(
  DESCRIPTION=(TMP=)(VSNNUM=
  153092352)
(ERR=12505)(ERROR_STACK=(ERROR=
  (CODE=12505)(EMFI=4)))).>

If you see an error message similar to this one, check the tns entry or your environment settings like PATH or LD_LIBRARY_PATH:

####<Apr 17, 2003 1:58:44 PM CEST> 
  <Error> <JDBC> <mydomain> 
  <myserver> <main> 
    <kernel identity> 
  <> <001060> 
<Cannot startup connection pool 
"myPool" weblogic.common.
  ResourceException:
  weblogic.common.ResourceException: 
  Could not create pool connection. 
  The DBMS driver exception was:
  java.sql.SQLException: Io 
  exception: The Network Adapter 
  could not establish the connection

On the Microsoft Windows platform, PATH needs to point to the client and OCI libraries; in Unix environments, LD_LIBRARY_PATH needs to point to the directories where the client installation copied the client and oci libraries.

If the tnsnames.ora file or ORACLE_HOME is not set correctly, this Oracle error will be thrown:

ORA-12154: TNS could not resolve 
  service name

Ensure that your ORACLE_HOME environment variable points to the correct directory and the tnsnames.ora file is stored in the correct directory. Also verify through sql-plus if a connect to this database is successful. (See Resources for additional information on ORA-12154 and related Oracle SQL errors.)

A related error message is ORA-24327, which is caused most likely by a configuration problem:

LOGIN ERROR CODE: 24327
  <Error> <JDBC Connection Pool> 
  Cannot startup connection pool 
  "xxxPool" weblogic.common.
  ResourceException: 
  Could not create pool connection. 
  The DBMS driver exception was: 
  java.sql.SQLException: ORA-24327: 
  need explicit attach before 
  authenticating a user.

Incorrect locale settings may lead to error messages like this one:

weblogic.management.
  DeploymentException: 
    Error creating 
  connection pool myConnectionPool: 
  0:Unable to load locale categories

Ensure that you have set the correct locale environment before starting WebLogic Server. Double-check by starting a database client in the same environment, and check if your locale works there.

If the database was intermittently down, a connection reset or refresh will happen if the TestConnectionsOnReserve property is set to true and the connection test query fails. You will find related messages in the WebLogic Server log file, similar to this one:

ORA-03113 end-of-file on 
  communication channel and/or 
  ORA-01012 not logged on: 

This message is for your information only, and, as long as the connection could be created successfully during the refresh or reconnect, it is harmless (see Listing 1).