Re: PL/SQL and Bind Variables / Literals
From: Mathias Magnusson <mathias.magnusson_at_gmail.com>
Date: Thu, 18 Jun 2009 06:04:28 +0200
Message-ID: <8580d4110906172104o18d1589bjb7a7b35c438749c8_at_mail.gmail.com>
Wouldn't an outline or SQL Profile work better in this case? No code change and no risk of paying for a lot more parsing. You ought to get the same overhead you have now (instead of increasing it) and you would lock the query to an execution plan you are happy with.
Date: Thu, 18 Jun 2009 06:04:28 +0200
Message-ID: <8580d4110906172104o18d1589bjb7a7b35c438749c8_at_mail.gmail.com>
Wouldn't an outline or SQL Profile work better in this case? No code change and no risk of paying for a lot more parsing. You ought to get the same overhead you have now (instead of increasing it) and you would lock the query to an execution plan you are happy with.
Mathias
On Thu, Jun 18, 2009 at 3:19 AM, 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
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jun 17 2009 - 23:04:28 CDT