RE: Bind variables peeked on first parse, but not on subsequent hard parses

  • From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
  • To: "kerry.osborne@xxxxxxxxxxx" <kerry.osborne@xxxxxxxxxxx>, "development@xxxxxxxxxxxxxxxxx" <development@xxxxxxxxxxxxxxxxx>, oracle-l <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 25 Nov 2009 15:08:35 -0700

Yes, the dbms_shared_pool.purge procedure worked fine for me in 10.2.0.4.  It 
just didn't work when I installed the patch (5614566) for 10.2.0.2 that is 
supposed to provide the same functionality for that older version.  The 
procedure did execute successfully the first time, but it didn't succeed in 
removing the cursor from the shared pool, and then the procedure failed when I 
tried to run it again.  It might have just been some anomaly with my specific 
configuration, so please don't assume that the patch/procedure won't work for 
you in 10.2.0.2 just based on my one test.

Regards,
Brandon



-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Kerry Osborne

This functionality has been backported to 10.2.0.4 and seems to work
fine.



On Nov 25, 2009, at 4:01 AM, Martin Bach wrote:

> Hmm, that's too bad.
>
> The 10.2.0.4 option to purge a statement from the shared pool was
> something I was really looking forward to using.
>


Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 11-2009