Connection recovery problem with OracleConnection

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Michael

I am not sure about your question. Do you mind providing more details
Are you saying that you can open a connection to the Oracle database sometimes, but not some other times? OR a successfully opened connection just throws this error when you try to use it later

-Manish
 
Hi,

I'm using ADO.Net in C# with Oracle9i Release 9.2.0.4.0
when loosing the connection with the Oracle database server the connections
doesn't recover and always returning the following exception even when the
connection has been restore:
"ORA-03114: not connected to ORACLE". I'm closing the connection properly in
that it will return to the connection pool. Here is an example code:

using(OracleConnection conn = new OracleConnection(connectionString))
{
conn.Open();
using(OracleCommand cmd = new OracleCommand(sql, conn))
{
object obj = cmd.ExecuteScalar();
}
}

This should close the connection properly. In the MSDN it is mention that if
the connection pooler detect that the connection with the server has been
severed it will remove the connection from the connection pool. It appears
that this is not happening an I always get bad connections from the pool,
even after the connection with the database server has been restore. How can
I solve this? What is the proper way to recover from connection lost with
database server?

Thanks,
Michael.
 
Manish,

Here is a scenario:
I'm using ado.net to open connection with the database server. I use this
connection to perform an sql select statement, when finish I close the
connection properly. I repeat this process X times. While this is happening
the network connection with the database server is lost (the network cable
has been plugged out), after the network connection has been resorted, I
still get an error message: "ORA-03114: not connected to ORACLE".

In the MSDN it is mention that if the connection pooler detect that the
connection with the server has been severed it will remove the connection
from the connection pool. It appears that this is not happening an I always
get bad connections from the pool, even after the connection with the
database server has been restore

Michael.

Manish Jadhav said:
Michael,

I am not sure about your question. Do you mind providing more details?
Are you saying that you can open a connection to the Oracle database
sometimes, but not some other times? OR a successfully opened connection
just throws this error when you try to use it later?
 
Michael,
I am sorry this one is my fault and it is a very bad bug. The problem here
is that our pooler fails to understand that a 03114 exception means we
should not put the connection back in the pool. We have a QFE that fixes
this problem by discarding the connection in the following Oracle
exceptions. Please let me know if you know of any other exceptions that also
result in a connection no longer being valid.

oracle exceptions checked
case 18: // max sessions exceeded,
case 19: // max session licenses exceeded
case 24: // server is in single process mode
case 28: // session has been killed
case 436: // oracle isn't licensed
case 1012 //not logged on error
case 1033: // startup/shutdown in progress
case 1034: // oracle not available
case 1075: // currently logged on
case 3113: // end-of-file on communication channel
case 3114: // not connected to ORACLE
case 12154: // can't resolve service name
case 12xxx //any error starting with 12 thousand

To get the fix please contact PSS directly and request QFE 830173
 
Back
Top