To test object visibility in SQL*Plus, issue SET ROLE NONE
before issuing other SQL - this will disable all roles and you'll
effectively be in the same environment as your PL/SQL programs
(unless they're AUTHID CURRENT_USER, for which roles are
active.)
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"DA Morgan" <damorgan_at_exxesolutions.com> wrote in message
news:3E79EBBF.C04976D9_at_exxesolutions.com...
> Jeff Kish wrote:
>
> > <snipped>
> >
> >
> > >The error message means exactly what it says. The procedure references some object, most likely
a table or view, for
> > >which you do not have sufficient rights to do what the procedure is trying to do ... select,
insert, update, delete, or
> > >reference.
> > >
> > >If the rights to the object are provided by a role that is insufficient for a procedure. The
rights must be explicitly
> > >granted to the schema.
> > >
> > >Daniel Morgan
> > Thanks. I was pretty sure I had all my rights, but I'll check again. Maybe they were dropped
somehow.
> > Jeff
>
> Remember that the rights to a table interactively can be through a role so testing in SQL*Plus or
another front-end tool are
> meaningless. You need to know the means by which the object privilege was granted.
>
> Daniel Morgan
>
Received on Thu Mar 20 2003 - 11:16:22 CST
