Re: PL/SQL and Bind Variables / Literals
From: Adam Musch <ahmusch_at_gmail.com>
Date: Wed, 17 Jun 2009 21:18:34 -0500
Message-ID: <516d05a0906171918j3f8ec369g8a8d711ec7552785_at_mail.gmail.com>
Well, there's DBMS_SQL.PARSE. And hints. And cursor_sharing=similar with histograms.
Date: Wed, 17 Jun 2009 21:18:34 -0500
Message-ID: <516d05a0906171918j3f8ec369g8a8d711ec7552785_at_mail.gmail.com>
Well, there's DBMS_SQL.PARSE. And hints. And cursor_sharing=similar with histograms.
Execute immediate's far more convenient if it won't trash the shared pool.
Adam Musch
ahmusch_at_spammenot.gmail.com
On Wed, Jun 17, 2009 at 8:19 PM, Thomas Roach <troach_at_gmail.com> wrote:
> Hi Group,
>
> I am looking at options on forcing Oracle to use literals inside of a
> PL/SQL package. I have a bind variable peeking issue that is causing a
> cached execution plan that doesn't work well for all scenarios. To get
> around this (and since the query is executed only a handful of times), I
> want to force the query to use literals inside of PL/SQL. One option I
> thought of is to use execute immediate. I was wondering if anyone had any
> ideas or thoughts if there is a better way to do this.
>
> Thanks,
>
> Tom
>
-- Adam Musch ahmusch_at_gmail.com -- http://www.freelists.org/webpage/oracle-lReceived on Wed Jun 17 2009 - 21:18:34 CDT