-
WARNING: inbound connection timed out (ORA-3136)
-
Thu Nov 21 11:13:49 2013
-
WARNING: inbound connection timed out (ORA-3136)
-
Thu Nov 21 11:14:54 2013
-
WARNING: inbound connection timed out (ORA-3136)
-
Thu Nov 21 11:15:01 2013
-
WARNING: inbound connection timed out (ORA-3136)
-
Thu Nov 21 11:15:49 2013
-
WARNING: inbound connection timed out (ORA-3136)
-
Thu Nov 21 11:16:18 2013
-
WARNING: inbound connection timed out (ORA-3136)
-
Thu Nov 21 11:31:00 2013
-
WARNING: inbound connection timed out (ORA-3136)
分析原因：
1：数据库负载正常
2：没有发现有Dos攻击迹象
3：防火墙的策略没有问题 防火墙的问题应该是长期的问题，不会今天报出超时，而以前没有。
查看listener.log 与sqlnet.log 发现主要是某app服务器上PHP应用链接异常，此问题先报给SA进行分析。
在查看listener.log时发现文件最新内容是上月的记录，查看了lsnrctl的状态也均运行正常。
-
LSNRCTL> show
-
The following operations are available after show
-
An asterisk (*) denotes a modifier or extended command:
-
-
rawmode displaymode
-
rules trc_file
-
trc_directory trc_level
-
log_file log_directory
-
log_status current_listener
-
inbound_connect_timeout startup_waittime
-
snmp_visible save_config_on_stop
-
dynamic_registration
-
-
LSNRCTL> show log_file
-
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxx)(PORT=1521)))
-
LISTENER parameter "log_file" set to listener.log
-
The command completed successfully
-
LSNRCTL> show log_status
-
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxxx)(PORT=1521)))
-
LISTENER parameter "log_status" set to ON
-
The command completed successfully
-
LSNRCTL> show log_directory
-
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxxxx)(PORT=1521)))
-
LISTENER parameter "log_directory" set to /u01/app/product/oracle/10.2.0/network/log/
-
The command completed successfully
-
LSNRCTL>
监听目前处于正常状态，日志功能也打开，后来一想，原来是日志文件大小已满。
处理：
1:首先 停止日志
-
LSNRCTL> set log_status off
2:到目录/u01/app/product/oracle/10.2.0/network/log/
mv listener.log listener.log.bak
3:开启日志
-
LSNRCTL> set log_status on
4:重新加载监听器
-
LSNRCTL> reload
-
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxxxx)(PORT=1521)))
-
The command completed successfully
-
LSNRCTL>
5:目录下重新生成新的日志，压缩保存
-
tar zcvf listener-20131121.log.tar.gz listener.log.bak
删除原有的日志：
今后准备编写脚本，定期备份监听日志，避免出现满的情况。
导致listener.log日志过大超过4G的原因为windows系统下oracle的bug问题。
测试库监听日志路径如下：
C:\app\BI\diag\tnslsnr\DESKTOP-S5CNE16\listener\trace
C:\app\BI\diag\tnslsnr\DESKTOP-S5CNE16\listener\alert
C:\app\Administrator\diag\tnslsnr\DESKTOP-S5CNE16\listener2\trace
