節點1 上的alert log :

-----------------------------------------------------------------------
Wed Apr 9 08:52:41 2008
Thread 1 advanced to log sequence 20110
Current log# 6 seq# 20110 mem# 0: /ocfs_data/tpc/redo06a.log
Current log# 6 seq# 20110 mem# 1: /ocfs_data2/tpc/redo06b.log
Wed Apr 9 08:59:02 2008
WARNING: inbound connection timed out (ORA-3136)

[@more@]

Wed Apr 9 09:07:55 2008
Thread 1 advanced to log sequence 20111
Current log# 7 seq# 20111 mem# 0: /ocfs_data/tpc/redo07a.log
Current log# 7 seq# 20111 mem# 1: /ocfs_data2/tpc/redo07b.log
Wed Apr 9 09:21:05 2008
WARNING: inbound connection timed out (ORA-3136)
Wed Apr 9 09:21:12 2008
WARNING: inbound connection timed out (ORA-3136)
Wed Apr 9 09:21:42 2008
Thread 1 advanced to log sequence 20112
Current log# 8 seq# 20112 mem# 0: /ocfs_data/tpc/redo08a.log
Current log# 8 seq# 20112 mem# 1: /ocfs_data2/tpc/redo08b.log
Wed Apr 9 09:27:19 2008
Thread 1 advanced to log sequence 20113
Current log# 9 seq# 20113 mem# 0: /ocfs_data/tpc/redo09a.log
Current log# 9 seq# 20113 mem# 1: /ocfs_data2/tpc/redo09b.log

節點2 上的alert log :

-----------------------------------------------------------------------
Thread 2 advanced to log sequence 16191
Current log# 11 seq# 16191 mem# 0: /ocfs_data/tpc/redo11a.log
Current log# 11 seq# 16191 mem# 1: /ocfs_data2/tpc/redo11b.log
Wed Apr 9 09:45:44 2008
WARNING: inbound connection timed out (ORA-3136)
Wed Apr 9 09:52:20 2008
Thread 2 advanced to log sequence 16192
Current log# 12 seq# 16192 mem# 0: /ocfs_data/tpc/redo12a.log
Current log# 12 seq# 16192 mem# 1: /ocfs_data2/tpc/redo12b.log
Wed Apr 9 10:08:33 2008
WARNING: inbound connection timed out (ORA-3136)
Wed Apr 9 10:18:36 2008
Thread 2 advanced to log sequence 16193
Current log# 13 seq# 16193 mem# 0: /ocfs_data/tpc/redo13a.log
Current log# 13 seq# 16193 mem# 1: /ocfs_data2/tpc/redo13b.log

兩個節點上的sqlnet.log

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

Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for Linux: Version 10.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 10.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.3.0 - Production
Time: 09-APR-2008 09:21:05
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.155.15.3)(PORT=1833))

***********************************************************************
Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for Linux: Version 10.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 10.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.3.0 - Production
Time: 09-APR-2008 09:21:12
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.155.15.3)(PORT=1834))

查詢到metalink 上以及eygle的文章：

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

這是和網路連線相關的一個錯誤,Metalink上給出瞭如下的解決方案:

1.set INBOUND_CONNECT_TIMEOUT_=0 in listener.ora
2. set SQLNET.INBOUND_CONNECT_TIMEOUT = 0 in sqlnet.ora of server.
3. stop and start both listener and database.
4. Now try to connect to DB and observe the behaviour

這裡重起資料庫和Listener我認為是沒有必要的,我們reload一下Listner應該就可以了.

[oracle@order admin]$ lsnrctl

LSNRCTL for Linux: Version 10.2.0.2.0 - Production on 19-JUL-2006 15:26:33

Welcome to LSNRCTL, type "help" for information.

LSNRCTL> reload
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.9.11)(PORT=1521)))
The command completed successfully
LSNRCTL> services
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.9.11)(PORT=1521)))
Services Summary...
Service "order" has 2 instance(s).
Instance "order", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "order", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully

LSNRCTL> show inbound_connect_timeout
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.9.11)(PORT=1521)))
LISTENER parameter "inbound_connect_timeout" set to 0
The command completed successfully
LSNRCTL> exit

修改之後,觀察了一段時間,目前正常.

關於SQLNET.INBOUND_CONNECT_TIMEOUT引數,Oracle建議修改該引數,以避免denial-of-service攻擊.

引用一段Oracle文件說明如下:

SQLNET.INBOUND_CONNECT_TIMEOUTPurposeUse the SQLNET.INBOUND_CONNECT_TIMEOUT parameter to specify the time, in seconds, for a client to connect with the database server and provide the necessary authentication information.

If the client fails to establish a connection and complete authentication in the time specified, then the database server terminates the connection. In addition, the database server logs the IP address of the client and an ORA-12170: TNS:Connect timeout occurred error message to the sqlnet.log file. The client receives either an ORA-12547: TNS:lost contact or an ORA-12637: Packet receive failed error message.

Without this parameter, a client connection to the database server can stay open indefinitely without authentication. Connections without authentication can introduce possible denial-of-service attacks, whereby malicious clients attempt to flood database servers with connect requests that consume resources.

To protect both the database server and the listener, Oracle Corporation recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying values for these parameters, consider the following recommendations:

Set both parameters to an initial low value.
Set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter.
For example, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed.

See Also: Oracle9i Net Services Administrator's Guide for information about configuring these parameters

Default
None

Example
SQLNET.INBOUND_CONNECT_TIMEOUT=3

Oracle10g R2 RAC: WARNING: inbound connection timed out (ORA-3136)

相關文章