Re: How I can kill killed session?

Hi, Andrew and Lev

The parameter SQLNET.EXPIRE_TIME=5 in sqlnet.ora is useful to kill session that has "INACTIVE" status, despite the user process was terminated. But, in this case, the session status already "KILLED". It means the death of the user process already detected by the oracle server. The resources isn't free yet because PMON process is doing rollback of the pending transactions for the interrupted session. You don't need to shutdown the database, actually, you don't need to do any thing. After any minutes, the session will disappear and the session's resources (table that is locked now) will become available.

bye,

Milagre.

In article <7a5610$8oc$1_at_nnrp1.dejanews.com>,   Andrew Protasov <a_protasov_at_hotmail.com> wrote:
> Hi,
>
> Try to set
>
> SQLNET.EXPIRE_TIME=5
>
> in server side sqlnet.ora file. It is time in minutes
> between watchdog packets. Server uses them to check
> where is client alive or not.
>
> Andrew Protasov
>
> In article <01bd36cb$3408e0e0$101aa8c0_at_lev.vaz.ru>,
> "Lev Yunak" <L.Yunak_at_vaz.ru> wrote:
> > Hello
> >
> > I disconnected one session and it had marked as "KILLED".
> > And this session continued lock object that it worked. Also I terminated
> > client program
> > too but nothing happened.
> > I want session dissapper only and unlock my objects without restart DB.
> > I remember there is parameter for init.ora that define time to wait client
> > answer.
> > Does it help? What can help?
> >
> > Best wishes, Lev.
> >
> > P.S. May it FAQ but I couldn't find.
> >
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Sun Feb 14 1999 - 20:56:46 CST