Profile On User IDLE_TIME Set To 15 Minutes
(Doc ID 1061189.6)
Last updated on JULY 26, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 7.3.4.0 to 12.1.0.1 [Release 7.3.4 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The parameter resource_limit is set to TRUE and idle_time is set in profile.When idle_time exceeds, the session status becomes 'sniped' in v$session, but sniped sessions never get cleaned up.
You looked in the "alert.log" and found the following error:
The command returns many sessions with 'Sniped' as the status. You issued the alter system, kill session using the appropriate SID and serial number. The session is still not cleaned up even after the 'alter system kill session' command was issued.
In the USER_PROFILE most users have an IDLE_TIME set to 15 minutes. After 15 minutes their session shows up in V$session as 'sniped'. Regardless if the 'sniped session' has been killed or not users cannot login because the 'sniped session' counts against the sessions parameter in the init.ora file.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |