RE: killing oracle processes
Date: Mon, 17 Aug 2009 15:36:22 -0400
Do you have a good way to make sure a developer running as Oracle account XYZ has permission to kill that session (logical ownership) rather than accidentally killing one of his or her co-workers critical processes? Folks need to be patient and realize there is a reason you don't just give everyone DBA access...
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Michael Schmitt Sent: Monday, August 17, 2009 11:34 AM
Subject: killing oracle processes
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?
ThanksReceived on Mon Aug 17 2009 - 14:36:22 CDT