Description
The Idle Time Resource Usage setting limits the maximum idle time allowed in a session.
Idle time is a continuous inactive period during a session, expressed in minutes.
Long-running queries and other operations are not subject to this limit.
Setting an Idle Time Resource Usage limit helps prevent users from leaving
applications open when they are away from their desks.
On my system:
SQL > select * from DBA_PROFILES where resource_name = 'IDLE_TIME';
PROFILE RESOURCE_NAME RESOURCE_TYPE LIMIT COMMON
-------------------- --------------- --------------- --------------- ------
DEFAULT IDLE_TIME KERNEL UNLIMITED NO
ORA_STIG_PROFILE IDLE_TIME KERNEL 15 NO
2 rows selected.
SELECT * FROM DBA_PROFILES WHERE PROFILE='DEFAULT' AND RESOURCE_NAME IN ('IDLE_TIME','CONNECT_TIME');
======================================================
select * from user_resource_limits where resource_name='IDLE_TIME';
Modify profiles to meet the idle time requirement.
alter profile default limit idle_time 15;
Question:
How the idle_time parameter works. I want to 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.
SQL > 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 15 minutes by setting idle_time to 15:
SQL > alter profile senior_claim_analyst limit connect_time 100 sessions_per_user 20 idle_time 15;
No comments:
Post a Comment