Connection Pool Failure

This kind of issues are common for Weblogic admins, you need to tackle with wise tricks. While configuring for a fresh WebLogic domain you might encounter this issue, While giving the connection pool parameters, It will show the following error in the WebLogic Server logs: <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "myds1": ORA-00257: archiver error. Connect internal only, until freed.>  <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'myds1' due to error weblogic.application.ModuleException: .weblogic.application.ModuleException:         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)

        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)

        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)

        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)

        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)

        Truncated. see log file for complete stacktrace

Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: ORA-00257: archiver error. Connect internal only, until freed.

        at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:263)

        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)

        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)

        at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:244)

        at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1109)

        Truncated. see log file for complete stacktrace

Trouble shooting 

You might wonder such scenario don't be panic when you got such Warning/Error, Relax, You have alternative way of testing your Oracle Database connectivity from the WebLogic installation machine. Remember that Oracle Thin Driver does not refer the 'tnsnames.ora' file. If your WebLogic machine may not have Oracle client connectivity even thought you can identify the connectivity to the database, It is a powerful command line utility, that gives you the connection details. You could do this drill before trying to configuring your DataSource with a Database details that must go for a Connection pool parameters. Some times this might be interview question for WebLogic Admins " How do you know the given database parameters are suitable for configuring a connection pool or not?"

The simple way answering this question is using command line utility provided by Oracle WebLogic "dbping".

The dbping command Usage

java utils.dbping DB2B  [-d dynamicSections] USER PASS HOST:PORT/DBNAME

or     java utils.dbping DERBY        USER PASS HOST:PORT/DBNAME

or     java utils.dbping JCONN2       USER PASS HOST:PORT/DBNAME

or     java utils.dbping JCONN3       USER PASS HOST:PORT/DBNAME

or     java utils.dbping JCONNECT     USER PASS HOST:PORT/DBNAME

or     java utils.dbping INFORMIXB    USER PASS HOST:PORT/DBNAME/INFORMIXSERVER

or     java utils.dbping MSSQLSERVERB USER PASS HOST:PORT/[DBNAME]

or     java utils.dbping MYSQL        USER PASS [HOST][:PORT]/[DBNAME]

or     java utils.dbping ORACLEB      USER PASS HOST:PORT/DBNAME

or     java utils.dbping ORACLE_THIN  USER PASS HOST:PORT:DBNAME

or     java utils.dbping POINTBASE    USER PASS HOST[:PORT]/DBNAME

or     java utils.dbping SYBASEB      USER PASS HOST:PORT/DBNAME