參考metalink的文檔：Doc ID: Note:3136.1 and 465043.1

WARNING: inbound connection timed out (ORA-3136)

1.參數(shù)含義：
SQLNET.INBOUND_CONNECT_TIMEOUT is set to a value in seconds and determines how long a client has to

provide the necessary authentication information to a database.

INBOUND_CONNECT_TIMEOUT_listenername is set to a value in seconds and determines how long a client has

to complete its connect request to the listener after the network connection has been established.

2.參數(shù)意義：
在oracle 10.2以后的版本當(dāng)中將SQLNET.INBOUND_CONNECT_TIMEOUT 和 INBOUND_CONNECT_TIMEOUT_listenername參

數(shù)設(shè)置缺省為60s，之前的版本當(dāng)中默認(rèn)為0（即關(guān)閉此功能）。這兩個(gè)參數(shù)用于防止惡意client通過(guò)網(wǎng)絡(luò)攻擊db

server

Note: This timeout restriction was introduced to combat Denial of Service (DoS) attack whereby

malicious clients attempt to flood database servers with connect requests that consumes resources.

3.報(bào)出此warning的原因如下：

a.server收到一個(gè)從惡意client發(fā)來(lái)的連接請(qǐng)求，在這種情況下拋出的錯(cuò)誤將是預(yù)期的和可取的。（客戶端反復(fù)輸錯(cuò)

username/password）
b.服務(wù)器接收到一個(gè)有效的客戶端連接請(qǐng)求,但客戶需要很長(zhǎng)時(shí)間來(lái)驗(yàn)證超過(guò)默認(rèn)60秒。（客戶端網(wǎng)絡(luò)延遲）
c.DB服務(wù)器負(fù)載很高導(dǎo)致它無(wú)法在指定時(shí)間內(nèi)完成客戶端登錄請(qǐng)求。（數(shù)據(jù)庫(kù)服務(wù)器高負(fù)載）

4.解決辦法：
a.驗(yàn)證db server端，本地連接是否成功（listener是否可用）
b.驗(yàn)證本地連接是否延遲（本地網(wǎng)絡(luò)是否高效可用）
c.驗(yàn)證數(shù)據(jù)庫(kù)性能（db server是否高負(fù)載）
d.告警日志是否在之前報(bào)過(guò)ORA-600或ORA-7445
e.檢查是否有client反復(fù)嘗試登錄密碼（這是目前最有可能的原因）
f.關(guān)閉此功能（將2參數(shù)設(shè)置為0，設(shè)置方法參照步驟5）也可將2參數(shù)設(shè)置為適當(dāng)值。

5.修改這兩個(gè)參數(shù)的方法如下：

Edit the server side sqlnet.ora file and add this parameter:
SQLNET.INBOUND_CONNECT_TIMEOUT=<n>? Where <n> is the value in seconds.
E.g.:
SQLNET.INBOUND_CONNECT_TIMEOUT = 120

Edit the listener.ora file and add this parameter:
INBOUND_CONNECT_TIMEOUT_<listenername> = <n>? Again, where <n> is the timeout value in seconds.?
For example if the listener name is LISTENER then use:
INBOUND_CONNECT_TIMEOUT_LISTENER = 110

6.總結(jié)：
此warning提示，極有可能是有客戶端在不知道密碼的情況下，反復(fù)嘗試連接數(shù)據(jù)庫(kù)或登錄延遲導(dǎo)致，個(gè)人認(rèn)為可以

忽略，重啟監(jiān)聽(tīng)并不會(huì)解決該問(wèn)題，只是暫時(shí)清空了監(jiān)聽(tīng)的告警信息，也可觀察一段時(shí)間，或抓取性能分析報(bào)告，確

認(rèn)是否為負(fù)載過(guò)高導(dǎo)致性能下降從而引起的告警。
?

?

:ORA-3136 錯(cuò)誤解決
:ORA-3136 錯(cuò)誤解決

