Oracle OCI driver stops working after a while of disuse

Question

I am using wl server 8.1, oracle oci driver (oracle 9i client), on solaris.
When i create a connection pool using the oci driver, it connects, and i
test it, and the tests run fine.
The Application works for a few days. Then eventually after disuse, say over
the weekend, I get exceptions in the log (the message is at end of email).
This is because it gives me a sql exception saying it cannot resolve the
service name. The database is up and running, confirmed.
I tried testing the connection pool manually through the console, and it
failed with the service name exception. But it would connect fine when i
used sqlplus to connect to the databse, using the same service name.
Why does this deteriorate over time? Is there a specific test that would
prevent this from happening?
Once i restart the weblogic server, the connection pool connects fine. But
this is not a solution, since I can't be restarting the server all the time.
Any one got any ideas?
-Ayan
------------WEBLOGIC MANAGED SERVER LOG----------
####<Mar 27, 2004 4:20:57 AM EST> <Error> <JDBC><<WLS Kernel>> <>
<BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "CRCPool2" failed
with exception: "java.sql.SQLException: ORA-03113: end-of-file on
communication channel
".>
####<Mar 27, 2004 4:20:57 AM EST> <Info> <JDBC> <<WLS Kernel>> <>
<BEA-001128> <Connection for pool "CRCPool2" closed.>
---------- and then eventually this----------
####<Mar 28, 2004 4:33:11 AM EST> <Warning> <JDBC> <<WLS Kernel>> <>
<BEA-001129> <Received exception while creating connection for pool
"CRCPool2": ORA-12154: TNS:could not resolve service name
>

Answer 1

Ayan wrote:
I am using wl server 8.1, oracle oci driver (oracle 9i client), on solaris.
When i create a connection pool using the oci driver, it connects, and i
test it, and the tests run fine.
The Application works for a few days. Then eventually after disuse, say over
the weekend, I get exceptions in the log (the message is at end of email).
This is because it gives me a sql exception saying it cannot resolve the
service name. The database is up and running, confirmed.
I tried testing the connection pool manually through the console, and it
failed with the service name exception. But it would connect fine when i
used sqlplus to connect to the databse, using the same service name.
Why does this deteriorate over time? Is there a specific test that would
prevent this from happening?
Once i restart the weblogic server, the connection pool connects fine. But
this is not a solution, since I can't be restarting the server all the time.
Any one got any ideas?
-AyanHi. Is there a firewall between the weblogic server and DBMS? There is
a problem with OCI losing connectivity to the DBMS. OCI may be keeping
a socket open as long as the process (weblogic) is running.
Joe
------------WEBLOGIC MANAGED SERVER LOG----------
####<Mar 27, 2004 4:20:57 AM EST> <Error> <JDBC><<WLS Kernel>> <>
<BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "CRCPool2" failed
with exception: "java.sql.SQLException: ORA-03113: end-of-file on
communication channel
".>
####<Mar 27, 2004 4:20:57 AM EST> <Info> <JDBC> <<WLS Kernel>> <>
<BEA-001128> <Connection for pool "CRCPool2" closed.>
---------- and then eventually this----------
####<Mar 28, 2004 4:33:11 AM EST> <Warning> <JDBC> <<WLS Kernel>> <>
<BEA-001129> <Received exception while creating connection for pool
"CRCPool2": ORA-12154: TNS:could not resolve service name