William, What versions of SAP and Oracle are you using? SAP is really funny about bind peeking and recommends setting the hidden parameter _optim_peek_user_binds to 'FALSE'. There are also several events you should have set (depending on your version of Oracle and SAP) to 'assist' Oracle in executing a correct plan when confronted with SAP generated code. Check the differences between your active parameters and events in QA and PRD. On Fri, Dec 12, 2008 at 3:48 PM, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx>wrote: > I think that's pretty common and not necessarily a bug. I'm not 100% > positive, but I seem to remember reading somewhere that v$sql_shared_cursor > by design only shows some, but not all, of the reasons for not sharing > cursors. > > Regards, > Brandon > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] > On Behalf Of Rich Jesse > > Beware that there is also what I believe to be a bug where all values for > the columns in v$sql_shared_cursor are "N", despite multiple children. > > > 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 > > >