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 localindexesare useful for OLTP environments.See Also: Oracle9i Data Warehousing Guide for more information about partitionedindexesname, and stores the index partition in the same tablespace as the table partition.Global Partitioned IndexesGlobal partitioned indexes are flexible in that the degree of partitioning and the partitioning key are independent from the table's partitioning method. They arecommonly used for OLTP environments and offer efficient access to any individualrecord.The highest partition of a global index must have a partition bound, all of whose valuesare MAXVALUE. This ensures that all rows in the underlying table can be represented inthe index. Global prefixed indexes can be unique or nonunique. You cannot add a partition to a global index because the highest partition always has a partition bound of MAXVALUE. If you wish to add a new highest partition, use the ALTER INDEX SPLITPARTITION statement. If a global index partition is empty, you can explicitly drop it byissuing the ALTER INDEX DROP PARTITION statement. If a global index partitioncontains data, dropping the partition causes the next highest partition to be markedunusable. You cannot drop the highest partition in a global index.Oracle9i Database Concepts Release 2 (9.2) March 2002 Part No. A96524-01(a96524.pdf) ch 10Unique and Nonunique IndexesIndexes canbeunique or nonunique.Unique indexesguaranteethat notworows of a tablehave duplicate values in the key column (or columns). Nonunique indexes do not imposethis restriction on the column values. Oracle recommends that unique indexes be createdexplicitly, and not throughenabling a unique constraint on a table.Alternatively, you can define UNIQUE integrity constraints on the desired columns.Oracle enforces UNIQUE integrity constraints by automatically defining a unique indexon the unique key. However, it is advisable that any index that exists for query performance, including unique indexes, be created explicitly.Reverse Key IndexesCreating a reverse key index,compared to a standard index, reverses the bytes of eachcolumn indexed (except the rowid) while keeping the column order. Such an arrangementcan help avoid performance degradation with Oracle9i Real Application Clusters wheremodifications to the index are concentrated on a small set of leaf blocks. By reversing thekeys of the index, the insertions become distributed across all leaf keys in the index.Using the reverse key arrangement eliminates the ability to run an index range scanningquery on the index. Because lexically adjacent keys are not stored next to each other in areverse-key index, only fetch-by-key or full-index (table) scans can be performed.Sometimes, using a reverse-key index can make an OLTP Oracle9i Real ApplicationClusters application faster. For example, keeping the index of mail messages in an e-mailapplication: some users keep old messages, and the index must maintain pointers to theseas well as to the most recent.