Re: autotrace issue

  • From: Wolfgang Breitling <breitliw@xxxxxxxxxxxxx>
  • To: madan.sanjay@xxxxxxxxx
  • Date: Fri, 14 Oct 2005 08:42:34 -0600

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
--
//www.freelists.org/webpage/oracle-l

Other related posts: