Database Administration (MOSC)

MOSC Banner

Managing access to PL/SQL code within the DB

edited May 6, 2010 9:04AM in Database Administration (MOSC) 12 commentsAnswered
Here's my dilemma:

We have development staff who, for various reasons, need to be able to perform comparisons of packages, procs, funcs, belonging to schema owners (not them) between environments, using tools such as TOAD, SQLNavigator, etc...

Thus far, I have only been able to come up with 3 methods to allow them to do this, each with its own "issues".

1) Grant select_catalog_role to the developer.  Downside:  In a 10G environment, this not only gives them access to code that we, the DBAs, have in-place for administration purposes, which MAY hold information that we would rather no one else be privy to (yes, I know we could/should wrap the code, but, for the moment that is not desireable), it also gives them the ability to see the hashed passwords of all users, which is, of course,a potential security hole.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center