Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Killing a session

Re: Killing a session

From: Frank Abney <abneyf_at_osshe.edu>
Date: 1997/01/06
Message-ID: <Pine.SOL.3.91.970106161957.4468E-100000@osshe.edu>#1/1

From my understanding of killing a session, the session stays alive until the next sql call against the session, and it kills it at that point. This of course does very little good when you want the session killed instantly. Not sure why Oracle did it this way.


Frank Abney                              Email: abneyf_at_osshe.edu
Oregon State System of Higher Education Phone: (541) 737-6269

On Thu, 2 Jan 1997, Mike Biggin wrote:

> B C Zygmunt wrote:
> >
> > Sometimes when I have killed a session the process stays "alive" until I shut
> > down the database. Is there a way to force the killing?
> >
> > TIA.
> >
> > Beverly Zygmunt
> > Oak Ridge National Lab
>
> I have found that quite often a 'killed' session entry hangs around in
> the V$SESSION table after issuing a 'kill session' command from sqldba
> (or svrmgrl). In my experience it is better to get the pid number of the
> process by joining V$SESSION with V$PROCESS for a given session, then
> terminate the process at the operating system level. Oracle then takes
> care of rollback etc., and removes the V$SESSION entry on completion.
>
>
>
> --
> Mike Biggin
> DENR, South Australian Government
> E-mail: mbiggin_at_denr.sa.gov.au
> Phone: +61 8 8204 9217; Fax: +61 8 8204 9017
>
> Unless explicitly attributed, the opinions expressed are personal
> and not those of DENR or the South Australian Government.
>
>
Received on Mon Jan 06 1997 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US