Re: Sure-fire "kill"

There is no init.ora parameters for getting rid of killed sessions AFAIK, but there is sqlnet.ora parameter SQLNET.EXPIRE_TIME which you set in seconds. You set it on server side and it affects how often server sends probes to check whether clients are still alive. If set to 0 (default) no probes are sent. I have usually set it to 12-24 hours or even more, because had problems w. version 8.0.4.0.0 on WinNT where long running jobs such analyze were terminated when exceeded expiry time, IIRC.

Don't set it too low, otherwise you might get lot's of extra network traffic and load on your system..

And, I just noticed, don't crosspost to all groups, cdo.server is enough.. Tanel.

"Fred" <noway_at_jose.com> wrote in message news:noway-0F6052.14454715072003_at_vienna7.his.com...
> There is a setting in INIT.ORA that has the unintended side-effect of
> making sure the ALTER SYSTEM KILL SESSION command has immediate affect.
> Without this setting, I've seen some instances where the session reports
> as being KILLED in V$SESSION but is not physically removed until the
> instance is bounced. Does anyone remember this value offhand?
Received on Tue Jul 15 2003 - 17:23:25 CDT