![]() ![]() Ok, now I know what I need to do □ Kill is such a harsh word. This is a snippet from a handy little report called ‘Blocking Locks by User.’ It’s available under the Database Administration and Locks report category. Maybe I should go check what they’re doing… That looks like something I would write, wait as second… What makes this report ‘enhanced’ is that it has a context menu available that allows me to start a trace, or execute a ‘kill.’ Inactive? Someone is just begging to be ‘let go.’ There is a report version of this under the Database Administration and Sessions category. How can you see what the hold-up is?Īnd more importantly, how can we figure out who or what is causing the delay so we can go KILL them (their session, cough!) Tools -> Monitor Sessions You are being BLOCKED because what you want is LOCKED. ![]() OR optionally you can use following command to kill session in Oracle RAC. Sometimes you’re left there waiting because a resource you’re attempting to access is already being used by someone else. SQL> alter system kill session 9,171,1 System altered. Know how to do it Here it goes: begin ( sid > &sid, serial > &serial) end / Putted it in a script: killrds.sql. Getting the Windows ‘busy’ hourglass cursor is sure to raise anyone’s blood pressure. Actually, just because more than once I was about to kill a session in a RDS session and it was simply not possible with my usual ALTER SYSTEM KILL SESSION scripts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |