Re: killing oracle processes

  • From: Martin Berger <martin.a.berger@xxxxxxxxx>
  • To: mschmitt@xxxxxxxxxxxx
  • Date: Tue, 18 Aug 2009 07:17:18 +0200

Michael,

maybe this script can help you.
we use it to give dedicated uses the possibility to kill sesssions of other users.

if you are using 11g, alter system kill session have a optional 3rd parameter for the instance id in a cluster.

hth
 Martin






 
Hi All,
 
I had a quick question that I was hoping the list could help me out with.  We have a group of developers who are requesting the ability to kill their own processes in the database (PRD/DEV/TST).  For example, if a poorly written report gets kicked off, one of their jobs chooses a poor execution plan, or an OWB process gets left out there.  The only reason they can really offer is that they do not have to wait for the DBA team to respond.  I am trying to think of technical reasons why this would not work.
 
I can write a script to limit the process to be killed to their stuff, but something about this still makes me feel uneasy.  Is there anything that I should worry about? 
 
Any thoughts?        
 
Thanks

Other related posts: