Thu Feb 18 22:05:53 2010
ksvcreate: Process(m000) creation failed
Thu Feb 18 22:06:46 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:06:46 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:06:46 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:06:46 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:07:01 2010
PMON failed to acquire latch, see PMON dump
Thu Feb 18 22:07:35 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:08:00 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:08:21 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:08:21 2010
WARNING: inbound connection timed out (ORA-3136)
Thu Feb 18 22:08:21 2010
日志中频繁出现以上信息,数据库并没有异常。
metalink给出处理方法:
1.$ lsnrctl (注意监听名称,set INBOUND_CONNECT_TIMEOUT_
=0)
LSNRCTL> show inbound_connect_timeout
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hpcmdb2.transgd)(PORT=1521)))
LISTENER parameter "inbound_connect_timeout" set to 60
The command completed successfully
LSNRCTL> set inbound_connect_timeout 0
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hpcmdb2.transgd)(PORT=1521)))
LISTENER parameter "inbound_connect_timeout" set to 0
The command completed successfully
LSNRCTL> show inbound_connect_timeout
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hpcmdb2.transgd)(PORT=1521)))
LISTENER parameter "inbound_connect_timeout" set to 0
The command completed successfully
LSNRCTL> exit
2.LSNRCTL>reload(是否影响现有客户端连接?)
3.之后,oracle建议在sqlnet中增加SQLNET.INBOUND_CONNECT_TIMEOUT参数,以避免denial-of-service攻击.
3. stop and start both listener and database.
4. Now try to connect to DB and observe the behaviour
这个参数的引入,主要是防止DoS攻击,恶意攻击者可以通过不停的开启大量连接请求,占用服务器的连接资源,使得服务器无法提供有效服务。在10.2.0.1起,该参数默认设置为60秒
但是,这个参数的引入也导致了一些相关的bug。比如:
Bug 5594769 - REMOTE SESSION DROPPED WHEN LOCAL SESSION SHARED AND INBOUND_CONNECT_TIMEOUT SET
Bug 5249163 - CONNECTS REFUSED BY TNSLSNR EVERY 49 DAYS FOR INBOUND_CONNECT_TIMEOUT SECONDS
阅读(968) | 评论(0) | 转发(0) |