Global Index Maintenance (GIDX) on Partitioned Tables not Running Asynchronously in 12c+
(Doc ID 2404701.1)
Last updated on FEBRUARY 22, 2024
Applies to:
Oracle Cloud Infrastructure - Database Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.
Symptoms
You are running RDBMS version 12c or higher and still see the synchronous global-index-maintenance (GIDX) behavior. The SQL that indicates synchronous GIDX maintenance is running is the following recursive SQL:
Changes
Starting in 12.1.0.1, GIDX maintenance after partition maintenance operations (PMOPs) using the UPDATE INDEXES clause happens asynchronously. It also introduces index coalesce in addition to cleanup_orphans operations. The asynchronous nature allows the PMOPs DDL to run faster and reduce the window where we hold a DML lock on the partition that blocks other operations. This maintenance is done via the dbms_scheduler job PMO_DEFERRED_GIDX_MAINT_JOB, which runs during the maintenance window, by default.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |