Home » RDBMS Server » Server Administration » Killed sessions exists even after 2 days (unix,10.2.01)
Killed sessions exists even after 2 days [message #480777] Wed, 27 October 2010 02:36 Go to next message
sekar52
Messages: 141
Registered: May 2010
Location: Mumbai
Senior Member
Hi I killed some 70 sessions which where inactive couple of days ago using
alter system kill session(sid,serial#) immediate;

But even after killing them it still exists in the v$session view when I query
select sid,serial# from v$session where username is not null;

It has the same sid and serial#....I tried killing them every now and then but it still shows those exists...What is the problem
Re: Killed sessions exists even after 2 days [message #480781 is a reply to message #480777] Wed, 27 October 2010 02:53 Go to previous messageGo to next message
Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
[Note that I'm not a DBA; however, I had a chance to listen to a lecture some time ago so - this is what I remembered.]

The man said that sessions won't go away until PMON removes them, and that might take a while (he mentioned half a day. In your case, it is 2 days now. I have no idea whether that's possible or not.). He also said that one might need to kill the process at the operating system level as well (using KILL or ORA_KILL) (depending on your OS).

Anyway: perhaps you should wait for another opinion, as what I said doesn't have to be true at all.
Re: Killed sessions exists even after 2 days [message #480789 is a reply to message #480781] Wed, 27 October 2010 03:46 Go to previous messageGo to next message
tahpush
Messages: 961
Registered: August 2006
Location: Stockholm/Sweden
Senior Member

Read ID 107686.1 and 1041427.6 on metalink.

Re: Killed sessions exists even after 2 days [message #480793 is a reply to message #480777] Wed, 27 October 2010 04:34 Go to previous message
Michel Cadot
Messages: 68718
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator
1/ Before killing you have to look at STATUS column
2/ After killing you have to look at STATUS column

If before status were SNIPPED then Oracle is waiting for an action from the user before ending the session.
In this case the only (supported) way to get the session removed from the session list is to use
alter system disconnect session immediate statement.

Regards
Michel
Previous Topic: managing space
Next Topic: Need help in 'Gather Stats'
Goto Forum:
  


Current Time: Fri Nov 29 08:54:54 CST 2024