Fatal NI Connect error 12170.

Environment: Oracle 11.2.0.4 R2 RAC

Today, in the log file alter log of the RAC two server, the following information is found:

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

Fatal NI Connect error 12170.

VERSION Information:

TNS for Linux:version 11.2.0.4.0-production

Oracle bequeath NT Protocol Adapter for Linux:version 11.2.0.4.0-production

TCP/IP NT Protocol Adapter for Linux:version 11.2.0.4.0-production

time:21-may-2016 20:52:15

Tracing not turned on.

Tns error struct:

NS Main ERR code:12535

Tns-12535:tns:operation timed out

NS Secondary Err code:12560

NT Main ERR code:505

Tns-00505:operation timed out

NT Secondary Err code:110

NT OS Err code:0

Client Address: (address= (PROTOCOL=TCP) (host=172.16.6.7) (port=41125))

Sat May 21 20:55:11 2016

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

View MoS and have the pleasure of discovering related articles about this error

Fatal NI Connect error 12170′, ' tns-12535:tns:operation timed out ' reported in 11g Alert Log [ID 1286376.1]

Do a few summaries, is to make a record for themselves, but also to the friends can not access MOS a reference

1. Scope of application

Oracle Net services-version:11.1.0.6 to 11.2.0.2-release:11.1 to 11.2

Oracle server-enterprise edition-version:11.1.0.6 to 11.2.0.2 [release:11.1 to 11.2]

Information in this document applies to any platform.

2, the cause of the problem

These time out related messages is mostly informational in nature. The messages indicate the specified client connection (identified by the ' Client address: ' Details ' have experienced a time  Out. The ' NT Secondary ERR code ' identifies the underlying network transport, such as (TCP/IP) timeout limits after a client ha s abnormally terminated the database connection.

The ' NT Secondary Err code ' translates to underlying network transport timeouts for the following Operating Systems:

For the Solaris system:nt secondary err code:145:

#define ETIMEDOUT 145/* Connection timed out */

For the Linux operating system:nt secondary err code:110

Etimedout Connection timed out

For the HP-UX system:nt secondary err code:238:

Etimedout 238/* Connection timed out * *

For Windows based Platforms:nt secondary err code:60 (which translates to Winsock error:10060)

DESCRIPTION:A connection attempt failed because the connected party does not properly respond after A period of time, or Established connection failed because connected host have failed to respond.

The reason the messages is written to the alert log was related to the use of the new 11g Automatic Diagnostic Repository (ADR) feature being enabled by default.

3, solve the problem

To revert-to-Oracle Net server tracing/logging, set following parameter in the Server ' s Sqlnet.ora:

diag_adr_enabled = OFF

Also, to-back out of the ADR diag for the Listener component, set following parameter in the server ' s Listener.ora:

diag_adr_enabled_<listenername> = OFF

-Where The <listenername> would is replaced with the actual name of the the configured listener (s) in the Listener.ora  Configuration file. For example, if the listener name is ' listener ', the parameter would read:

Diag_adr_enabled_listener = OFF

-reload or restart the TNS Listener for the parameter change to take effect.

Description: This issue is due to the fact that the Oracle Net Diagnostic in automatic Diagnostic repository is turned on by default, and when the database and client connections exceed a certain time, such information is written to the alert log. So this is not a fatal problem, and if it happens occasionally, you can ignore a bit of this ora-3136 error

Simplified steps:

1. Add the following in the "/u01/app/11.2/grid/network/admin/listener.ora" file:

Diag_adr_enabled_listener = OFF

Diag_adr_enabled_listener_scan1 = OFF

2. Add the following in the "/u01/app/11.2/grid/network/admin/sqlnet.ora" file:

diag_adr_enabled = OFF

3, create "/u01/app/oracle/product/11.2/db_1/network/admin/sqlnet.ora" file, the content is as follows:

NAMES. Directory_path= (TNSNames, Ezconnect)

diag_adr_enabled = OFF

Default_sdu_size = 8192

4, single instance re-import configuration can take effect

Lsnrctl Reload

5. Oracle 11g R2 RAC is managed using SRVCTL

Srvctl Stop Listener

Srvctl Start Listener

This article from "Travel Life" blog, declined reprint!

Fatal NI Connect error 12170.