Re: how to kill a session that marked for kill

hans-peter sloot wrote:
>

> I think that this session will go away eventually automatically.
> Probably recovery needs to be done.

I concur .... Once you killed the session , what the instace does is make sure to rollback all the uncommitted transaction that had been done but not committed . This will take sometime depending on how long the transactions and how much data has been changed, then once the rollback has been done , then the client tried to contact oracle again using the same session that will be the time that sqlnet will inform the client that the session has been killed and the marked for killed or killed will be removed from your system tables .

>
> Sigrid Staudte <mstaudte_at_rz.uni-leipzig.de> wrote in article
> <34830B6D.5C2B38E5_at_rz.uni-leipzig.de>...
> > In the database a session is running that
> > runs and runs and blockade ressources, locks tables
> > and so on. The session is never ending.
> > It is not possible to kill this session
> > with the alter system kill session command. The
> > session is only marked for kill. The only way to
> > terminate the session is shutting down the database.
> > Knows anywhere another way to solve this problem?
> >
> >
> > Bye...Sigrid
> >

-- 
================================================================
============================
| Joseph Sumalbag                                                                           
|
| Oracle DBA                                                                                
|
|                                                                                           
|
| The opinions expressed above are my own and doesn't 
 necessarily                           |
|reflect the opinion of any of my client company or my employer.                            
|
================================================================
============================