Re: SettingTime out for killed users

The problem here is that when you issue an 'alter system kill session' command, Oracle
marks the session as killed, but then waits for the operating system to clean up,
which depending on the port, it may or may not do in a timely fashion. Worse still,
any locks the session held stay held until the operating system cleans up.

A more reliable method is to grab the operating system process id from the V$PROCESS
table, and use the relevant OS command to kill the process.

After a short while, Oracle will then clean up the session, release any resources and
rollback any outstanding transactions. If this doesn't happen fast enough, you can
issue the following command to force PMON to clean up:

SVRMGR> oradebug wakeup 2
Statement processed.

Hope that helps

Graham

Ema wrote:

> Hi
>
> When I kill a database user with Oracle 8.0.5 Instance Manager,
> the user status become 'KILLED' but I still show it in the users list.
>
> I have set MAX_SESSIONS_PER_USER = 1 and, sometimes, when an application
> error occurs, the current user is still active and I can't connect me again.
>
> Is there an Oracle parameter to reduce time out for deleting killed users ?
>
> Thanks to all..
>
> Emanuele
Received on Fri Jul 21 2000 - 00:00:00 CDT