Essential permissions for a user to use PL/SQL Developer to fullest effect short of full DBA

[Allen Marshall]

We are encountering a situation where certain folders in PL/SQL Developer are empty, such as Materialized Views, but we need to see the objects and at least View their contents for most users. The powers-that-be want to limit Edit access to most objects to DBAs only, but the DBAs support multiple organizational sections and have no way to know any individual business domain, so they need to be directed to make necessary changes to secured objects. However, if the objects are invisible, this is a bit difficult to do.

Is there a script or table of the appropriate permissions on objects for different user roles with some indication of the corresponding visibility and access level within the PL/SQL Developer UI? In other words, a way to troubleshoot the empty folders based on a given login account (and its role grants).
Thank you.

 

[Marco Kalter]

To view objects owned by other users you may need to enable the "Use DBA Views if available" option on the Preferences > Oracle / Options page.

In this case you will also need select privileges on DBA views like DBA_OBJECTS and DBA_SOURCE.