Troubleshooting Guide ORA-3136: WARNING Inbound Connection Timed Out (文档 ID 465043.1)

灰太狼 2022-08-11 14:59 17阅读 0赞

<table> 
 <tbody> 
  <tr> 
   <td><img src="/images/20220810/5f8de8e776104c248c6c8b5ec423a8db.png" alt="" width="10" height="10"></td> 
   <td align="left"><span style="font-size:14px; text-align:right; padding:0px 6px 0px 0px; font-weight:bold">Troubleshooting Guide ORA-3136: WARNING Inbound Connection Timed Out (文档 ID 465043.1)</span></td> 
   <td align="right">&nbsp;</td> 
   <td>&nbsp;</td> 
  </tr> 
 </tbody> 
</table>

![t.gif][]

<table style="table-layout:fixed; overflow:hidden"> 
 <tbody> 
  <tr> 
   <td style="overflow:hidden"><span style="font-size:12px"></span> <p><strong>In this Document</strong><br> </p> 
    <table> 
     <tbody> 
      <tr> 
       <td></td> 
       <td><a href="https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=738bcgepc_9&amp;_afrLoop=512761289592314#PURPOSE" rel="nofollow">Purpose</a></td> 
      </tr> 
     </tbody> 
    </table> 
    <table> 
     <tbody> 
      <tr> 
       <td>&nbsp;</td> 
       <td><a href="https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=738bcgepc_9&amp;_afrLoop=512761289592314#TRBLSHOOT" rel="nofollow">Troubleshooting Steps</a></td> 
      </tr> 
     </tbody> 
    </table> 
    <table> 
     <tbody> 
      <tr> 
       <td>&nbsp;</td> 
       <td><a href="https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=738bcgepc_9&amp;_afrLoop=512761289592314#REF" rel="nofollow">References</a></td> 
      </tr> 
     </tbody> 
    </table> 
    <hr> <p></p> <h2 style="border-bottom-width:1px; border-bottom-style:solid; border-bottom-color:rgb(196,209,230); font-size:16px; background-color:rgb(119,119,115); color:rgb(255,255,255); text-transform:uppercase; padding-top:6px; padding-bottom:6px; padding-left:8px"> APPLIES TO:</h2> Oracle Net Services - Version 10.2.0.5 to 11.2.0.4 [Release 10.2 to 11.2]<br> Information in this document applies to any platform.<br> ***Checked for relevance on 21-APR-2014***<br> <h2 style="border-bottom-width:1px; border-bottom-style:solid; border-bottom-color:rgb(196,209,230); font-size:16px; background-color:rgb(119,119,115); color:rgb(255,255,255); text-transform:uppercase; padding-top:6px; padding-bottom:6px; padding-left:8px"> <a rel="nofollow"></a>PURPOSE</h2> <p>Troubleshooting guide for "ORA-3136&nbsp; WARNING inbound connection timed out" seen in the alert log.</p> <h2 style="border-bottom-width:1px; border-bottom-style:solid; border-bottom-color:rgb(196,209,230); font-size:16px; background-color:rgb(119,119,115); color:rgb(255,255,255); text-transform:uppercase; padding-top:6px; padding-bottom:6px; padding-left:8px"> <a rel="nofollow"></a>TROUBLESHOOTING STEPS</h2> <p>The "WARNING: inbound connection timed out (ORA-3136)" in the alert log indicates that the client was not able to complete&nbsp; the&nbsp; authentication process within the period of time specified by the parameter SQLNET.INBOUND_CONNECT_TIMEOUT.&nbsp;<br> <br> You might also see the errors ORA-12170 or TNS-12535 in the sqlnet.log that is generated on the server.<br> Check $ORACLE_HOME/network/log for this file.&nbsp; This entry should contain client address from which the timeout originated and may be helpful in determining how to troubleshoot the issue.&nbsp; Some applications or JDBC thin driver applications may not have these details.&nbsp; The sqlnet.log file is not generated&nbsp; by default in 11g and newer.&nbsp;&nbsp;<br> <br> From 10.2.0.1 onwards the default setting for the parameter SQLNET.INBOUND_CONNECT_TIMEOUT is 60 seconds.&nbsp; If the client is not able to authenticate within 60 seconds, the warning would appear in the alert log and the client connection will be terminated.</p> 
    <div style="padding:10px; background-color:rgb(255,249,215); border:1px solid rgb(193,169,13)">
      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. 
    </div> <p><br> <strong>The following are the most likely reasons for this error -</strong></p> 
    <ol> 
     <li>Server gets a connection request from a malicious client which is not supposed to connect to the database.&nbsp; In this case the error thrown would be the expected and desirable behavior. You can&nbsp;get the client address for which the error was thrown in the sqlnet.log file that is local to the database.</li> 
     <li>The server receives a valid client connection request but the client takes a long time to authenticate more than the default 60 seconds.</li> 
     <li>The DB server is heavily loaded due to which&nbsp;it cannot finish the client logon within the timeout specified.</li> 
    </ol> <p><strong>To understand what is causing this issue, following checks can be done&nbsp;<br> </strong></p> <p>The default value of 60 seconds is good enough in most conditions for the database server to authenticate a client connection. If it is taking longer, then it's worth checking the following items before implementing the workaround:<br> <br> 1. Check whether local connection on the database server is successful &amp; quick.<br> 2. If local connections are quick ,then check for underlying network delay with the help of your network administrator.<br> 3. Check whether your Database performance has degraded in anyway.<br> 4. Check alert log for any critical errors for eg, ORA-600 or ORA-7445 and get them&nbsp; resolved first.&nbsp;<br> These critical errors might have triggered the slowness of the database server.<br> <br> It is often necessary to increase the values for INBOUND CONNECT TIMEOUT at&nbsp; both the listener and the database in order to resolve this issue.&nbsp;&nbsp;&nbsp; It is usually advisable to set the database (sqlnet.ora) value slightly higher than the listener (listener.ora).&nbsp;&nbsp;&nbsp; The authentication process is more demanding for the database than the listener.</p> <p><br> <br> To set these parameters to use values higher than the default of 60 seconds, follow these instructions and restart the listener.&nbsp; There is no need to restart Oracle:&nbsp;<br> <br> Edit the server side sqlnet.ora file and add this parameter:<br> <br> SQLNET.INBOUND_CONNECT_TIMEOUT=&lt;n&gt;&nbsp; Where &lt;n&gt; is the value in seconds.<br> <br> E.g.:</p> 
    <div style="overflow:auto; border:1px solid rgb(196,209,230); padding:0.5em; margin:5px 0px 0px; font-family:'Courier New',Courier,monospace; font-size:12px; background-color:rgb(224,234,241); width:738.1500244140625px">
      SQLNET.INBOUND_CONNECT_TIMEOUT = 120 
    </div> <p>&nbsp;</p> <p>Edit the listener.ora file and add this parameter:&nbsp;</p> <p>INBOUND_CONNECT_TIMEOUT_&lt;listenername&gt; = &lt;n&gt;&nbsp; Again, where &lt;n&gt; is the timeout value in seconds.&nbsp;&nbsp;<br> <br> For example if the listener name is LISTENER then use:</p> 
    <div style="overflow:auto; border:1px solid rgb(196,209,230); padding:0.5em; margin:5px 0px 0px; font-family:'Courier New',Courier,monospace; font-size:12px; background-color:rgb(224,234,241); width:738.1500244140625px">
      INBOUND_CONNECT_TIMEOUT_LISTENER = 110 
    </div> <p>&nbsp;</p> 
    <div style="padding:10px; background-color:rgb(255,249,215); border:1px solid rgb(193,169,13)">
      From Oracle version 10.2.0.1 onwards the default value of&nbsp;INBOUND_CONNECT_TIMEOUT_&lt;listenername&gt; is 60 seconds. For previous releases it is zero or OFF by default. 
    </div> <p><br> <strong>How to check whether inbound timeout is active for the&nbsp;listener and database server</strong>:<br> <br> For example,&nbsp; INBOUND_CONNECT_TIMEOUT_&lt;listener_name&gt; =110<br> <br> You can check whether the parameter is active or not by simply doing telnet to the listener port.<br> $ telnet &lt;database server IP&gt; &lt;listener port&gt;&nbsp;<br> for eg.</p> 
    <div style="overflow:auto; border:1px solid rgb(196,209,230); padding:0.5em; margin:5px 0px 0px; font-family:'Courier New',Courier,monospace; font-size:12px; background-color:rgb(224,234,241); width:738.1500244140625px">
      $ telnet 123.23.23.23 1521 
    </div> <p><br> The telnet session should disconnect after 110 seconds which indicates that the inbound connection timeout for the listener is active.<br> <br> Alternatively, check at the LSNRCTL prompt using:<br> <br> LSNRCTL&gt;set current_listener &lt;listener_name&gt;<br> LSNRCTL&gt;show inbound_connect_timeout<br> <br> To check whether database server SQLNET.INBOUND_CONNECT_TIMEOUT is active:&nbsp;<br> Eg.</p> 
    <div style="overflow:auto; border:1px solid rgb(196,209,230); padding:0.5em; margin:5px 0px 0px; font-family:'Courier New',Courier,monospace; font-size:12px; background-color:rgb(224,234,241); width:738.1500244140625px">
      SQLNET.INBOUND_CONNECT_TIMEOUT=120 
    </div> <p><br> <br> a. For Dedicated server setup, enable the support level sqlnet server tracing will show the timeout value as below:</p> 
    <div style="overflow:auto; border:1px solid rgb(196,209,230); padding:0.5em; margin:5px 0px 0px; font-family:'Courier New',Courier,monospace; font-size:12px; background-color:rgb(224,234,241); width:738.1500244140625px">
      niotns: Enabling CTO, value=120000 (milliseconds) &lt;== 120 seconds 
     <br> niotns: Not enabling dead connection detection. 
     <br> niotns: listener bequeathed shadow coming to life... 
    </div> <p><br> <br> b. For shared Server setup,&nbsp;<br> $ telnet &lt;database server IP&gt; &lt;dispatcher port&gt;<br> Example.</p> 
    <div style="overflow:auto; border:1px solid rgb(196,209,230); padding:0.5em; margin:5px 0px 0px; font-family:'Courier New',Courier,monospace; font-size:12px; background-color:rgb(224,234,241); width:738.1500244140625px">
      $ telnet 123.23.23.23&nbsp; 51658 
    </div> <p><br> The telnet session should disconnect after 120 seconds which indicates that the sqlnet.inbound_connect_timeout is active.<br> <br> <br> If you have further questions&nbsp; regarding this issue then please create a Service Request in My Oracle Support and provide the following information:<br> <br> <strong>a. Client and matching server traces generated at support level.<br> <br> </strong><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?id=395525.1" rel="nofollow">Note 395525.1</a>&nbsp;How to Enable Oracle Net Client,Server,Listener,Kerberos and External procedure Tracing from Net Manager (netmgr):<br> <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?id=374116.1" rel="nofollow">Note 374116.1</a>&nbsp;How to Match Oracle Net Client and Server Trace Files<br> <strong><br> b. Upload sqlnet.ora, listener.ora Sqlnet.log, &amp; Alert_&lt;sid&gt;.log from database server</strong></p> </td> 
  </tr> 
 </tbody> 
</table>

[t.gif]: /images/20220810/5f8de8e776104c248c6c8b5ec423a8db.png