Last updated on JUNE 16, 2017
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 6.0 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 23-May-2016***
When IDLE_TIME is set in the users' profiles it will kill the sessions in the database if user is idle for more than IDLE_TIME specified and status in v$session now becomes SNIPED.
However it will take some time to disappear this SNIPED session information From V$Session and this note explains why.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms