RE: killing oracle processes
Date: Mon, 17 Aug 2009 16:51:37 -0400
In the scenario you describe, it sounds like the developer had privilege to kill any session, not just his own. When this thread started, the question was if there was a way to allow developers to kill their own sessions. The two are completely different. I'd never buy in to a non-DBA being able to kill arbitrary sessions, at least not without very special circumstances and lots of training. Now, if the question is the ability for him to kill his own sessions, on non-production databases, I may buy into that......
I do acknowledge that your CPU limit profile may be a cleaner and easier to maintain solution....depending on the circumstances....
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Goulet, Richard
Sent: Monday, August 17, 2009 3:45 PM
To: mschmitt_at_uchicago.edu; oracle-l_at_freelists.org Subject: RE: killing oracle processes
The biggest reason that I can drop on you and yes this did in fact happen in prod, was a developer who believed that a user was blocking his activity & he killed their session. Now I think that it being the CFO running some financial report near to closing time did a lot to bolster my contention that they should not have that privilege, because that afternoon we were revoking it.
Senior Oracle DBA
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Michael Schmitt Sent: Monday, August 17, 2009 1:49 PM
Subject: RE: killing oracle processes
Thanks for the suggestion. We are actually on Oracle 10g. I am not sure if resource limits will work for us in this case since it is typically scheduled batch jobs or ad-hoc reports that need to be killed. These all tend to run as a common user, and will sometimes be expected to run for long periods of time. Some have suggested in separate emails that there is really no issue in development environments, but this request includes production. I am trying to think of a technical reason why it should not be done (beyond knowing what is being done in the environment we support).
From: Goulet, Richard [mailto:Richard.Goulet_at_parexel.com]
Sent: Monday, August 17, 2009 12:39 PM
To: Michael Schmitt; oracle-l_at_freelists.org Subject: RE: killing oracle processes
I'm going to assume that your atleast on Oracle 9i. If so have you tried enabling resource limits in their profiles? I normally create a developer profile that kills a statement after 30 minutes of CPU time. It always seems to work.
Senior Oracle DBA
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 - 15:51:37 CDT