Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Resetting execution plan

Re: Resetting execution plan

From: Charles Schultz <>
Date: Thu, 30 Nov 2006 09:09:23 -0600
Message-ID: <>

A couple of us did in fact file an enhancement request for this feature. There have also been several threads discussing the pros and cons of such an approach. As far as I understand it, the only current, practical way to reparse (hard) a query is to invalidate (and revalidate) the underlying objects.

On 11/30/06, Yasin Baskan <> wrote:
> I remember seeing an enhancement request for this feature but as far as I
> know it has not been implemented yet.
> *From:* [mailto:
>] *On Behalf Of *LS Cheng
> *Sent:* Thursday, November 30, 2006 3:31 PM
> *To:* oracle-l
> *Subject:* Resetting execution plan
> Hi
> Anyone know a trick which can invalidate a cursor execution plan?
> I know if you run any DDL against a tabble we can invalidate the execution
> plans related to the table but that affects many cursors, I was wondering if
> there is any trick to reset a single cursor execution plan?
> Bu mesaj ve onunla iletilen tum ekler gonderildigi kisi ya da kuruma ozel
> ve Bankalar Kanunu geregince, gizlilik yukumlulugu tasiyor olabilir. Bu
> mesaj, hicbir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve
> para karsiligi satilamaz; mesajin yetkili alicisi veya alicisina iletmekten
> sorumlu kisi degilseniz, mesaj icerigini ya da eklerini kopyalamayiniz,
> yayinlamayiniz, baska kisilere yonlendirmeyiniz ve mesaji gonderen kisiyi
> derhal uyararak bu mesaji siliniz. Bu mesajin iceriginde ya da eklerinde yer
> alan bilgilerin dogrulugu, butunlugu ve guncelligi Bankamiz tarafindan
> garanti edilmemektedir ve bilinen viruslere karsi kontrolleri yapilmis
> olarak yollanan mesajin sisteminizde yaratabilecegi zararlardan Bankamiz
> sorumlu tutulamaz.
> This message and the files attached to it are under the privacy liability
> in accordance with the Banking Law and confidential to the use of the
> individual or entity to whom they are addressed. This message cannot be
> copied, disclosed or sold monetary consideration for any purpose. If you are
> not the intended recipient of this message, you should not copy, distribute,
> disclose or forward the information that exists in the content and in the
> attachments of this message; please notify the sender immediately and delete
> all copies of this message. Our Bank does not warrant the accuracy,
> integrity and currency of the information transmitted with this message.
> This message has been detected for all known computer viruses thence our
> Bank is not liable for the occurrence of any system corruption caused by
> this message

Charles Schultz

Received on Thu Nov 30 2006 - 09:09:23 CST

Original text of this message