Re: Index Range Scan vs Fast full scan
- From: "Ken Naim" <kennaim@xxxxxxxxx>
- To: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxxxxx>
- Date: Wed, 10 Jan 2007 17:56:40 -0500
I must be having a bad day now my copy and paste had the wrong thing
in the buffer.
Plan
SELECT STATEMENT CHOOSECost: 119,032 Bytes: 16,599,249 Cardinality:
164,349
11 SORT GROUP BY Cost: 119,032 Bytes: 16,599,249 Cardinality:
164,349
10 HASH JOIN Cost: 113,891 Bytes: 16,599,249 Cardinality:
164,349
5 MERGE JOIN Cost: 15 Bytes: 33,580 Cardinality: 730
2 TABLE ACCESS BY INDEX ROWID TABLE
UIMSMGR.UTRACCT Cost: 2
Bytes: 1,335 Cardinality: 89
1 INDEX FULL SCAN INDEX
UIMSMGR.UTRACCT_KEY2_INDEX Cost: 1
Cardinality: 89
4 SORT JOIN Cost: 13 Bytes: 22,630
Cardinality: 730
3 TABLE ACCESS FULL TABLE
UIMSMGR.UTRSRAT Cost: 12 Bytes: 22,630
Cardinality: 730
9 PARTITION RANGE ALL Cost: 113,872 Bytes: 21,198,155
Cardinality: 385,421 Partition #: 8 Partitions accessed #1 - #4
8 INLIST ITERATOR
7 TABLE ACCESS BY LOCAL INDEX ROWID
TABLE UIMSMGR.UABOPEN Cost:
113,872 Bytes: 21,198,155 Cardinality: 385,421 Partition #: 8
Partitions accessed #1 - #4
6 INDEX RANGE SCAN INDEX
UIMSMGR.UAB_OPEN_BALANCE_ID_INDEX Cost:
4,714 Cardinality: 7,708,413 Partition #: 8 Partitions accessed #1
- #4
this last line in the plan is what i am trying to change
--
//www.freelists.org/webpage/oracle-l
Other related posts:
