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

From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
To: Martin Ruthner <ruthner@xxxxxxxxxxx>, "kerry.osborne@xxxxxxxxxxx" <kerry.osborne@xxxxxxxxxxx>, Oracle-L Freelists <oracle-l@xxxxxxxxxxxxx>
Date: Tue, 24 Nov 2009 17:17:11 -0700

So much for that idea - I downloaded and installed patch 5614566 successfully, 
ran dbmspool.sql to recreate the dbms_shared_pool package with the purge 
procedure, set event 5614566 as instructed in MOS 751876.1 and restarted the 
instance.  When I ran the purge procedure, it said it executed successfully, 
however the query still stayed in the shared pool, and then when I tried to run 
purge again it failed with "ORA-6558: buffer in dbms_pipe is full", so I gave 
up at that point.  I'll have to find another way to test . . .


-----Original Message-----
From: Allen, Brandon

Unfortunately, dbms_shared_pool.purge doesn't exist in 10.2.0.2 so I'll have to 
install a patch to add it and do some more testing

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

References:
- Bind variables peeked on first parse, but not on subsequent hard parses
  - From: Allen, Brandon
- Re: Bind variables peeked on first parse, but not on subsequent hard parses
  - From: Martin Ruthner
- RE: Bind variables peeked on first parse, but not on subsequent hard parses
  - From: Allen, Brandon

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

Other related posts: