Re: What makes a stored procedure 'INVALID'?

I suspect what you are seeing is the following. The procedure is invalid because the OWNER of the procedure does not have the required privileges on one or more of the objects that are referenced in the procedure.

However, you as the user who is executing the procedure may very well have the required object privileges. So, for you, the procedure runs okay despite the fact that the procedure is invalid.

Regards

Karl

Jeffrey Mark Braun wrote in message <7gq077$eqe$1_at_halcyon.com>...
>I was trying to look this up in our Oracle documentation, but couldn't
>find it, so maybe someone out there knows the answer.
>
>We use a lot of stored procedures, and I refer to the the user_objects
>table quite a bit, but I noticed that many of the stored procedures listed
>in this table have a status of 'INVALID', yet the procedure runs justs
>fine and appears to have nothing wrong with it.
>
>I can imagine if a stored procedure dependence changes (such as another
>stored procedure, table, etc) then the stored procedure might be flagged
>invalid until reloaded, but I reloaded all of our procedures and I still a
>bunch of marked as invalid, although they're working fine for me.
>
>Anyway, just curious what conditions make a procedure invalid.
>
>Thanks.
>
>-jeff
Received on Thu May 06 1999 - 05:23:58 CDT