Is It Possible To Execute The Job PMO_DEFERRED_GIDX_MAINT_JOB With Parallel Degree?
(Doc ID 2126370.1)
Last updated on FEBRUARY 21, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Goal
NOTE: In the images and/or the document content below, the user information and data used represents fictitious
data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead,
is purely coincidental and not intended in any manner.
PMO_DEFERRED_GIDX_MAINT is an internal job introduced in 12c for clearing the orphan data from the global 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.
Solution
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
| Goal |
| Solution |
| References |