alert日志内容:
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
Tracing not turned on.
Time: 09-FEB-2011 06:11:23
nt OS err code: 0
TNS-12537: TNS:connection closed
Tracing not turned on.
ns secondary err code: 12560
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Tns error struct:
Tns error struct:
nt main err code: 0
ns main err code: 12537
ns main err code: 12537
Time: 09-FEB-2011 06:11:23
nt secondary err code: 0
nt OS err code: 0
TNS-12537: TNS:connection closed
TNS-12537: TNS:connection closed
ns secondary err code: 12560
ns secondary err code: 12560
nt main err code: 0
nt main err code: 0
Tracing not turned on.
nt secondary err code: 0
nt secondary err code: 0
Tns error struct:
nt OS err code: 0
nt OS err code: 0
ns main err code: 12537
opiodr aborting process unknown ospid (29191) as a result of ORA-609
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (29189) as a result of ORA-609
opiodr aborting process unknown ospid (29183) as a result of ORA-609
opiodr aborting process unknown ospid (29193) as a result of ORA-609
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 09-FEB-2011 06:11:23
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
Wed Feb 09 06:11:23 2011
***********************************************************************
nt main err code: 0
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
nt secondary err code: 0
nt OS err code: 0
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
opiodr aborting process unknown ospid (29201) as a result of ORA-609
opiodr aborting process unknown ospid (29199) as a result of ORA-609
Time: 09-FEB-2011 06:11:23
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (29203) as a result of ORA-609
同时检查 listener 日志没有特别异常
在部分机器 TNSPING XXX 60 等进行尝试结果正常,无链接问题
明显感觉,只要第一次 tnsping 链接正常,之后的 jdbc 链接就正常;如果第一次不正常,之后的 jdbc 链接就容易返回超时的错误。
尝试重启 lsnrctl stop/start 和重新加载配置文件 lsnrctl reload 重新注册数据库实例,仍然无法解决超时错误。
tnsping xxxx N 的时候明显观察到:
OK (56730 msec)
OK (80 msec)
OK (80 msec)
OK (70 msec)
OK (60 msec)
OK (70 msec)
OK (70 msec)
OK (80 msec)
OK (60 msec)
OK (60 msec)
OK (70 msec)
OK (60 msec)
OK (47820 msec)
OK (70 msec)
....
同时 PING IP 的结果并没有出现延时,机器之前并未设置防火墙等,可以排除网络和防火墙问题。
在连续 TNSPING 的情况下,出现明显链接延时,怀疑是监听器的问题。
重启监听后,问题仍然能够重现,参考google的结果,注释掉DB机器上 /etc/resolve.conf 文件中对 DNS 的解析后,TNSPING的结果恢复正常,alert 日志也不再出现 tns-12537 错误。
目前还没弄明白为什么DNS的解析会对监听器有影响?之前也并未修改过DNS,初步怀疑是DNS出现问题。
最后在 根据网上文档
http://forums.oracle.com/forums/thread.jspa?messageID=4489745
注释掉 /etc/resolve.conf 配置文件中对 DNS 的解析解决
metalink 上文档关于解决 TNS-12537 的文档用处不大,基本上和提供的可能无关
Troubleshooting ORA-12537 / TNS-12537 TNS:Connection Closed [ID 555609.1]
Fatal NI Connect 12560 And ORA-609 Opiodr Aborting Process Errors In The Alert Log [ID 987162.1]
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/7353848/viewspace-702564/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/7353848/viewspace-702564/