Identify the indexing technique you would use to minimize partition maintenance.
A.
Local indexes
B.
Global partitioned indexes
C.
Global nonpartitioned indexes
D.
Both global partitioned and global nonpartitioned indexes
Explanation:
If your priority is manageability, use a local index.
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.
Reference: Oracle Database VLDB and Partitioning Guide, 11g Release 1 (11.1), 2 Partitioning
Concepts
Note:
Local indexes are indexes create on each partition in a table. A local index automatically creates
an index partition for each partition in the table. The index is partitioned by the same key as the
partition key of the table.
A local index is always partitioned by the same partition key as the parent table. You cannot add
or remove partitions in a local index, or in a global index for that matter. You must add and remove
partitions from the parent table. A local index does not need to include the partition key in the list
of indexed columns.
Local indexes provide the best throughput of a query and are used primarily in OLAP and DSS
type environments.