Re: Killed sessions lock some tables

Billy is right but a little OTT ...

The sessions will vanish when they are done rolling back or whatever. not before.

You might want to look at the work they have done ( look at the open rollback segment transactions ).

Restarting the database will not make the problem go away if that is what it is.

My advice to you is to learn the rollback segment information that will tell you why this is happening.

You will be a better person for it... ;-) "Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message news:b59hrs$5s2$1_at_ctb-nnrp2.saix.net...
> DavidS wrote:
>
> > How can I definitely kill sessions marked as 'killed'?
> > They lock some tables. Is it only way to restart database?
>
> They are likely rolling back. After all, you do not want a killed process
> just to stop and abort, leaving behind partial transactions, inconsistent
> data and a screwed database.
>
> > I would like to awoid this, if it is not inevitable.
>
> Ah.. the trick is not to have to kill sessions in the first place. Killing
> sessions must be an exception.
>
> As soon as it becomes so common that you're looking for ways to overcome
the
> locks issue, then you have a more serious problem on your hands than
killed
> sessions still being busy.
>
> > Do I have to kill some windows processes?
>
> Rather not.
>
> > I cannot find any related in Task Manager.
>
> Which is a Good Thing (tm). Task Manager only shows processes that have
> Window handles. Non-interactive processes (and threads) do not create (or
> seldom do create) windows.
>
> > Any hint would be greatly appreciated
>
> Seeing like you have a propensity for killing stuff, you're not perhaps
> interested in signing up for the Gulf War : Episode 2? ;-)
>
> --
> Billy
Received on Wed Mar 19 2003 - 06:59:38 CST