Oracle: TNS-12560: TNS:protocol adapter error

[Former Member]

Mr.

somebody is more background on these logs, added that the SAP system was disconnected in these two occasions

thanks

***********************************************************************

Fatal NI connect error 12518, connecting to:

(DESCRIPTION=(ADDRESS=(COMMUNITY=SAP.WORLD)(PROTOCOL=TCP)(HOST=ckqerp)(PORT=1527))(CONNECT_DATA=(SID=KRQ)(GLOBAL_NAME=KRQ.WORLD)(CID=(PROGRAM=C:\usr\sap\KRQ\DVEBMGS00\exe\disp+work.EXE)(HOST=CKQERP)(USER=SAPServiceKRQ))))

VERSION INFORMATION:

TNS for 64-bit Windows: Version 10.2.0.1.0 - Production

Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 10.2.0.1.0 - Production

Time: 22-DEC-2011 07:52:27

Tracing not turned on.

Tns error struct:

ns main err code: 12564

TNS-12564: TNS:connection refused

ns secondary err code: 0

nt main err code: 0

nt secondary err code: 0

nt OS err code: 0

***********************************************************************

Fatal NI connect error 12560, connecting to:

(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleKRQ)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=KRQ)(CID=(PROGRAM=C:\usr\sap\KRQ\SYS\exe\uc\NTAMD64\brconnect.exe)(HOST=CKQERP)(USER=SAPServiceKRQ))))

VERSION INFORMATION:

TNS for 64-bit Windows: Version 10.2.0.1.0 - Production

Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 10.2.0.1.0 - Production

Time: 06-JAN-2012 02:09:25

Tracing not turned on.

Tns error struct:

ns main err code: 12560

TNS-12560: TNS:protocol adapter error

ns secondary err code: 0

nt main err code: 0

nt secondary err code: 0

nt OS err code: 0

[former_member188883]

Hi Ronald,

We will have an entry on the alert.log file every time a client connection of any kind fails to complete or is aborted.

One way to minimize the impact is by using the parameter SQLNET.INBOUND_CONNECT_TIMEOUT (default to 60 seconds on 10gR2 and 11g) but, sometimes, this value is not adequate.

To fix the problem you could increase the value of SQLNET.INBOUND_CONNECT_TIMEOUT on the listener.ora and the sqlnet.ora file located on the server side.If you already have a value you have considered adequate, you might want to add the following line on your listener.ora file:

DIAG_ADR_ENABLED_listener_name=OFF

This line will hide the error on the alert.log file and the error will be posted on the $ORACLE_HOME/network/log/sqlnet.log file

Regards,

Deepak Kori

[former_member204746]

First of all, Oracle 10.2.0.1.0 was never supported by SAP. upgrade to at least 10.2.0.5, or better yet, Oracle 11.2.0.2.

As for your error, maybe you oracle "sessions" or "processes" parameters are not high enough, refer to SAP note 830576.

also look into your alert_SID.log to see if an error occurred at DB level at the exact same time.