Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Index Partitioning

RE: Index Partitioning

From: DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>
Date: Wed, 30 Oct 2002 20:33:49 -0800
Message-ID: <F001.004F82F6.20021030203349@fatcity.com>


George - Your current indexes are global. I have only used global indexes with partitioning so far. The case against global indexes on partitioned tables is probably overstated because whenever you do any partition type stuff you invalidate your global index and have to rebuild it.

    Firstly with partitions, make sure you've got the Partitioning Option licensed. Once you've cleared that hurdle, come back and we'll talk.

    Secondly, partitions are mainly of benefit with full table scans, and if Siebel has that many indexes, I'd suspect they don't do any full table scans. The other place partitions are helpful are really enormous tables.

Dennis Williams
DBA, 40%OCP
Lifetouch, Inc.
dwilliams_at_lifetouch.com <mailto:dwilliams_at_lifetouch.com>

-----Original Message-----
Sent: Tuesday, October 29, 2002 2:38 PM
To: Multiple recipients of list ORACLE-L

Hi all  

System is Siebel  

Ok I got a couple of tables about 6 GB big, up to 10 million rows.  

Some of the tables come out of the box with 30+ indexes, now for those not aware Siebel does not support the dropping of any indexes.  

I do though know what my indexes is that are hit the most and was thinking of partitioning them and or maybe the tables.  

Firstly  

If I was to partition only the table, Would I have to make any changes to the currently indexes other than rebuilding them.  

Second. Is it possible for to only partition a selected index.

Here I keep on seeing local and global partitions - indexes. From what I can determine Global is bad news.  

How do I do local, what consideration are there.  

Some of the tables/indexes considered is orders, orderliness, shipments, shipments lines, all with well over 5 million records each.  

The queries is not date specific but more account or contact specific for the order if that's helps.  

I was considering partitioning on order_id but again it looks best to use hash partitioning since there is not real way of saying the queries will always go this way.  

Basically trying to reduce the work for Oracle to get to data. All my queries is already using the best possible index.  

Comment, suggestions  

thx  

George


George Leonard

Oracle Database Administrator

Dimension Data (Pty) Ltd

(Reg. No. 1987/006597/07)

Tel: (+27 11) 575 0573

Fax: (+27 11) 576 0573

E-mail:george.leonard_at_za.didata.com

Web: http://www.didata.co.za <http://www.didata.co.za>  

You Have The Obligation to Inform One Honestly of the risk, And As a Person

You Are Committed to Educate Yourself to the Total Risk In Any Activity!

Once Informed & Totally Aware of the Risk, Every Fool Has the Right to Kill or Injure Themselves as They See Fit!  

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: DENNIS WILLIAMS
  INET: DWILLIAMS_at_LIFETOUCH.COM

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).
Received on Wed Oct 30 2002 - 22:33:49 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US