Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







sqlnet.inbound_connect_timeout tips

Oracle Tips by Burleson Consulting

April 1, 2015

Question:  What is the "sqlnet.inbound_connect_timeout" parameter and how do I use sqlnet.inbound_connect_timeout for logging off idle sessions?

Answer:  The sqlnet.inbound_connect_timeout parameter is used to limit the time, set in seconds, for a client to connect with the database server and provide the required authentication information.

Also see my important notes on expiring sessions with high idle time.

To minimize the effect of denial-of-service attacks, you should configure sqlnet.inbound_connect_timeout parameter to limits that constrain the time in which resources can be held prior to authentication. In this way, client attempts to exceed the configured limits will result in connection terminations and an audit trail containing the IP address of the client being logged.

To limit consumption of Oracle resources by unauthorized users and enable an audit trail, you should set the sqlnet.inbound_connect_timeout parameter time-limit values for the sqlnet.inbound_connect_timeout parameter, expressed in wall-clock seconds

Failure resulting from sqlnet.inbound_connect_timeout will throw a ORA-03136 inbound connection timed out error.

You can enable SQL*NET logging by setting:

- inbound_connect_timeout_listenername=0

- log_directory_server=/u01/oracle/prod/network/admin

- log_file_server=sqlnet.log

- sqlnet.trace_level_listener=4. This parameter defaults to OFF.  The value can be set to 4 (which is USER) or 10 (which is ADMIN) or 16 (which is SUPPORT).  Normally, level 4 should suffice.

- sqlnet.inbound_connect_timeout=0


- You can set the inbound_connect_timeout to a non-zero value, See MOSC Document 465043.1. 

- Beware of a bug that can cause corruption, See MOSC Document 976852.1.

- Also see the MOSC note 730066.1 titled “Diagnosis of ORA-3135/ORA-3136 Connection Timeouts when the Fault is in the Database”.


Get the Complete
Oracle SQL Tuning Information 

The landmark book "Advanced Oracle SQL Tuning  The Definitive Reference"  is filled with valuable information on Oracle SQL Tuning. This book includes scripts and tools to hypercharge Oracle 11g performance and you can buy it for 30% off directly from the publisher.



Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster