Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Force Kill Session 1

Status
Not open for further replies.

fatcodeguy

Programmer
Feb 25, 2002
281
CA
Hi,

I have a runaway process that is blocking some packages I need to recompile, but can't because they're blocked. When I try to kill the session, I get a "ORA-00031: session marked for kill" error.

Is there a way I can force kill this session, short of restarting the db server?

Thanks
 
Guy,

Unfortunately, the "ALTER SYSTEM KILL SESSION..." command does not actually KILL the session; it just mortally wounds the "killed" session. I have had killed sessions remain visible for days following their kill. In urgent cases where the sessions had locks that would not release until the session actually went away, I had to bounce the server. (In my mind, this is a "near-bug" in Oracle that sessions remain past the "kill" command.)

[santa]Mufasa
(aka Dave of Sandy, Utah, USA @ 18:40 (10Mar04) UTC (aka "GMT" and "Zulu"), 11:40 (10Mar04) Mountain Time)
 
Thanks Dave,

Guess I'll just restart the server. If anyone has another alternative (cuz this happens often enough) please let me know. Thanks
 
Hi, The process/session wil actually be killed once the session that started it tries to access it again..That signals PMON to clean up - The process, until then, is waiting for an acknowledgement from the user that their session has been killed - if that user has alrteady logged off, then it will wait for some unspecified time...

Look for a program called, I think, ORAKILL if in windows
or use the kill -9 in Unix once you have identified the process you want to kill.

[profile]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top