Re: Partitioned Table Slower - Where's Tim Gorman when you need him?

From: jaromir nemec <jaromir_at_db-nemec.com>
Date: Tue, 8 Jan 2008 22:12:44 +0100
Message-ID: <06d701c8523b$3869b920$3e02a8c0@ADLA>


HI,

> In trying to see if
> partitioning them off to their own partition with local prefixed indexes
> matching the indexes of the original heap table

any chance that due to "prefixing" of the index on the partitioned table the range scan is forced to scan the whole partition? i.e. index on the partitioned table is defined (col_a,col_b) and on the non-partitioned table only (col_b) The predicate col_a = 'X' returns 2.5M rows with is approximately 30% of your 8M rows, i.e. the target data. Verify that the index ASN_ORG_IX is defined identically on both tables except for the LOCAL keyword on the partitioned table.

regards,

Jaromir D.B. Nemec

  • Original Message ----- From: Greg Rahn To: moabrivers_at_gmail.com Cc: oracle-l_at_freelists.org Sent: Tuesday, January 08, 2008 7:04 PM Subject: Re: Partitioned Table Slower - Where's Tim Gorman when you need him?

  It appears that there is a different number of rows being returned from the ASN table. Why is this?

  Rows Row Source Operation

  • --------------------------------------------------- // non partitioned 51560 INDEX RANGE SCAN ASN_ORG_IX (cr=323 pr=0 pw=0 time=464207 us) // partitioned 2540907 INDEX RANGE SCAN ASN_PART_ORG_IX PARTITION: 1 1 (cr=9988 pr=0 pw=0 time=22868284 us)
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jan 08 2008 - 15:12:44 CST

Original text of this message