Re: Problem executing stored function

You can get around the problem by GRANTing EXECUTE to the individual user ( user B ) instead of GRANTing EXECUTE to a role.

Larry Reid wrote:
>
> There's a bug in the way ORACLE looks up PL/SQL functions in SQL
> statements. I don't remember the exact circumstances, but ask your ORACLE
> tech support to look up TAR #946-895 (that's a Canadian TAR. I don't know
> if that makes a difference).
>
> In article <32ED58DA.7A28_at_interramp.com>, "Kevin S. DeWitt"
> <dewitt_at_interramp.com> wrote:
>
> >Thanks for taking the time to read this.
> >
> >I have a stored function created by user A that works fine for user A.
> >However, user B cannot 'see' this function from his SELECT. User A
> >granted EXECUTE privileges to a global role that all users belong to.
> >User A also created a PUBLIC synonym for the stored function. An
> >example follows:
> >
> > SELECT qty_of_trading_instr_executed(100) FROM DUAL;
> >
> >User A returns the correct value. User B gets:
> >
> > PLS-00201: identifier 'QTY_OF_TRADING_INSTR_EXECUTED' must be
> >declared
> >
> >I've also tried prefacing the function name with the schema name. Any
> >ideas as to what I'm doing wrong? BTW, I'm using Oracle 7.1.3 and
> >PL/SQL 2.1.3.
> >
> >Thanks
> >
> >--
> > Kevin S. DeWitt Actium
> > dewitt_at_interramp.com 101 North Meadows Dr
> > 1-888-504-8048 x5006 Suite 113
> > http://www.actium.com Wexford, PA 15090
>
> --
> Larry Reid lcreid_at_web.net
 

-- 
____________________________________
Oleg Dimerman (olegd_at_e-mail.com)