Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Strange 9.2.0.5 Optimizer Decisions.
Tom:
Thank you for your traces and 10053 outputs. The major difference between those two plans are the table access (CLAIM_FACT). In 2003 this table is accessed by Index and 2004 it is accessed by FTS. From the 10053 trace of 2004, the table access cost is expensive than the index cost, but still it is using the table. I am failing to understand this and suspect this could be a bug unless I miss something obvious.
**BEGIN TRACE**
SINGLE TABLE ACCESS PATH
TABLE: CLAIM_FACT ORIG CDN: 5214450 ROUNDED CDN: 5214450 CMPTD
CDN: 5214450
Access path: tsc Resc: 27875 Resp: 27875
Access path: index (no sta/stp keys)
Index: BMX_CLAIM_SSN
TABLE: CLAIM_FACT
RSC_CPU: 1147794333 RSC_IO: 10824
IX_SEL: 1.0000e+00 TB_SEL: 1.0000e+00
**END TRACE***
Now coming to the Normal (!) tuning process, you may consider creating
a composite index on CLAIM_EFF_DT and CLAIM_SSN and check the response
time. Irrespective of the above, I am still interested in seeing the
10053 trace for the value 2003.
Thanks
Gopal
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Thu Aug 12 2004 - 10:47:34 CDT
![]() |
![]() |