When IDLE_TIME Exceeds, Sessions Are Going In Killed Status Instead Of Sniped in v$session
(Doc ID 2583637.1)
Last updated on SEPTEMBER 04, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
When idle_time exceeds, the session status becomes KILLED instead of SNIPED in v$session.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document