This content has been marked as final. Show 3 replies
I have the permission to see the specification and package bodyIt seems that if the permission that allows you to see the code is something like
grant catalog_role to ...or
grant select any dictionary to ...then the export behavior you noted will occur -- as when you export from under the Other Users node.
If you actually own the package the export will work, and perhaps if you have the execute privilege (but I did not check). I will ping the developer. Hopefully you will get an additional response about whether this is expected behavior or a bug.
SQL Developer Team
It seems that the issue is related to the lack of executing privilege.
I managed to export using another user with this privilege.
My user really can not run the objects, can only see them.
The question now is why I can see the specification and package body but I can not save your text to a file?
I'll wait for a response from developer.
Looking at the Save Specification and Package Body code, I can see that we are only querying the ALL_SOURCE view which means we will not find the source in your case. The code needs to determine if the user can access to the DBA_SOURCE view and use that if possible. Working on that change now.