Fatal NI connect error 12170

11.2.0.2的库两个节点的alert里均频繁出现如下信息：

***********************************************************************
Fatal NI connect error 12170.VERSION INFORMATION:TNS for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - ProductionTCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - ProductionOracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - ProductionTime: 15-NOV-2012 15:49:33Tracing not turned on.Tns error struct:ns main err code: 12535TNS-12535: TNS:operation timed outns secondary err code: 12560nt main err code: 505TNS-00505: Operation timed outnt secondary err code: 0nt OS err code: 0Client address: <unknown>
***********************************************************************
Fatal NI connect error 12514, connecting to:(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=db1)(PORT=1525))(ADDRESS=(PROTOCOL=TCP)(HOST=xx)(PORT=1525))(LOAD_BALANCE=yes))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=zjcs)(CID=(PROGRAM=oracle)(HOST
=dbdemo1)(USER=oracle))))VERSION INFORMATION:TNS for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - ProductionTCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - ProductionTime: 15-NOV-2012 16:09:34Tracing not turned on.Tns error struct:ns main err code: 12564TNS-12564: TNS:connection refusedns secondary err code: 0nt main err code: 0nt secondary err code: 0nt OS err code: 0

11g R1如果出现如上的错误信息会写入到sqlnet.log,11g R2会写入到alert.log，其实出现此错误是正常的现象。

贴出metalink的处理方法：

Note the time of the client corresponding client connection(s) in the listener log.  Here you may find a particular client,
set of clients or particular applications that are improperly disconnecting causing the timeout errors to be raised and recorder in the database alert log.
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_<listenername> = OFF
- Where the <listenername> would 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 would read:DIAG_ADR_ENABLED_LISTENER = OF
-Reload or restart the TNS Listener for the parameter change to take effect.

简单记录之…………

Fatal NI connect error 12170相关推荐

oracle 10035 err 942,案例:Oracle日志报错 Fatal NI connect error 12170 TNS-12535 TNS-00505
天萃荷净 Oracle数据库alert日志文件报错Fatal NI connect error 12170,通过查看mos相关文章找到解决办法今天在一台服务器的日志文件中,发现如下信息: Fatal ...
关于 Fatal NI connect error 12170
在 sqlnet.log 中错误如下: Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Versio ...
RAC下Fatal NI connect error 12170.报错处理
原创作品,出自 "深蓝的blog" 博客,欢迎转载,转载时请务必注明出处,否则有权追究版权法律责任. 深蓝的blog:http://blog.csdn.net/huangyanlo ...
关于Fatal NI connect error 12170
11.2.0.2的库两个节点的alert里均频繁出现如下信息: [html] ************************************************************* ...
Fatal NI connect error 12170错误解决办法
近日,在查看数据库告警日志时都发现有连续报以下错误信息: Fatal NI connect error 12170.VERSION INFORMATION: TNS for Linux: Versio ...
Fatal NI connect error 12170.
alert_oracl.log里发现了很多连接错误的信息. Fatal NI connect error 12170. VERSION INFORMATION: TNS for Lin ...
Fatal NI connect error 12170的解决方案
导读作者:杨漆 16年关系型数据库管理,从oracle 9i .10g.11g.12c到Mysql5.5.5.6.5.7.8.0 到TiDB获得3个OCP.2个OCM:运维路上不平坦,跌过不少坑.熬 ...
gitlab报错 fatal: index-pack failed error: RPC failed; result=18, HTTP code = 200解决方案
gitlab报错 "fatal: index-pack failed error: RPC failed; result=18, HTTP code = 200",如下图这个问题 ...
linux socket 错误 Connect error: No route to host(errno:113) 解决方法
两台机器进行socket通信时,可能在连接时出现错误: connect error: No route to host(errno:113) 出错原因:server端的防火墙设置了过滤规则解决办法: ...

Fatal NI connect error 12170

Fatal NI connect error 12170相关推荐

最新文章

热门文章