Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: why administrator refuse to give permission on PLUSTRACE

Re: why administrator refuse to give permission on PLUSTRACE

From: DA Morgan <>
Date: Sat, 03 Nov 2007 06:23:19 -0700
Message-ID: <>

Peter J. Holzer wrote:
> On 2007-11-03 06:30, DA Morgan <> wrote:

>> But lets give you an opportunity to test those developers around you to
>> see how good they really are.
>> What would you do if the stored procedure "test" was identified as the
>> issue?

> If that procedure has been identified as "the issue" (whatever "the
> issue" is and however that has been determined) most of the forensic
> work has already been done. The rest is fixing the problem which is the
> developer's job.
>>    FOR r IN (SELECT * FROM parent)
>>    LOOP
>>      r.part_num := r.part_num * 10;
>>      INSERT INTO child
>>      VALUES
>>      (r.part_num, r.part_name);
>>    END LOOP;
>>    COMMIT;
>> END test;
>> /

> I realize of course that your example isn't meant to do anything useful,
> but that's what makes it unrealistic. Because if I find a procedure
> called "test" which does what the procedure above does, and which
> appears to be "the issue", the first questions I am going to ask are:
> What is this supposed to do? Is it doing that? Is it needed at all? If
> it is, when is it needed? Why is it not documented? Only after
> answering these questions and establishing that the procedure is indeed
> useful and needs to be called as often as it is (which includes
> documenting it and probably renaming it to something more descriptive)
> am I going to look into how to make it faster. (At least in an ideal
> world - if the users are breathing down my neck I might try the obvious
> optimization first and then do it right).
> hp

You are mostly correct in your assumptions. But I am still waiting for some hotshot developer, one who thinks he or she is good enough to be given DBA privileges in a production database to identify the glaring problem in the procedure I created and fix it.

I am already on record stating that I think DBAs should give developers PLUSTRACE in development and test. So I am not trying to stomp on developers egos. My point from the beginning is that developers need the best tools and the greatest access but NOT in prod.

One or more developers keep claiming to be such hotshots that I should rethink my position so I've put up a very simple test, one I give my students at the U as part of their midterm. I'm still waiting for one of you to see the obvious.

Daniel A. Morgan
University of Washington (replace x with u to respond)
Puget Sound Oracle Users Group
Received on Sat Nov 03 2007 - 08:23:19 CDT

Original text of this message