ORA-3135/ORA-3136 Connection Timeouts when the Fault is in the Database
最近發現 alert file 中又有 ORA - 3136 WARNING Inbound Connection Timed Out 的錯誤, 查看 metalink 說以下三種可能造成的原因, 分別為惡意的 client, 超時的認證, DB Server 忙碌時, 完整的說明如下 :
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.
解決的方法是設定 qlnet.ora 的 SQLNET.INBOUND_CONNECT_TIMEOUT = 0.
原因是10.2.0.1之後的版本預設值是60秒.
最近發現 alert file 中又有 ORA - 3136 WARNING Inbound Connection Timed Out 的錯誤, 查看 metalink 說以下三種可能造成的原因, 分別為惡意的 client, 超時的認證, DB Server 忙碌時, 完整的說明如下 :
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.
解決的方法是設定 qlnet.ora 的 SQLNET.INBOUND_CONNECT_TIMEOUT = 0.
原因是10.2.0.1之後的版本預設值是60秒.
全站熱搜
留言列表
