I think I would just re-define all_source to include that priv. Just remember to re-run the definition after upgrades, perhaps.
Mogens Jack Silvey wrote: >Good day listers, > >We have some developers that would like to see all the >package bodies in our data warehouse. This is a >reasonable request. > >The developers use Toad, which used the ALL_SOURCE >view. > >I pulled the code for all_source and discovered that >the execute_any priv exclusion is hardcoded in this >view. > >Rather than granting them EXECUTE ANY PROCEDURE to >allow them to get to the code (can you say >resume.ksh?), I have three options I am considering. > >1) give select_catalog_role and asking them to use >sqlplus (let the hatemail ensue) >2) create a new dd view based on all or dba_source and >give them a synonym called ALL_SOURCE in their private >schema to fool toad into seeing dba source >3) create a view in their schema called all_source >that is actually a select on dba_source >4) telling them that once source is in the database it >cannot be seen by anybody, even dbas. > >I have heard that TOAD can use dba_source, but they >have not had luck with this (might be a default role >thing, have not verified). > >Opinions or other options? > >Jack Silvey > > >__________________________________________________ >Do You Yahoo!? >LAUNCH - Your Yahoo! Music Experience >http://launch.yahoo.com > -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mogens =?ISO-8859-1?Q?N=F8rgaard?= INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
