Fatal NI connect error 12170
导读：收集整理的这篇文章主要介绍了html5教程-Fatal NI connect error 12170，觉得挺不错的，现在分享给大家，也给大家做个参考。小宝典致力于为广大程序猿（媛）提供高品质的代码服务，请大家多多光顾小站，小宝典在此谢过。...
收集整理的这篇文章主要介绍了html5教程-Fatal NI connect error 12170，觉得挺不错的，现在分享给大家，也给大家做个参考。小宝典致力于为广大程序猿（媛）提供高品质的代码服务，请大家多多光顾小站，小宝典在此谢过。 11.2.0.2的库两个节点的alert里均频繁出现如下信息：[htML]
***********************************************************************
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for IBM/aiX RISC System/6000: Version 11.2.0.2.0 - PRoduction
TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
oracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
Time: 15-NOV-2012 15:49:33
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: 0
nt OS err code: 0
Client 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 - Production
TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
Time: 15-NOV-2012 16:09:34
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
11g R1如果出现如上的错误信息会写入到SQLnet.LOG,11g R2会写入到alert.log，其实出现此错误是正常的现象。
贴出metalink的处理方法：
[html]
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. 11.2.0.2的库两个节点的alert里均频繁出现如下信息：
[html]
***********************************************************************
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
Time: 15-NOV-2012 15:49:33
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: 0
nt OS err code: 0
Client 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 - Production
TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
Time: 15-NOV-2012 16:09:34
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
11g R1如果出现如上的错误信息会写入到sqlnet.log,11g R2会写入到alert.log，其实出现此错误是正常的现象。
贴出metalink的处理方法：
[html]
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.
觉得可用，就经常来吧！ 欢迎评论哦！ html5教程，巧夺天工，精雕玉琢。小宝典献丑了！
声明：本文内容由网友自发贡献，本站不承担相应法律责任。对本内容有异议或投诉，请联系2913721942#qq.com核实处理，我们将尽快回复您，谢谢合作！
若转载请注明出处： Fatal NI connect error 12170
本文地址： https://pptw.com/jishu/586491.html