ORA-3136: Fatal NI connect error 12170.

Today, in the log file of a server, the following information is found: It seems to be an error, but it does not affect the operation of the database. However, after all, the error is reported. If you look uncomfortable, study it.

Fatal NI connect error 12170.

Version information:
TNS for Linux: Version 11.1.0.7.0-Production
Unix Domain Socket ipc nt Protocol Adaptor for Linux: Version 11.1.0.7.0-Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.1.0.7.0-Production
TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.7.0-Production
Time: 08-NOV-2011 13:57:10
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 = IP) (PORT = 51345 ))
View mos and find related articles about this error.
Fatal NI connect error 12170 ', 'tns-12535: TNS: operation timed out 'reported in 11g Alert Log [ID 1286376.1]
I made some summaries and made a record for myself. I also gave a reference to friends who cannot access mos.
1. Applicability
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. Cause
These time out related messages are mostly informational in nature. the messages indicate the specified client connection (identified by the 'client address: 'details) has experienced a time out. the 'nt secondary err Code' identifies the underlying network transport, such as (TCP/IP) timeout limits after a client has 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
For the Linux operating system: nt secondary err code: 110
ETIMEDOUT 110 Connection timed out
For the HP-UX system: nt secondary err code: 238:
ETIMEDOUT 238
For Windows based platforms: nt secondary err code: 60 (which translates to Winsock Error: 10060)
Description: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
The reason the messages are written to the alert log is 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 the ADR diag for the Listener component, set following parameter in the server's listener. ora:
DIAG_ADR_ENABLED _ = OFF
-Where the wocould be replaced with the actual name of the configured listener (s) in the listener. ora configuration file. for example, if the listener name is 'listener ', the parameter wocould read:
DIAG_ADR_ENABLED_LISTENER = OFF
-Reload or restart the TNS Listener for the parameter change to take effect.
Note: This problem occurs because Oracle Net Diagnostic in the diagic diagnostic Repository is enabled by default. When the connection between the database and the client exceeds the specified time, this information will be written into the alert Log, so this is not a fatal problem, if occasionally appears, you can ignore errors that are somewhat similar to this ORA-3136