Reconnect after Oracle maintenance

  • Thread starter Thread starter n.prabhakar
  • Start date Start date
N

n.prabhakar

Hi,

I am facing a similar problem as described in a much older post <a
href="http://tinyurl.com/y27abp"/>.

We are using .NET 1.1 with the MS Oracle ADO.NET driver. After reading
the above post, we had disabled Pooling on our application. After that
the application worked fine for a few restarts of the DB (after
maintenance), but once in a while it is still not able to recover, and
seemingly continue to use some older connection. Is there some other
driver level caching of the older corrupt connections that are retained
in the "Open" state as described by the post i have mentioned.

When the DB recovers, our application throws the following exception,
and even if we retry, continues to throw this exception:
"System.Data.OracleClient.OracleException: ORA-12154: TNS:could not
resolve service name"

Thanks
 
I used to have that problem. It was always a problem
with the tnsnames.ora and/or sqlnet.ora files.

I worked for a huge company that had a standard
sqlnet.ora file that they would use as the default
on everyone's machine, and it overrode the tnsnames.ora
file, no matter what you put in the tnsnames.ora file.

If that wasn't the problem, then it was the tnanames.ora
file not having the definition of the server I was using.

I'm not sure that's your problem, if it's intermittent.
But you can check it and see.

Robin S.
 
Back
Top