Recommendation For "Orders per Partition" Value When Creating OSM Production Schema
(Doc ID 1062515.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications Order and Service Management - Version 2.6.3 to 7.0.0 [Release 2.6 to 7.0.0]
Information in this document applies to any platform.
***Checked for relevance on 26-APR-2013***
***Checked for relevance on 01-Oct-2014***
***Checked for relevance on 06-July-2016***
OSM order data will be saved into partitioned tables if you choose "Use Oracle Partitioning features for optimal performance in high volume production environment" during installing OSM database schema. However based on several customers production environment, it seems quite often partition limit was poorly configured as only few partitions were created, this will lead into two problems:
1. Completed orders purging problem - purging orders one at a time is time consuming and it will take a long time to purge large amount of orders. Drop partitions is the most effective way, but if there are live/pending orders in all the partitions, you can't use this method.
2. Performance problem - the purpose of partitioning tables is to divide large tables into smaller and more manageable collections of partitioned tables (this is internally done by the magic of the database engine and is transparent to applications). If you have only one partition or several partitions per huge table, you are not using this great feature correctly.
This note is for DBA, OSM Administrators, Consultants who will set up OSM environment for production or performance testing usage.
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