This discussion is archived
6 Replies Latest reply: Mar 27, 2013 7:24 PM by mseberg RSS

IDLE_TIME in profiles is not working..need suggestion

IamHariKrishna Newbie
Currently Being Moderated
Guys,

11gr2. windows 2005

we have lot of inactive sessions from java-thin-client and I setup a profile to kill sessions which are inactive for more than 4 hrs.
select resource_name,limit from dba_profiles where profile='APP_USERS';

RESOURCE_NAME                    LIMIT
-------------------------------- ----------
COMPOSITE_LIMIT                  DEFAULT
SESSIONS_PER_USER                UNLIMITED
CPU_PER_SESSION                  DEFAULT
CPU_PER_CALL                     UNLIMITED
LOGICAL_READS_PER_SESSION        DEFAULT
LOGICAL_READS_PER_CALL           DEFAULT
IDLE_TIME                        240
CONNECT_TIME                     DEFAULT
PRIVATE_SGA                      DEFAULT
FAILED_LOGIN_ATTEMPTS            10
PASSWORD_LIFE_TIME               DEFAULT
PASSWORD_REUSE_TIME              DEFAULT
PASSWORD_REUSE_MAX               DEFAULT
PASSWORD_VERIFY_FUNCTION         NULL
PASSWORD_LOCK_TIME               1
PASSWORD_GRACE_TIME              7

SQL> select username,profile from dba_users where username in ('RATOR');

USERNAME                       PROFILE
------------------------------ ------------------------------
SOCTT                         APP_USERS

SELECT SID, SERIAL#, USERNAME,STATUS, (LAST_CALL_ET / 60) LAST_CALL_ET,
LOGON_TIME
FROM v$session
WHERE username IS NOT NULL
AND (LAST_CALL_ET / 60) > 240
AND STATUS = 'INACTIVE';

-- still showing 12 records --
But when I ran the query to check inactive sessions which are for more than 4 hrs (240 mins), I'm able to still see them

They should be killed right? Correct me If im wrong.

Thanks

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points