Re: sqlnet.log file growing with this error.

From: Pete Sharman <psharman_at_us.oracle.com>
Date: Wed, 21 Apr 1999 14:18:16 -0700
Message-ID: <371E4098.C95060D1@us.oracle.com>

The error stack you're getting is:

Error: ORA 12206
Text: TNS:received a TNS error during navigation

Cause: Internal navigation error because of an unexpected TNS error. Action: Look at the log file to find the TNS error. If necessary, turn

on tracing and repeat the operation.

OK, so what's further down the stack?

Error: ORA 12545
Text: TNS:name lookup failure

Cause: A protocol specific ADDRESS parameter cannot be resolved. Action: Ensure the ADDRESS parameters have been entered correctly;

The most likely incorrect value is the node name.

Error: ORA 12560
Text: TNS:protocol adapter error

Cause: A generic protocol adapter error occurred. Action: Check addresses used for proper protocol specification. Before

        reporting this error, look at the error stack and check for lower level
        transport errors.For further details, turn on tracing and reexecute the
        operation. Turn off tracing when the operation is complete.

Error: TNS 00515
Text: Connect failed because target host or object does not exist

Cause: The address specified is not valid, or the program being connected to does not exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the

     most likely incorrect parameter is the node name.  Ensure that the
     executable for the server exists (perhaps "oracle" is missing.)

The last three all point to address parameter issues. Can you post the tnsnames.ora so we can see that?

HTH. Pete

Michael Rothwell wrote:

> My sqlnet.log file has been growing too fast. In looking at the file, I
> keep getting the same error. None of the users have noticed any problem,
> but the log file will grow 4M per day.
>
> Here is the message:
>
> ***********************************************************************
> Fatal OSN connect error 12545, connecting to:
>
> (DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=oracle)(ARGV0=oracle)(ARGS='(DESCR
> IPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')(DETACH=NO))(CONNECT_DATA=(CID=(PRO
> GRAM=)(HOST=i3107ps3)(USER=insight))))
>
> VERSION INFORMATION:
> TNS for HPUX: Version 2.1.4.1.0 - Production
> Unix Domain Socket IPC NT Protocol Adaptor for HPUX: Version 2.1.4.1.0
> - Production
> Oracle Bequeath NT Protocol Adapter for HPUX: Version 2.1.4.1.0 -
> Production
> TCP/IP NT Protocol Adapter for HPUX: Version 2.1.4.1.0 - Production
> Time: 21-APR-99 13:20:22
> Tracing not turned on.
> Tns error struct:
> nr err code: 12206
> TNS-12206: Message 12206 not found; No message file for
> product=NETWORK, facility=TNS
> ns main err code: 12545
> TNS-12545: Message 12545 not found; No message file for
> product=NETWORK, facility=TNS
> ns secondary err code: 12560
> nt main err code: 515
> TNS-00515: Message 515 not found; No message file for product=NETWORK,
> facility=TNS
> nt secondary err code: 2
> nt OS err code: 0
>
> The listener log is OK. Users are always able to connect to the instance.
> What is happening here?
>
> Thanks.
>
> --
> Michael A. Rothwell
> Oracle DBA/Oracle Web Applications Developer
>
> Views expressed here are not those of my company
> No - Actually - Since I am independent, They are the views of my company.

Regards

Pete

Peter Sharman                             Email: psharman_at_us.oracle.com
WISE Course Development Manager           Phone: +1.650.607.0109 (int'l)
Worldwide Internal Services Education            (650)607 0109 (local)

San Francisco

SQL> select standard_disclaimer, witty_remark 2 from company_requirements;

Opinions are mine and do not necessarily reflect those of Oracle Corporation

"Controlling application developers is like herding cats." Kevin Loney, ORACLE DBA Handbook
"Oh no it's not! It's much harder than that!" Bruce Pihlamae, long term ORACLE DBA

Received on Wed Apr 21 1999 - 16:18:16 CDT