Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Bad exectution plans due to bind variable peeking

RE: Bad exectution plans due to bind variable peeking

From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Mon, 26 Jun 2006 08:45:22 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45059E1942@NT15.oneneck.corp>


That's what I really did (method_opt=> 'FOR ALL COLUMNS SIZE 1') - I just consider that functionally the same as deleting them since it makes them show up as NONE in dba_tab_col_statistics.histogram, and technically 1 bucket can't qualify as an actual histogram.

Thanks,
Brandon

-----Original Message-----

From: Alex Gorbachev [mailto:gorbyx_at_gmail.com] Sent: Saturday, June 24, 2006 2:59 AM
To: Allen, Brandon
Cc: oracle-l_at_freelists.org
Subject: Re: Bad exectution plans due to bind variable peeking

Actually, you might want to collect them with size 1 instead of deleting completely. This way Oracle has better chances to guesstimate cardinality of the columns.

--

http://www.freelists.org/webpage/oracle-l Received on Mon Jun 26 2006 - 10:45:22 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US