Using MAX_IDLE_TIME In Resource Manager Mark Session Killed But It Is Still There
Last updated on FEBRUARY 02, 2017
Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 126.96.36.199 - Release: 10.2 to 11.2
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms