Fatal NI connect error 12170

在数据库升级到11g之后，发现alert log里经常会有下面的报错信息，查看mos(1286376.1)后发现这个问题是由于Automatic Diagnostic Repository(ADR)中的 Oracle Net diagnostic在默认的情况下是开启的，当数据库和客户端的连接超过特定时间，就会把这样的信息写入到alert日志中，如果不是特别频繁出现，我想应该是没关系的

Fatal NI connect error 12170.

  VERSION INFORMATION:
        TNS for Solaris: Version 11.2.0.3.0 - Production
        Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production
        TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production
  Time: 04-DEC-2014 12:40: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
    
TNS-00505: Operation timed out
    nt secondary err code: 145
    nt OS err code: 0
  Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=.....)(PORT=2764))
Thu Dec 04 12:41:49 2014

当然，如果不想在alert 里看到这些信息，可以通过下面设置：
You may choose to revert from the new Automatic Diagnostic Repository (ADR) method to prevent the Oracle Net diagnostic details from being written to the alert log(s) by setting the following Oracle Net configuration parameters:

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

然后reload或restart 监听


PS:第一次写技术blog，当练练手

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/21560888/viewspace-1716958/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/21560888/viewspace-1716958/