Re: Stored Outlines in 10gR1

At this point, it is one single statement for one specific business function that is the issue, so I would prefer to go with a stored outline so as to minimize the impact on any other processes. 

Wolfgang Breitling wrote:

At 10:46 AM 12/26/2006, A Joshi wrote:

Have you considered setting hidden parameter :
_OPTIM_PEEK_USER_BINDS=FALSE 
The default it true. for details metalink : *387394.1
*when googling also do metalinking,askoming.
Do you have gather statistics using histograms? You can think of changing that since that will not involve much changes and will not need bounce. Thanks
I second the call to verify that the histogram is needed. Problems with plan differences due to BV peeking are usually due to inappropriate histograms. Changing _OPTIM_PEEK_USER_BINDS should be the last resort even *after *trying the stored_oulines. Unless there are very many stored outlines to create. Then setting _OPTIM_PEEK_USER_BINDS=false, perhaps by session in an after logon trigger, could be the lesser "evil" (not that stored outlines are evil). 


Regards

Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com <http://www.centrexcc.com/>

Other related posts: