Re: Locking production PL/SQL stored procedures

Daniel Pinol wrote:

> Hi,
>
> do you know any way to lock PL/SQL packages?
> I have a production environment on user PROD, and I'm developing
> next release of the application on user DEV. But I'm afraid I
> could
> connect by mistake to PROD, and spoil the system that is on
> production.
> I tried revoking the grant RESOURCE to PROD (it contains
> CREATE PROCEDURE). Then, I cannot create new procedures, but I
> still can 'CREATE or REPLACE' or DROP packages.
> Any suggestion?
>
> Thanks,
> I'll apreciate aan email to dpinol_at_cesca.es

  Well, the problem isn't just you're code, it's the entire production database and all the objects - and data - it contains. You say you have 'user' PROD and DEV, does this mean they are both in the same database? You should always develop away from you're production database. By giving your production database a different sid, schema and password from you're production system, you should have to many problems steering clear of it - especially if you hand it over to a support group in your company.

I suppose you could also try disabling the 'create session' privilege from the application schema owner.

Steve Phelan. Received on Tue Jun 03 1997 - 00:00:00 CEST