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: autotrace issue

Re: autotrace issue

From: Wolfgang Breitling <breitliw_at_centrexcc.com>
Date: Fri, 14 Oct 2005 08:42:34 -0600
Message-ID: <434FC3DA.1070904@centrexcc.com>


You don't, by any chance, have set cursor_sharing to force or similar? How did you gather the table statistics? "options=>'gather auto'" ?

Sanjay Madan wrote:

> Chris,
>
>
> There is an associated problem too. I am not sure whether the 2 are related.
> An autotrace output of FTS or INDX scan doesn't seem to actually
> guarantee an actual run as per the autotrace plan.
>
> i set db_file_multiblock_read_count to 16 with an alter session ( its 32
> right on on the db). THAT makes the autotrace output show an INDX scan
> for the same 1234561 for which it shows a FTS with a
> db_file_multiblock_read_count = 32.
> (block_size is 8192). HOWEVER, the actual run timings for both the runs
> are quite similar.
> But if I specify an Index-hint, it runs in a fraction of that time (
> irrespective of whether the db_f_m_r_c is set to 16 or 32 ...
>

-- 
Regards

Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Oct 14 2005 - 09:45:10 CDT

Original text of this message

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