How to kill Oracle Process on Win NT/2000

Quote:

---

Originally posted by ctcyl
Dear friends..

I have tried by ORAKILL, but I got the following error. and unable to kill the process.

Firstly I have query for the process by the following query.
1 select sid, spid as thread, osuser, s.program
2 from sys.v_$process p, sys.v_$session s
3* where p.addr = s.paddr
SQL>/
1 193 SYSTEM ORACLE.EXE
2 263 SYSTEM ORACLE.EXE
3 267 SYSTEM ORACLE.EXE
4 216 SYSTEM ORACLE.EXE
5 254 SYSTEM ORACLE.EXE
6 259 SYSTEM ORACLE.EXE
7 233
8 250
9 257
10 290
13 113 DOMAIN\Administrator SQLPLUSW.EXE

Then I have tried to kill the process 13 and thread 113 by the following commands -

Microsoft(R) Windows NT(TM)
(C) Copyright 1985-1996 Microsoft Corp.

C:\>orakill 13 113

Could not attach to Oracle instance 13: err = 2

C:\>

and got the above error "Could not attach to Oracle instance 13: err = 2 "

Please advise.

Thanks & Regards
Naresh

---

yes,I have the same problem:
C:\>orakill 8 616

Could not attach to Oracle instance 8: err = 2

can someone give the answer?
thanks !
Auling

hi...

try that...

c:\orakill %sid% spid

example:

c:\orakill test 113

mfg blackswan

The usage of orakill is

orakill sid thread

sid here means Oracle SID

Well i tried
orakill "instance_name" thread
it says
kill of thread id instance successfully signalled.
I did this for a user using sqlplus, but even after receining this message the user continued to use sqlplus and access the database without any hinderance for the same session !!!!!

WHY ?

Hi,
Is everybody or shall i say anybody not facing the same results as i did ?
Anyone out there ?

I realize that Im novice but this code looks to me have more bugs than windows ME ...
1) there are really no such views as sys.v_$process p, sys.v_$session s

probably v$process & v$session are good choices

1 select sid, spid as thread, osuser, s.program
2 from v$process p, v$session s
3* where p.addr = s.paddr;
SQL> /
where p.addr = s.paddr;
*
ERROR at line 3:
ORA-00911: invalid character

since it quite late I said I have enough with bugging this script (for exam Ill remember
ALTER SYSTEM KILL SESSION 'SID, THREAD#';

Thnx but no THANKS!!

Quote:

---

Originally posted by sreddy
Win NT/2000 is a thread based Operating System and not process based Operating System like Unix. Oracle user and background processes are not multiple processes but, threads with in oracle.exe process. 'orakill' is oracle provided utility to kill a particular resource intensive thread under oracle.exe process. For help type in at the DOS prompt C:\>orakill /?

The following query can be used to get the sid, thread id of a particular resource intensive thread.

SQL> select sid, spid as thread, osuser, s.program
2 from sys.v_$process p, sys.v_$session s
3 where p.addr = s.paddr;

SID THREAD OSUSER PROGRAM
-------- --------- --------------- -------------------------------------
1 000C5 UNKNOWN ORACLE73.EXE
2 0013F UNKNOWN ORACLE73.EXE
3 00140 UNKNOWN ORACLE73.EXE
4 0005F UNKNOWN ORACLE73.EXE
5 0011C UNKNOWN ORACLE73.EXE
6 0009A UNKNOWN ORACLE73.EXE
7 00101
8 000C0
12 00148 SYSTEM D:\ORANT805\agentbin\DBSNMP.EXE
18 001FC scott SQLPLUS.EXE
9 001F2 adam C:\WINNT\Profiles\All Users\Start Menu\AFF_PFC.LNK
36 00206 mark SVRMGR.EXE
31 000E1 cathy AFFAIRS.EXE
15 00204 Julie C:\Documents and Settings\julie\Start Menu\Programs\AFFS.lnk


Say the query from user scott is consuming lot resources and it can be killed by running orakill utility as follows.

C:\>orakill 18 001FC


[Edited by sreddy on 03-29-2001 at 10:49 AM]

---

So when u execute the above command, that particular process for user scott will be termintaed... But is the user scott still supposed to be connected to the database and can work with the same sql plus session ?

I tried the above but could still work in my sql session.

Could some one please explain
what is happening.

--A

Hi
Actully ORAKILL command expects the SID and THREADID

SID is the name of the databse itself
if the database name is xyz and the psid(thread id) = 510 then

c:\orakill
means
c:\orakill xyz 510

it will work
Thanks

this 13 isnt the SID