I do not run Oracle on NT but I believe that you will find that
Oracle has provided an OS level utility to kill sessions,
orakill. If you are using Oracle on NT you should probably use
this utility instead of the alter system kill session command.
In article <ee0W4.39715$PL4.840741_at_ozemail.com.au>, "Richard"
<roxl_at_ozemail.com.au> wrote:
>> Kill the process using OS tools (if your platform allows of
course).
>> v$session will give you the process ID (PID or SPID I think).
>>
>>
>> If you are runnuing NT, you may sometimes find that the
processes never
>> leave v$session even though they've been marked for killing.
>>
>> In this case you'll need to restart the Oracle instance.
>
>
>That sounds a bit extreme. Oracle should remove the session
itself -
>though this may not happen right away. Given that the session
has been
>marked for removal I think I'd be inclined to leave the
database up.
>
>.... or have you seen cases where the processes hang around for
days despite
>killing from OS and Oracle?
>
>/Richard/
>
- Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
Received on Mon May 22 2000 - 00:00:00 CDT
