Fatal NI connect error 12170.

最新推荐文章于 2024-08-04 09:00:00 发布

奋斗的小鸟-贵在坚持

最新推荐文章于 2024-08-04 09:00:00 发布

阅读量1.1k

点赞数

分类专栏：常见数据库异常处理 Oracle 技术文档 Oracle 技术分享文章标签：数据库 oracle

Oracle 技术分享同时被 3 个专栏收录

51 篇文章

订阅专栏

Oracle 技术文档

40 篇文章

订阅专栏

常见数据库异常处理

17 篇文章

订阅专栏

本文讨论了在Oracle数据库升级至11.2.0.3版本后出现的连接超时错误，并提供了通过调整Oracle Net配置参数来解决此问题的方法。包括修改sqlnet.ora和listener.ora文件中的DIAG_ADR_ENABLED参数，以及重启监听器以应用更改。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

前段时间将数据库升级到了11.2.0.3，查看alert.log有发现连续报以下错误信息：

 
        1
       
        2
       
        3
       
        4
       
        5
       
        6
       
        7
       
        8
       
        9
       
        10
       
        11
       
        12
       
        13
       
        14
       
        15
       
        16
       
        17
       
        18
       
        19
       
        20
       
        21
       
        Fatal 
        NI 
        connect 
        error
         
        12170.
       
        VERSION 
        INFORMATION
        :
       
        TNS 
        for
         
        Linux
        :
         
        Version
         
        11.2.0.3.0
         
        -
         
        Production
       
        Oracle 
        Bequeath 
        NT 
        Protocol 
        Adapter 
        for
         
        Linux
        :
         
        Version
         
        11.2.0.3.0
         
        -
         
        Prod
       
        uction
       
        TCP
        /
        IP 
        NT 
        Protocol 
        Adapter 
        for
         
        Linux
        :
         
        Version
         
        11.2.0.3.0
         
        -
         
        Production
       
        Time
        :
         
        27
        -
        JUL
        -
        2013
         
        16
        :
        25
        :
        30
       
        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
        =
        192.168.3.201
        )
        (
        PORT
        =
        52543
        )
        )
       
        Sat 
        Jul
         
        27
         
        16
        :
        25
        :
        32
         
        2013

上MOS查到文档 ID 1286376.1说这个信息大多数是正常的与超时有关的消息，这个消息指出了一个经历了超时的客户端，这个客户端试图连接但是没有得到响应，或者由于被连接的主机没有响应导致的一个已建立的连接失败，这个信息被写到alert.log里是因为使用了11g新的ADR自动诊断资料库功能，那个功能是被默认启用的，原文如下：

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:
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 AIX: nt secondary err code: 78:
ETIMEDOUT 78 /* Connection timed out */

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

Description: A connection attempt fa

iled 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. See (Doc ID 454927.1).

根据MOS提供的解决方法是设置Oracle Net的配置参数使它的诊断追踪信息不再写入到alert.log中，需要修改两个地方：

1.在服务端的sqlnet.ora文件中设置以下参数

1

DIAG_ADR_ENABLED = OFF

2.在服务端的listener.ora中设置以下参数

1

DIAG_ADR_ENABLED_ < listenername > = OFF

这个<listenername>根据你实际的监听名称来替换，比如你的监听名称叫'LISTENER'，那么这个参数就设置为

1

DIAG_ADR_ENABLED_LISTENER = OFF

3.reload或者restart监听使配置生效

1

lsnrctl reload