My Oracle Support Banner

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 to [Release 10.2 to 11.2]
Information in this document applies to any platform.
Reviewed 02-Feb-2012.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.