not able to kill session

Hi,
I am not able to kill a session.

SQL>  ALTER SYSTEM KILL SESSION '889, 46821'  immediate;

System altered.

SQL> SELECT STATUS FROM V$SESSION WHERE SID='889';

STATUS
--------
ACTIVE
dba1234Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gerwin Jansen, EE MVETopic Advisor Commented:
As what user are you trying this? When you try to kill the session as the same user that owns the session, it should work.
0
sventhanCommented:
It takes some time. Try killing it from unix

kill -9 processid
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Wasim Akram ShaikCommented:
author, you might have got confused with the sid..

oracle allocates SID(Service Identifiers) dynamically, it doesn't mean that you just have killed a SID and it should not appear again..

yes, for some time, the SID,Serial# combination will not appear

check with sid and serial#

you should use your query like this

SELECT STATUS FROM V$SESSION WHERE SID='889' and serial#='46821'  

then you can actually see whether the process got killed or not..

to be more precise, you can check the paddr from the v$session before killing the session like this

select paddr V$SESSION WHERE SID='889'  and place this value in

select * from v$process where addr='<pddr from above query>' to get the OS process id,where in you can check the status at Operating System level too..!!!
0
Wasim Akram ShaikCommented:
its possible that the sid which you have just killed might have got allocated with some other process, so you are seeing it again.. as mentioned in my earlier comment check the sid and serial# combination..

and be careful while seeing alone the SID it will lead to killing of some unwanted process which may lead to some other problems..
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.