packages and bodies not showing in brower

AKL

Member
LS,

PL/SQL Developer Version 10.0.5.1710 (version 9.0.6.1661 as well)

We do see tables and views of an other schema.
We do NOT see packages and packages bodies.
"desc owner.package_name" in a command window result in
"object dos not exists".

Straingly enough the describe DOES work in SQL*Plus and it DOES work in Toad. We can see all those packages and the content of their bodies.
A schema with execute rigths DOES see the objects.
How can I make the packages/bodies visible in PLSQL Developer without granting the execute right?
What well hidden filter seem to be active?

Regards,
Andr
 
I had a similar case:
Strangly enough the view all_procedures does not return any rows, while the view dba_procedures did (=>user has necessary permissions).

To solve the problem for PL/SQL Developer, you have to go to Preferences\Options and check "Use DBA Views if available".
Then you can see the objects.
 
I just observed one more problem:

If you(as a logged in Oracle user) cannot see a Package in the Oracle-View all_procedures (but in dba_procedures), you cannot quick-jump to its definition. Also you can't see the procedure defintion/parameters popup, when moving the mouse cursor over the procedure name.

Reason is: The Oracle-User (and PUBLIC) have no EXECUTE permission on the procedure, but is granted SELECT ANY DICTIONARY.

User "Use DBA Views if available" makes thos packages visible/accessible in the Object Browser, but not in the Program or SQL-Editors.
(Applies to PL/SL Developer 10.0.5)
 
To view the sources you need select privileges on the sys.dba_objects and sys.dba_source views. The "Use DBA views if available" preference needs to be enabled as well. If these conditions are met you should be able to see all package bodies, including the source.
 
I'm able to see the objects/packages and see/open their source with "Use DBA views if available" enabled.

But what is not working is:
- Jump into another package's code with CTRL+MouseClick UNLESS the package is already opened in another program window.
- See the procedure definition/parameters as ToolTip if you place the mouse cursor over such a procedures name in the code.

All this is working well for procedures that can be seen by the all_procedures view, but not for those that only can be seen in dba_procedures view. (A somewhat funny situation but the user is only supposed to see everything but has otherwise very little rights).

 
Back
Top