Local Partitioned Indexes

Local partitioned indexes are easier to manage than other types of partitioned indexes.
They also offer greater availability and are common in DSS environments. The reason
for this is equipartitioning: each partition of a local index is associated with exactly one
partition of the table. This enables Oracle to automatically keep the index partitions in
sync with the table partitions, and makes each table-index pair independent. Any
actions that make one partition's data invalid or unavailable only affect a single
partition.

Local partitioned indexes support more availability when there are partition or
subpartition maintenance operations on the table. A type of index called a local
nonprefixed index is very useful for historical databases. In this type of index, the
partitioning is not on the left prefix of the index columns.

You cannot explicitly add a partition to a local index. Instead, new partitions are added
to local indexes only when you add a partition to the underlying table. Likewise, you
cannot explicitly drop a partition from a local index. Instead, local index partitions are
dropped only when you drop a partition from the underlying table.

A local index can be unique. However, in order for a local index to be unique, the
partitioning key of the table must be part of the index’s key columns. Unique local
indexes are useful for OLTP environments.

區域性索引分割槽與表分割槽同步，一一對應.
區域性非字首索引對於歷史資料庫非常有用.
不能顯示的新增刪除分割槽於區域性索引.
表的分割槽鍵需為索引鍵的一部分才能構建唯一的區域性索引，對於OLTP環境非常有用.

[@more@]