Shrinking Volatile OSM Table Sizes to Increase OSM Performance
(Doc ID 2268291.1)
Last updated on JULY 26, 2018
Oracle Communications Order and Service Management - Version 7.2.0 and later Information in this document applies to any platform.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!