Re: partitioning questions

Actually, even without the date field, queries will still benefit from the partition-wise join on the charge_id column. You would see something like this (partition hash all) in the plan:

SELECT STATEMENT CHOOSE (Cost=178026)
  PARTITION HASH ALL 1:4:1
    HASH JOIN

      PARTITION RANGE ALL 1:13:3
        TABLE ACCESS FULL TAB_5 * 1:52:3
      PARTITION RANGE ALL 1:13:5
        TABLE ACCESS FULL TAB_6 * 1:52:5

>>> sfaroult_at_oriole.com 11/23/02 03:19a.m. >>>

> 3) If we range-partition by date, subpartition by hash (charge_id),

  No for the same reason as above. It would be also interesting to check whether you should rather have a LOCAL or GLOBAL index on charge_id in this case.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Binley Lim
  INET: Binley.Lim_at_ird.govt.nz

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).