本文分析了Oracle数据库出现ORA-609错误，伴随TNS-12537和TNS-12547错误的原因，主要由数据库inbound connect timeout默认值60秒超时引起。该问题常见于被DB Console和Enterprise Manager agent监控的数据库。解决方案包括增加INBOUND_CONNECT_TIMEOUT参数值，以及通过监听器和服务器端sqlnet.ora文件进行配置。此外，文章提供了问题定位和追踪的步骤，包括查看alert.log、sqlnet.log和启用服务器端跟踪。
天萃荷净
生产数据库alert日志中出现错误信息ORA-609 TNS-12537 TNS-12547，分析原因为数据库inbound connect timeout默认为60导致
1.数据库alert日志ora报错
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
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: 21-AUG-2012 09:50:15
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 (15204768) as a result of ORA-609
2.ora报错的原因
The ORA-609 error is thrown when a client connection of any kind failed to complete or
aborted the connection process before the connection/authentication process was complete.
Very often, this connection abort is due to a timeout. Beginning with 10gR2, a default value for
inbound connect timeout has been set at 60 seconds.
This time limit is often inadequate for the entire connection process to complete.
We have also discovered that the ORA-609 occurs frequently in installations
where the database is monitored by DB Console and the Enterprise Manager agent (emagent).
After the DB Console is started and as a matter of routine, the emagent will repeatedly try to
connect to the target instances.
We can see frequent emagent connections in the listener.log without error.
However, on occasion it may hav
最低0.47元/天 解锁文章
扫一扫
8751
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
