This content has been marked as final. Show 6 replies
PMON will clean out these sessions but it only does this periodically.
Eventually it will show in v$session as dead. Most likely your sessions are dead already and on time.
If you want to test this logon and let your session go idle and then check you connection at 241 minutes.
Salman raises a good point : ( see for yourself )
Edited by: mseberg on Mar 26, 2013 9:03 PM
Hi,1 person found this helpful
What is value of init parameter RESOURCE_LIMIT? It should be TRUE.
Thanks Mseberg for nice information.
How frequently pmon wlil do clean-up of dead-connections process. Any idea ?
Yeah Salman,it is set to TRUE. Thanks for the response.
How frequently pmon wlil do clean-up of dead-connections process.
Well now you need to clarify what it is you are still asking about.
Your original post was asking why you still have INACTIVE sessions. Now you are asking about KILLED sessions.
PMON isn't going to clean up a session just because it is INACTIVE; the session needs to have a status of KILLED: and that just means 'Session marked to be killed'; it doesn't necessarily mean the 'kill' process has been completed.
Your question said you are seeing sessions still marked INACTIVE even after the profile limit is reached and exceeded. Have you checked periodically to see if any of those sessions had a status change to KILLED or have not disappeared?
Hello again;1 person found this helpful
I don't know the timing exactly. This Oracle note may help :
The Sessions do not Get Terminated After passing the Time Specified with LIMIT CONNECT_TIME [ID 948589.1]