Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Computing statistics and query plans
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
Sybrand Bakker wrote in message
<948818647.24768.0.pluto.d4ee154e_at_news.demon.nl>...
>query plans are not stored, not even in memory. The associated sql is
simply
>invalidated and reparsed, when you compute statistictiscs, AFAIK
>
>Hth,
>
>--
>Sybrand Bakker, Oracle DBA
><wtgreen_at_my-deja.com> wrote in message news:86keeb$en4$1_at_nnrp1.deja.com...
>> 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 that it
>> 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 query
>> 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 anyone
>> know the answer to this definitively?
>>
>> Thanks
>>
>> --
>> Tim Green
>> ADP, Inc
>>
>>
>> Sent via Deja.com http://www.deja.com/
>> Before you buy.
>
>
Received on Tue Jan 25 2000 - 13:01:17 CST
![]() |
![]() |