My Oracle Support Banner

Oracle Net SQLNET.SEND_TIMEOUT and SQLNET.RECV_TIMEOUT Parameters and errors ORA-12170 TNS-12535 ORA-12609 ORA-12608 (Doc ID 1335630.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Net Services - Version to [Release 11.1 to 12.1]
Oracle Net Services - Version to [Release 12.1]
Oracle Database - Enterprise Edition - Version to [Release 12.1]
Information in this document applies to any platform.
***Checked for Relevancy on 19-NOV-2014***


The Alert log is reporting the error codes.
(Please note from 11g onwards Sqlnet.log for RDBMS side, reports net errors in the Alert.log due to ADR)

Fatal NI connect error 12170.

TNS for HPUX: Version - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version - Production
TCP/IP NT Protocol Adapter for HPUX: Version - Production
Time: 02-JUL-2011 19:02:18
Tracing not turned on.

Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12609
nt main err code: 0
nt secondary err code: 0
nt OS err code:

Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=XX.XXX.XX.XX)(PORT=53678))

These show the failure is just in the Network Session (NS) section of the Oracle Net Foundation Layer.There are no errors in the Network Transport(NT) section of the Oracle Protocol Support Layer, which report problems from underlying network issues. See Oracle documentation for further details on Oracle Net Foundation layer and Oracle Protocol Support.

When tracing a failing connection, Level 16 Oracle Net, shows similar to following:

[02-JUL-2011 19:03:43:551] nttfprd: entry
[02-JUL-2011 19:03:43:551] ntt2err: entry
[02-JUL-2011 19:03:43:551] ntt2err: soc 1120 error - operation=5, ntresnt[0]=530, ntresnt[1]=53, ntresnt[2]=0
[02-JUL-2011 19:03:43:551] ntt2err: exit
[02-JUL-2011 19:03:43:551] nttfprd: exit
[02-JUL-2011 19:03:43:551] nserror: entry
[02-JUL-2011 19:03:43:551] nserror: nsres: id=0, op=68, ns=12570, ns2=12560; nt[0]=530, nt[1]=53, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
[02-JUL-2011 19:03:43:551] nsbasic_brc: exit: oln=0, dln=0, tot=0, rc=-1
[02-JUL-2011 19:03:43:551] nioqrc: recv: packet reader error -> translated to IFCR_EOF
[02-JUL-2011 19:03:43:551] nioqer: entry
[02-JUL-2011 19:03:43:551] nioqer: incoming err = 12151
[02-JUL-2011 19:03:43:551] nioqce: entry
[02-JUL-2011 19:03:43:551] nioqce: exit
[02-JUL-2011 19:03:43:551] nioqer: returning err = 3113
[02-JUL-2011 19:03:43:551] nioqer: exit
[02-JUL-2011 19:03:43:551] nioqrc: exit
[02-JUL-2011 19:03:43:551] nioqds: entry
[02-JUL-2011 19:03:43:551] nioqds: disconnecting...

The highlighted error stack, does show an error in the NT section of the Oracle Protocol Support layer,
nt[1]=53. Client example used here is windows, so 53 maps to 

Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or
protocol error.

But this does not mean the issue is solely a TCP one.  Socket was attempted to be used and failed.


SQLNET.RECV_TIMEOUT and / or SQLNET.SEND_TIMEOUT set in the client / server SQLNET.ORA files


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.