1Z0-060 · Question #205
DBS_IND_PARTITIONS.ORPHANED_ENTRIES contains YES for several index partitions. This is due to the use of deferred index maintenance. Which three methods will remove the orphaned keys? (Choose three.)
The correct answer is A. using ALTER INDEX REBUILD PARTITION once for each affected local index partition B. using DBMS_PART.CLEANUP_GIDX once to clean up orphaned keys in all local indexes. C. using ALTER INDEX COALESCE PARTITION CLEANUP once for each affected global index. Orphaned index entries created by deferred index maintenance can be cleaned up by rebuilding local index partitions, using COALESCE PARTITION CLEANUP on global index partitions, or calling DBMS_PART.CLEANUP_GIDX for a bulk global index cleanup.
Question
DBS_IND_PARTITIONS.ORPHANED_ENTRIES contains YES for several index partitions. This is due to the use of deferred index maintenance. Which three methods will remove the orphaned keys? (Choose three.)
Options
- Ausing ALTER INDEX REBUILD PARTITION once for each affected local index partition
- Busing DBMS_PART.CLEANUP_GIDX once to clean up orphaned keys in all local indexes.
- Cusing ALTER INDEX COALESCE PARTITION CLEANUP once for each affected global index
- Dusing DBMS_PART.CLEANUP_CIDX once to clean up any orphaned keys in all global indexes on
- Eusing ALTER INDEX COALESCE PARTITION CLEANUP once for each affected local index
- Fusing ALTER INDEX REBUILD PARTITION once for each affected global index partition
How the community answered
(30 responses)- A83% (25)
- D3% (1)
- E3% (1)
- F10% (3)
Why each option
Orphaned index entries created by deferred index maintenance can be cleaned up by rebuilding local index partitions, using COALESCE PARTITION CLEANUP on global index partitions, or calling DBMS_PART.CLEANUP_GIDX for a bulk global index cleanup.
ALTER INDEX REBUILD PARTITION physically reconstructs a local index partition from the base table data, discarding all orphaned entries that accumulated during deferred partition maintenance operations such as DROP PARTITION or TRUNCATE PARTITION. Each affected local index partition must be rebuilt individually since local indexes are partition-aligned.
DBMS_PART.CLEANUP_GIDX is an Oracle-supplied procedure that scans all global indexes on partitioned tables and removes orphaned keys in a single invocation, making it more efficient than issuing individual DDL statements per partition. It is specifically designed to handle the orphaned entry cleanup that deferred global index maintenance defers.
ALTER INDEX COALESCE PARTITION CLEANUP on a global index partition merges leaf blocks and explicitly purges orphaned row entries left by deferred maintenance, and is the supported DDL method for targeted cleanup of individual global index partitions. It is distinct from a standard COALESCE PARTITION, which does not remove orphaned entries.
DBMS_PART.CLEANUP_CIDX is not a valid Oracle-supplied procedure; the correct package procedure for cleaning orphaned global index entries is DBMS_PART.CLEANUP_GIDX, making this option non-functional.
ALTER INDEX COALESCE PARTITION CLEANUP is intended for global index partitions to remove orphaned keys, not for local index partitions; applying it to local index partitions will not correctly address deferred-maintenance orphaned entries.
While ALTER INDEX REBUILD PARTITION can reconstruct a global index partition, it is not the recommended or efficient mechanism for orphaned key removal in global indexes - COALESCE PARTITION CLEANUP or DBMS_PART.CLEANUP_GIDX are the correct approaches for global index orphan cleanup.
Concept tested: Removing orphaned keys from deferred partition index maintenance
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/vldbg/maintenance-partition-index.html
Topics
Community Discussion
No community discussion yet for this question.