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 







idle_time Tips

Oracle Database Tips by Donald BurlesonMarch 6, 2015

Question:  Please explain how the idle_time parameter works.  I want t disconnect sessions after the idle_time has expired.

Answer:  The idle_time parameter is used within a SQL*Plus profile.  Oracle has several ways to disconnect idle sessions, both from within SQL*Plus via resources profiles (connect_time, idle_time), and with the SQL*net expire time parameter.

IMPORTANT NOTE:  You must set resource_limit=TRUE to automatically terminate Oracle connections.

alter system set resource_limit=true scope=both;

You can use profiles to set the connect time and idle time with "alter profile" statements.  Note that idle_time is expressed in minutes and you can express idle_time for 30 minutes by setting idle_time to 30:

alter profile senior_claim_analyst limit
connect_time 180000
sessions_per_user 2
idle_time 30;

Also see these notes on the connect_time  parameter.

Profiles comprise a named set of resource limits. By default, when you create users, they are given the default profile, which provides unlimited use of all resources.

The syntax to create a profile with idle_time follows:

CREATE PROFILE profile LIMIT resource_parameters|password_parameters;

By setting resource limits like idle_time, you can prevent users from performing operations that will tie up the system, and prevent other users from performing operations. You can use resource limits for security, to ensure that users log off the system, so as not to leave the session connected for long periods of time.

The idle_time parameter limits the maximum time a session can stay connected without doing anything. By reducing the period of time an inactive session stays connected, the probability of that session being a victim of abuse is reduced.

Based on our decision, we can create the profile to enforce it. Since we already have the profile, we will merely update it with the new parameters.

alter profile senior_claim_analyst limit
Connect_time 180000
Sessions_per_user 2
idle_time 30

As we see, the idle_time parameter will disconnect sessions after n minutes of inactivity.

Oracle Training from Don Burleson 

The best on site "Oracle training classes" are just a phone call away! You can get personalized Oracle training by Donald Burleson, right at your shop!

Oracle training



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 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster