There are lot of bugs regarding this issue. The only 'workaround' at this time in these cases is to kill the OS process (Unix) or thread (NT). Yes, you can use ORAKILL. ORAKILL is run from the Command Prompt in the following syntax:
C:> orakill Sid Threadid
where: Sid is the Oracle instance to target
Thread is the thread id of the thread to kill
Threadid can be retrived from the spid column of the V$PROCESS data dictionary view.
You can use the following query to find the session threadid.
select p.spid THREADID, s.osuser, s.program
from v$process p, v$session s
where p.addr=s.paddr;
Last edited by sgodbole; 01-15-2003 at 01:32 PM.
HTH.
Shripad Godbole
OCP DBA (8,8i,9i)
"Let's document it and call it a feature."