Hello All,
We have to servers (D and U). They are identical. We are developing using the Toad tool. On the D server we all have access to view, and change all of the tables, packages, functions, and stored procedure code. On server U we would only like to VIEW the code behind these objects. NO changes are allowed on server U. Is there some permissioning configuration that will allow this to happen? I have asked our DBA about this and she has told us, the only way to view the code of these objects and not have auth to change it, would be to grant select_catalog_role to <username>. With this, we have to run "select dmbs_metadata.get_ddl(<objecttype>,<objectname>,<owner>)". In short, It would be much easier for us to be able to see this code through the Toad interface. Any suggestions? Can this be done?
Thanks for your time.
-dinzana
We have to servers (D and U). They are identical. We are developing using the Toad tool. On the D server we all have access to view, and change all of the tables, packages, functions, and stored procedure code. On server U we would only like to VIEW the code behind these objects. NO changes are allowed on server U. Is there some permissioning configuration that will allow this to happen? I have asked our DBA about this and she has told us, the only way to view the code of these objects and not have auth to change it, would be to grant select_catalog_role to <username>. With this, we have to run "select dmbs_metadata.get_ddl(<objecttype>,<objectname>,<owner>)". In short, It would be much easier for us to be able to see this code through the Toad interface. Any suggestions? Can this be done?
Thanks for your time.
-dinzana