转载于:http://lanying1982.blog.163.com/blog/static/23067748201332410527783/
------>>方案一
[Oracle] opiodr aborting process unknown ospid (***) as a result of ORA-609

今天线上数据库（版本11.2.0.1）无法建立新连接，但原有的连接不受影响，alert.log报如下错误：

opiodr aborting process unknown ospid (22997) as a result of ORA-609

但在listener.log里却显示连接已建立

03-APR-2014 16:05:44 * (CONNECT_DATA=(SERVICE_NAME=orcl2.localdomain)(CID=(PROGRAM=python@lx151)(HOST=lx151)(USER=gl))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.100.151)(PORT=52903)) *establish * orcl2.localdomain * 0

在sqlnet.log里报12537错误

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: 03-APR-2014 15:24:30
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

当用lsnrctl status查看监听器状态时，卡住

通过查询官方文档，知道这是个bug，后来根据网上搜索的解决办法，链接：http://forums.oracle.com/forums/thread.jspa?messageID=4489745

删除主机文件/etc/resolv.conf，果然恢复了，具体原因不清楚，这只是一个临时的解决办法，要想彻底解决，应该要升级
------>>方案二

公司某系统在alert日志中报如下错误

TNS for HPUX: Version 11.2.0.3.0 - Production

Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.2.0.3.0 - Production

Fatal NI connect error 12547, connecting to:

(LOCAL=NO)

VERSION INFORMATION:

TNS for HPUX: Version 11.2.0.3.0 - Production

Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.2.0.3.0 - Production

TCP/IP NT Protocol Adapter for HPUX: Version 11.2.0.3.0 - Production

Time: 23-APR-2013 18:30:09

Tracing not turned on.

Tns error struct:

ns main err code: 12547

TNS-12547: TNS:lost contact

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 (13330) as a result of ORA-609

Tue Apr 23 18:30:09 2013

并且，客户端连接数据库特别慢，超过20s，查看oracle support，翻到了note 1121357.1,直接跳到known issues，直接将listener中INBOUND_CONNECT_TIMEOUT_ 及 SQLNET.INBOUND_CONNECT_TIMEOUT设置为0，故障消除。

公司其它系统都用的都是默认配置，没有发现这样的问题。

与其它系统的不同处是该系统客户端与服务器端位于不同网段，是否有影响暂时不知道。

listener 原配置与修改后配置如下：

LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))) # line added by Agent

LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))) # line added by Agent

ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by Agent

ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent

INBOUND_CONNECT_TIMEOUT_LISTENER=120

INBOUND_CONNECT_TIMEOUT_LISTENER_SCAN1=120

TRACE_LEVEL_CLIENT=0

TRACE_DIRECTORY_CLIENT=/oracle/app/crs_base/diag/tnslsnr/cydb1/listener/trace

TRACE_TIMESTAMP_CLIENT=TRUE

DIAG_ADR_ENABLED=off

-----------------------------------------------------

LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))) # line added by Agent

LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))) # line added by Agent

ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by Agent

ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent

INBOUND_CONNECT_TIMEOUT_LISTENER=0

TRACE_LEVEL_CLIENT=0

TRACE_DIRECTORY_CLIENT=/oracle/app/crs_base/diag/tnslsnr/cydb1/listener/trace

TRACE_TIMESTAMP_CLIENT=TRUE

DIAG_ADR_ENABLED=off

只修改了标黑部分

ITPub博客

ORA-609,ORA-12537问题处理

最新文章