Is It Possible To Execute The Job PMO_DEFERRED_GIDX_MAINT_JOB With Parallel Degree?
Last updated on MAY 16, 2017
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
PMO_DEFERRED_GIDX_MAINT is an internal job introduced in 12c for clearing the orphan data from the global and local indexes which were generated during partition maintenance operations (PMOP). Maintenance operations on indexes can now be performed with the automatic scheduler job SYS.PMO_DEFERRED_GIDX_MAINT_JOB to clean up all global indexes vs. having to wait for the index maintenance as part of the PMOP itself, which can significantly prolong a PMOP. Additionally, this job coalesces the index, which actually returns space to the index, which is not the case with regular index maintenance. This job is scheduled to run at 2:00 A.M. on a daily basis by default.
The PMO_DEFERRED_GIDX_MAINT job may run slower in some environments due to a large number of partitioned tables or due to data volume changes, and may not complete within a day. This can cause the Global Index Maintenance operation to fail. In order to speed up PMO_DEFERRED_GIDX_MAINT, is it possible to run it with a parallel degree.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms