You're being bitten by connection pooling. The algorithm doesn't properly
release connections on errors that are non-recoverable, such as when
communication to the server is lost.
To simulate the problem, build a fat client, nail up a connection, begin
performing queries and recycle the server. Make sure not to fix the
connection, but continue outputting errors. You should see the same
behavior.
--
Michael D. Long
"Chuck" <chuckh_nospam_at_softhome.net> wrote in message
news:Xns95647DC197927chuckhnospamsofthome_at_130.133.1.4...
> Can anyone explain why this happened.
>
> A web application started returning TNS-12535 last weekend. The app
> connects to the database through a Microsoft COM object. I logged on to
> the same web server and had no problems connecting to the same db with
> sqlplus and with the Oracle ODBC test program. We recycled the server.
> Then the error message switched to ORA-12154. Again I had no problems
> connecting with either sqlplus or ODBC test program.
>
> Around the time all this began, our primary names server was also taken
> down (intentionally for an OS upgrade). The secondary one seemed to be
> working fine as evidenced by sqlplus working.
>
> The server in question has no tnsnames.ora file and no other names
> resolution method configured other than ONAMES.
>
> Versions all the way around are 8.1.7.4, client, database, listeners, and
> names servers.
>
> Any ideas?
>
> I have seen similar things happen in the past. Unexplainable connection
> errors when sqlplus works fine. Recycling IIS on the web server is
> usually all that's needed to fix the problem.
>
> --
> Chuck
> Remove "_nospam" to reply by email
Received on Tue Sep 14 2004 - 20:29:52 CDT
