Rebuild Of Global Indexes After Dropping Partitions With MDM
Last updated on AUGUST 15, 2017
Applies to:Oracle Utilities Meter Data Management - Version 188.8.131.52 and later
Information in this document applies to any platform.
In Meter Data Management version 184.108.40.206 and later how should global indexes be managed when dropping partitions ? Following the partitioning recommendations of your Database Administrator’s Guide without without ILM, the problem appears to be the same.
For example, testing purge of D1_MSRMT, D1_INIT_MSRMT_DATA and other tables by dropping partition or the tablepace that contains them, and performances issues are encountered when rebuilding the global Indexes. It is observed when partitions are dropped or tablespaces containing them, the global indexes are set unusable, and with their volumes, particularly for D1_MSRMT, or D1_INIT_MSRMT_DATA, it costs a lot of time and disk usage to rebuild them even with high parallelism.
Is there any solution to avoid that they are set unusable?
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