Re: Permission to see the procedures

Kline.Michael wrote:

> The need to view the code is stated to be that the DEV database may have
> "new changes" not on PRD. And they have 4 "dev" databases.
>
> So, if he gets a call at 2AM, then he wants to be able to see production
> code.

You might also consider trying to fix the underlying management issue that has led you to the brink of this slippery slope. What's the point of getting a developer into production at 2 AM (presumably an urgent situation) if he or she isn't going to be allowed to fix anything?

Once your first tier trouble-shooting team is able to reliably reproduce the problem, provide a "post production bug fix" environment which has exactly the same code as production, but where developers can re-create the problem at will and test fixes. (similar to other replies in this thread).

Also, your PL/SQL code (in fact all your DDL) should be version controlled, so a developer should be able to check out the current production code into their own test environment at any time.

-- 
Mark Bole
http://www.bincomputing.com



--
http://www.freelists.org/webpage/oracle-l