Re: Killed database sessions

erenner932_at_aol.com (ERenner932) wrote:
>Alex,
>
>If anyone knows to the contrary it would be very interesting, as I am
>suffering from the same issue.
>Apparently, a kill session is very low on the priority stack in relation
>to PMON who cleans out the sessions (I think its PMON). But on a very
>busy system it could take HOURS to clean out, as it is processing other
>requests with higher priority.
>I think this is a serious issue and should be addressed by Oracle. How
>can you expect to meet customer needs as well as system needs when you
>can't implement Profiles without running into these issues?
>Very frustrating.
>Hope this is helpful and someone else can correct/support/help on this
>comment.
>Ernst Renner

Ernst,

Indeed PMON is the culprit here. It is supposed to clean up killed sessions as well as monitor things like inactive sessions that exceed idle time settings or elapsed time settings. However because of the performance hit Oracle does not have PMON monitor processes constantly and it is unclear how often it is actually activated to remove these killed sessions. The manual says minutes but I have experienced killed sessions still showing in V$SESSION for hours or days. I agree this is frustrating. Since I am not a 7X24 shop I can do a shutdown abort to kill the sessions, but I feel for those who are. I too would be interested to hear if there is another solution!!!

Nevin Hahn Received on Wed Mar 05 1997 - 00:00:00 CST