TNS Errors
jayb...@my-deja.com
database continuously over a span of 10 to 12 hours.
Any help or clues would be terrific.
Here is one of the many errors in the SQLNET.LOG:
Fatal OSN connect error 12547, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle80)
(ARGV0=oracle80ORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=
(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=XXXX.exe)
(HOST=XXXXX)(USER=XXXXX))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 2.3.4.0.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version
2.3.4.0.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows:
Version 2.3.4.0.0 - Production
Time: 01-NOV-00 16:37:52
Tracing not turned on.
Tns error struct:
nr err code: 12206
TNS-12206: TNS:received a TNS error during navigation
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 517
TNS-00517: Lost contact
nt secondary err code: 0
nt OS err code: 0
This will cause the application running to catch the following error:
Error, cd: 12537
Message: ODBC Message
Nbr: 12537
State: S1000
Desc: [Oracle][ODBC Oracle Driver][Oracle OCI]ORA-12537:
TNS:connection closed.
Error, cd: 12542
Message: ODBC Message
Nbr: 12542
State: S1000
Desc: [Oracle][ODBC Oracle Driver][Oracle OCI]ORA-12542: TNS:address
already in use.
It will catch about 5 or so of the 12537's, then a couple of the
12542's.
Thanks in advance for your help,
JB
Sent via Deja.com http://www.deja.com/
Before you buy.
joc...@my-deja.com
Description of the error messages
TNS-12537 TNS:connection closed
Cause: "End of file" condition has been reached; partner has
disconnected. This is an informational message.
Action: No action required.
TNS-12542 TNS:address already in use
Cause: Specified listener address is already being used.
Action: Start your listener with a unique address.
It sounds as if you may be having intermittant network problems or your
server listners may be quitting and restarting. These should both be
eminently recoverable error conditions, so I wouldn't worry too much.
--
Justin Cave - Oracle ODBC Development
Opinions expressed herein are my own and may not reflect those of
Oracle Corporation.
jayb...@my-deja.com
during a database connection??
Also, is there anything obvious that would be causing the listeners to
go down and come back up on their own?
Thanks in advance for the excellent help,
JB
In article <8ts4v8$a7m$1...@nnrp1.deja.com>,
joc...@my-deja.com
jayb...@my-deja.com wrote:
> So would this be the error generated if a network connection is
dropped
> during a database connection??
That's certainly a possibility. Any time the server or network dropped
a connection, I'd expect to see this error. If this only happens a few
times a day under heavy load, I'd tend to view this as a reasonable
state of affairs.
>
> Also, is there anything obvious that would be causing the listeners to
> go down and come back up on their own?
Not that I can think of, though I'm far from a competent DBA. From the
description you give, it sounds like there's a small window between
whatever event causes the connection to be dropped where OCI/TNS may be
a bit confused and then settles down. I assume that there is some
cacheing of network information being done by TNS and/or OCI. It's
possible that these events cause the cached data and the actual network
to be briefly out of sync but then are quickly corrected.