Thanks, this was exactly what I was looking for. Excuse my use of the
term "query plan" - my Sybase roots are showing. : ) Do you know by
the way in the documentation where this is stated, however? While I
have suspected as much, I'd like to know where to point others here
that question the accuracy of this statement, which up until this
point, has really just been an assumption of mine.
> I think you have a terminology mix-up there.
> A 'pre-parsed' SQL statement in the shared_pool
> is loosely speaking an in-memory stored execution
> plan. With this interpretation the answer to the
> original question is that such statements are
> invalidated and a new path evaluated automatically.
> Jonathan Lewis
> Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
> >query plans are not stored, not even in memory. The associated sql is
> >invalidated and reparsed, when you compute statistictiscs, AFAIK
> >Sybrand Bakker, Oracle DBA
> >> A question for you Oracle gurus out there...
> >> When an "alter table... compute statistics" is issued, does this
> >> automatically cause Oracle to recompute the stored query plans
> >> already has in memory? I come from the Sybase world where is was
> >> necessary to issue a recompile command on a table or index after
> >> statistics were updated in order to assure that all the in-memory
> >> plans would be recalculated using the new statistics data. I can't
> >> seem to find any mention of this in the Oracle documentation, and
> >> therefore I am hoping that no such step is necessary. But does
> >> know the answer to this definitively?
> >> Thanks
> >> --
> >> Tim Green
> >> ADP, Inc
> >> Sent via Deja.com http://www.deja.com/
> >> Before you buy.
Sent via Deja.com http://www.deja.com/
Before you buy.