早上突然接到監控報警WARNING: inbound connection timed out (ORA-3136)。

ora-3136 連線超時在大部分情況下是可以忽略的，這個錯誤一般是由於客戶端由於沒有使用正確登入的密碼，連線超時導致。

比如下面的例子：

oracle@rac1:/home/oracle>sqlplus yang/yan@yangdbstd

SQL*Plus: Release 11.2.0.1.0 Production on Wed Sep 21 10:47:35 2011

ERROR:

ORA-01017: 使用者名稱/口令無效; 登入被拒絕

Enter user-name:

在備庫中檢視日誌：

oracle@rac4:/home/oracle>tf

***********************************************************************

Fatal NI connect error 12170.

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: 21-SEP-2011 10:48:36

Tracing not turned on.

Tns error struct:

ns main err code: 12535

TNS-12535: TNS:operation timed out

ns secondary err code: 12606

nt main err code: 0

nt secondary err code: 0

nt OS err code: 0

Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.250.7.226)(PORT=61449))

WARNING: inbound connection timed out (ORA-3136)

sqlplus user/passwd@tnsname，這個passwd 是錯誤的，oracle提示：ORA-01017: 使用者名稱/口令無效; 登入被拒絕，不做稽核操作，把連線掛在那裡，等帶一會，就可以在服務端的資料庫alert 日誌中看到WARNING: inbound connection timed out (ORA-3136)客戶端使用錯誤的密碼登入，但是之後又沒有退出連線導致ORA-3136。查詢ML文件《Troubleshooting ORA – 3136 WARNING Inbound Connection Timed Out [ID 465043.1]》，還有如下原因：

There can be three main reasons for this error -

1. Server gets a connection request from a malicious client which is not supposed to connect to the database , in which case the error thrown is the correct behavior. You can get the client address for which the error was thrown via sqlnet log file.

2. The server receives a valid client connection request but the client takes a long time to authenticate more than the default 60 seconds.

3. The DB server is heavily loaded due to which it cannot finish the client logon within the timeout specified.

【Oracle】 inbound connection timed out (ORA-3136)

相關文章