Fatal NI connect error 12170

最新推荐文章于 2024-12-24 09:43:17 发布

原创最新推荐文章于 2024-12-24 09:43:17 发布 · 758 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

oracle 同时被 2 个专栏收录

6 篇文章

订阅专栏

rac

5 篇文章

订阅专栏

本文讨论了Oracle Net连接超时导致的错误信息及其原因，解释了NT次要错误代码对应的操作系统网络运输时间超时情况，并提供了修改sqlnet.ora和listener.ora文件以关闭ADR（Automatic Diagnostic Repository）功能的解决方案，最终通过重新加载或重启TNS Listener来应用更改。

1  出现问题
alert.log

Fatal NI connect error 12170.
  VERSION INFORMATION:

        TNS for Solaris: Version 11.2.0.1.0 - Production

        TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.1.0 - Production

  Time: 17-JUL-2013 05:26:23

  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
2 原因
Thesetimeout related messages are mostly informationalinnature. 
 The messages indicate the specified client connection (identified by the'Client address:'details) has experienced a
timeout.  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 timeoutsfor
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 110 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 (whichtranslates to Winsock Error:
 10060) 
  
Description:  A connection attempt failed because the connected party did not properly respond after a period oftime,
 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
 
注：主要由于ADR（Automatic Diagnostic Repository）默认开启Oracle Net diagnostic，并在连接超时记录到了ALERT.LOG中。
3 解决方案
修改 sqlnet.ora :
  
DIAG_ADR_ENABLED = OFF
  
修改 listener.ora:
  
DIAG_ADR_ENABLED_<listenername> = OFF
  
   - Where the <listenername> would be replaced with the actual name of the configured listener(s)inthe
 listener.ora configurationfile.  For example,ifthe listener name is'LISTENER',
 the parameter wouldread:
  
DIAG_ADR_ENABLED_LISTENER = OFF
  
-Reload or restart the TNS Listenerforthe parameter change to take effect.