Using MAX_IDLE_TIME In Resource Manager Mark Session Killed But It Is Still There
(Doc ID 1239533.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 184.108.40.206 [Release 10.2 to 11.2]
Information in this document applies to any platform.
Configuring resource manager plan and specified a value for max_idle_time = 600 seconds, then after 600
seconds the session is marked killed, but it is still there and showing in v$session.
Also all PQ slave processes used by that session are still allocated to it and active.
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