Notice that the index partitions are automatically named the same as their corresponding
table partitions. One of the benefits of local indexes is that when you create a new table partition,
the corresponding index partition is built automatically; similarly, dropping a table partition
automatically drops the index partition without invalidating any other index partitions, as would
be the case for a global index.
Creating Range-Partitioned Global Indexes Creating a range-partitioned global index
involves rules similar to those you use when creating range-partitioned tables. In a previous
example, you created a range-partitioned table called CAT_REQ that contained four partitions
based on the CAT_REQ_DT column. In this example, you will create a partitioned global index
that will only contain two partitions (in other words, not partitioned the same way as the
corresponding table):
create index cat_req_dt_ix on oe.cat_req(cat_req_dt)
global partition by range(cat_req_dt)
(partition spr_sum_2007
values less than (to_date('20070901','YYYYMMDD'))
tablespace idx_4,
partition fal_win_2007
values less than (maxvalue)
tablespace idx_8);
Note that you specify two tablespaces to store the partitions for the index that are different
from the tablespaces used to store the table partitions. If any DDL activity occurs on the underlying
table, global indexes are marked as UNUSABLE and need to be rebuilt unless you include the
update global indexes clause (invalidate global indexes is the default).
Pages:
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853