Re: Unexpected result from ALL_TABLES

All:
  There was a concern at my work place.  That is why I raised this issue
here.
  A particular user can see only the objects he was given privilege to in
the ALL_ tables.
  I performed some tests, and told the management that it cannot be
revoked.  Some of the packages and functions call some of the Oracle
built-in packages suchs as UTL_FILE, etc., and if we revoke execute on
sys.UTL_FILE from public, that is it., All the dependent objects will become
invalid.  Right?  Then we have to create a new role, assign these to that
role, and give that role to whoever wants.  This is insane.

  Sanity Now, Insanity Later.

  So, let us consider the topic closed.  We need  ALL_ objects so that users
can see the objects they have priv to in these ALL_ views.

  Thank you all.

Ram Srinivasan
--------------------


On 8/9/07, Dennis Williams <oracledba.williams@xxxxxxxxx> wrote:
>
> Jared,  that was a great suggestion to replicate the problem, thanks
>
> I have tried to replicate the problem and am unable to do so. So I guess I
> just have to mark this one up to "anomalyous incident". Fortunately this is
> a verification process so it isn't critical. But based on everybody's
> responses, I feel justified in sticking with ALL_TABLES for this purpose.
>
> Thanks,
> Dennis Williams
>



-- 
Sincerely
Ram Srinivasan
Charlottesville, VA.

Other related posts: