Re: kill session questions

Hello, Verna,

Query the v$process view spid column (operating system process id) where pid = v$session.sid and try to find the processes from the OS. Make sure the sessions are not vital to your database and if so kill them from the OS. The effect will be a wild disconnect like some users do by shutting down their PC in a middle of a transaction. In case you'rent, sure just keep waiting: you're better loosing some limted resources than the whole database.

Regards,

Verna Legaspi a écrit :

> Hello -
>
> There seemed to be a procedure gone awry and I had to do a
> ALTER SYSTEM KILL SESSON 'sid, serial#'
>
> on 2 sessions. They were both ACTIVE when I tried to kill them. However,
> it's been at least 3 hours, now - and they're both still simply flagged as
> "to be killed."
>
> Is this not uncommon? Is there any other way for me to force it to be
> killed completely? Also - am I correct in assuming none of their resources
> or locks/blocks have been released, yet? ... at least not until they finally
> fall of the v$session view?
>
> TIA,
> Verna
  Received on Sat Dec 23 2000 - 16:16:35 CST