My Oracle Support Banner

Shrinking Volatile OSM Table Sizes to Increase OSM Performance (Doc ID 2268291.1)

Last updated on JULY 26, 2018

Applies to:

Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.

Purpose

The performance of some queries and delete statements in OSM can be improved by reducing the size of volatile tables.  Because these tables are relatively small, in terms of the number of records, the optimizer is more likely to choose a table scan.  Old partitions of these tables may be empty, but they still have blocks.  Therefore, as the number of partitions grows, these queries must scan a growing number of blocks.

The simple change of reducing the volatile table size has been found to improve order processing performance and reduce the time of certain administrative operations, like cartridge deployment. The more partitions that exist in the system, the larger the benefit by shrinking these tables. For instance, reductions in cartridge deployment times of a few minutes have been observed for systems with a large number of partitions.

Scope

 

Details

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
Purpose
Scope
Details
                                                    
 Changing the Default Initial/Next Extent Storage Size for Volatile Tables
 Reducing the Storage Used by Volatile Tables in Existing Partitions
 For Offline Move Partition (Oracle 11g and 12c)
 For Online Move Partition  (Oracle 12c and above)
 Checking the INITIAL/NEXT Extent Sizes on Existing Partitions

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.