Re: Why do objects become invalid?

"INVALID" is really an unfortunate choice of wording on Oracle's part. All it really is is an indicator to the Oracle Server that it should re-compile the procedure before executing it. It makes sense that they did it this way because if you change a table it's best to defer compilation of stored procedures until you're done making changes, but calling the procedure "invalid" makes people panic...Notable PowerSoft - PowerBuilder refuses to call an invalid procedure - it should call it, because Oracle will recompile it and, in most cases, make it "VALID" again if you just call it.

Winnie Liu wrote:
>
> IF you make changes to the objects which those "invalid" objects depends on,
> such as changes on table. The objects will then became invalid. But the next
> time you call those objects again, (if everything is valid), Oracle will
> recompile that for you again.
>
> Winnie
>
> Violin wrote in message <360a1c6d.7714776_at_news.twsc.pouchen.com.tw>...
> >Hello,
> >I want to ask a question,
> >When I connect as system/mamanger and
> >SELECT * FROM ALL_OBJECTS WHERE STATUS = 'INVALID';
> >I can find some objetcs like procedures,triggers,views become INVALID.
> >And if I recompile the scripts,the objects' STATUS become VALID.
> >But I don't know why?
> >'Cause I don't alter the objects,but they become INVALID.
> >Please give me more information about this.
> >Please Cc to : violin.hsiao_at_mail.pouchen.com.tw,Thank you :-)

--
Adrian Hands
Raleigh, NC

panic: attempt to recv circular datagram in round socket! panic: stack pointer is read-only!
$ Received on Thu Sep 17 1998 - 00:06:51 CDT