OSM Purge Partition Online Take Long Time
(Doc ID 1663578.1)
Last updated on MARCH 20, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.2.0 and laterInformation in this document applies to any platform.
*****Currency checked on 13 Oct 2017 *****
Symptoms
During purge partition, Customer experienced that it was taking very long time during swap partition step (1 hour++). The partition size is 300,000. Below are steps which we use to purge partition.
Note that we stopped at step#2 because it took too long.
2. om_part_maintain.purge_partitions(
a_online => true,
a_delete_before => sysdate + 1,
a_order_states => om_new_purge_pkg.v_all_orders,
a_order_id_ge => null,
a_order_id_lt => 300001,
a_drop_empty_ptns => false);
3. om_part_maintain.drop_empty_partitions(1,300001);
4. om_part_maintain.purge_xchg_prg_tables;
During step#2, we observed that below statement was iteratively going through every single partition even though table is empty. OSM has a lot of sub partitions across many tables. This is suspected to be causing the slowness. Is there anything we can do to improve the time taken for purging partition process?
Changes
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 |