From: Roby Sherman <rxsherm@uswest.net>
Subject: Re: How to clean Killed Oracle sessions ???
Date: 2000/05/05
Message-ID: <39134FEA.B3CF746@uswest.net>#1/1
Content-Transfer-Encoding: 7bit
References: <8ev106$bke$1@nnrp1.deja.com> <8evblq$o7i$1@nnrp1.deja.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Trace: news.uswest.net 957567259 63.225.125.238 (Fri, 05 May 2000 17:54:19 CDT)
Organization: Interealm
MIME-Version: 1.0
NNTP-Posting-Date: Fri, 05 May 2000 17:54:19 CDT
Newsgroups: comp.databases.oracle.misc


c_dopp@my-deja.com wrote:

> The "KILLED" session disappears the next time the user tries to access
> their killed session, after notifying the user the session is killed.
>

That is one scenario. Also consider:

* A user may have been executing a PL/SQL block that is stuck in a loop and
will never die - If this occurs, the only "graceful" (and I use this term
loosely. <grin>) ways to get rid of this session is to shut down the
database or kill the session's corresponding OS process.
* The session could be already be long gone on the client side but if they
had large uncommitted transactions, I believe the session will continue to
be listed until the session's transactions have completely rolled back.


--Roby


>
> In article <8ev106$bke$1@nnrp1.deja.com>,
>   venkata_jonnala@my-deja.com wrote:
> > DBA GURU's
> >
> > Please suggest me how to clean the killed sessions
> > in Oracle.
> >
> > When your client session got disconnected , then
> > you killed the session in the database still the
> > session exist with the status "KILLED". How to
> > remove that ???.
> >
> > Thanks,
> > Venkata
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
> >
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.