Re: Permissions in PL/SQL

Jared,

 Don't know what happened to my post below. I think I've learned my lesson with the hazards of using X$ tables, and was fortunate to find that the DBA_LMT_USED_EXTENTS view is a mirror of X$KTFBUE. Avoids the ORA-2030 errors and allows for a miminum change to the code.

Mike Hand

-----Original Message-----
From: Hand, Michael T
Sent: Thursday, April 09, 2009 11:26 AM
To: oracle-l_at_freelists.org
Subject: RE: Permissions in PL/SQL

 Joel,

I'll have to do more experimentation to get my arms around just what AUTHID does. In the mean time I've converted X$KFTBUE to DBA_LMT_USED_EXTENTS and granted select. The package body now compiles and runs as expected. Thanks for the feedback.

Mike Hand

> -----Original Message-----
> From: Joel.Patterson_at_crowley.com [mailto:Joel.Patterson_at_crowley.com]
> Sent: Thursday, April 09, 2009 10:29 AM
> To: Hand, Michael T; oracle-l_at_freelists.org
> Subject: RE: Permissions in PL/SQL
>
> I'll take stab.
>
> You have to have a direct grant to execute privilege within any
> procedure, function package etc. (not a role). So SYS would have to
> grant directly to owner of code.
>
> If owner A owned some code, and users b, c, and d wished to execute
> A.code with AUTHID current_user.

--
http://www.freelists.org/webpage/oracle-l