1、首先通過(guò)后臺(tái)alter日志發(fā)現(xiàn)報(bào)如下錯(cuò)誤:
Mon May 20 12:44:19 2013
WARNING: inbound connection timed out (ORA-3136)
Mon May 20 12:44:19 2013
WARNING: inbound connection timed out (ORA-3136)
Mon May 20 12:44:19 2013
WARNING: inbound connection timed out (ORA-3136)
?
2、觀察sqlnet.log中記錄如下錯(cuò)誤:
Fatal NI connect error 12514, connecting to:
?(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=XXXXX)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)
(SERVICE_NAME=XXXXXXXX)(INSTANCE_NAME=XXXX)(CID=(PROGRAM=XXXXXX)(HOST=XXXXXX)
(USER=oracle))))
? VERSION INFORMATION:
?TNS for Linux: Version 10.2.0.1.0 - Production
?TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.1.0 - Production
? Time: 28-11月-2008 14:10:42
? Tracing not turned on.
? Tns error struct:
??? ns main err code: 12564
??? TNS-12564: TNS:connection refused
??? ns secondary err code: 0
??? nt main err code: 0
??? nt secondary err code: 0
??? nt OS err code: 0
?
3、重新reload一下Listner:
??
[oracle@XXX ~]$ lsnrctl
LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 20-5月 -2013 12:54:56
Copyright (c) 1991, 2007, Oracle.? All rights reserved.
Welcome to LSNRCTL, type "help" for information.
?
LSNRCTL> reload
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
The command completed successfully

?
LSNRCTL> services
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
Services Summary...
Service "+ASM" has 1 instance(s).
? Instance "+ASM2", status BLOCKED, has 1 handler(s) for this service...
??? Handler(s):
????? "DEDICATED" established:0 refused:0 state:ready
???????? LOCAL SERVER
Service "+ASM_XPT" has 1 instance(s).
? Instance "+ASM2", status BLOCKED, has 1 handler(s) for this service...
??? Handler(s):
????? "DEDICATED" established:0 refused:0 state:ready
???????? LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
? Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
??? Handler(s):
????? "DEDICATED" established:0 refused:0
???????? LOCAL SERVER
Service "XXXXXXXX" has 2 instance(s).
? Instance "XXXXXX", status READY, has 1 handler(s) for this service...
??? Handler(s):
????? "DEDICATED" established:16 refused:0 state:ready
???????? REMOTE SERVER
???????? (ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXXXX)(PORT=1521))
? Instance "XXXXXX", status READY, has 2 handler(s) for this service...
??? Handler(s):
????? "DEDICATED" established:0 refused:0 state:ready
???????? REMOTE SERVER
???????? (ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXX)(PORT=1521))
????? "DEDICATED" established:31 refused:0 state:ready
???????? LOCAL SERVER
Service "XXXXXXXXX" has 2 instance(s).
? Instance "XXXXXX", status READY, has 1 handler(s) for this service...
??? Handler(s):
????? "D000" established:0 refused:0 current:0 max:972 state:ready
???????? DISPATCHER <machine: XXXXXXX, pid: 28579>
???????? (ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXX)(PORT=6661))
? Instance "XXXXXX", status READY, has 1 handler(s) for this service...
??? Handler(s):
????? "D000" established:0 refused:0 current:0 max:1022 state:ready
???????? DISPATCHER <machine: XXXX, pid: 28800>
???????? (ADDRESS=(PROTOCOL=tcp)(HOST=XXXXX)(PORT=51924))
Service "XXXXXXXX" has 2 instance(s).
? Instance "XXXXXXX", status READY, has 1 handler(s) for this service...
??? Handler(s):
????? "DEDICATED" established:16 refused:0 state:ready
???????? REMOTE SERVER
???????? (ADDRESS=(PROTOCOL=tcp)(HOST=XXXXX)(PORT=1521))
? Instance "XXXXXXX", status READY, has 2 handler(s) for this service...
??? Handler(s):
????? "DEDICATED" established:0 refused:0 state:ready
???????? REMOTE SERVER
???????? (ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXXX)(PORT=1521))
????? "DEDICATED" established:31 refused:0 state:ready
???????? LOCAL SERVER
The command completed successfully

LSNRCTL> show inbound_connect_timeout
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
LISTENER parameter "inbound_connect_timeout" set to 60
The command completed successfully
?
4、修改之后觀察一段時(shí)間系統(tǒng)恢復(fù)正常。

?

ORA-3136 錯(cuò)誤解決