Partition_utils Execution Caused Database Performance Issue
(Doc ID 2711575.1)
Last updated on APRIL 19, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Qn1: partition_utils is executed once a month. The user observed that after execution, all the front-end applications took a long time to process. One of the custom opcode, which is mostly doing searches in different storable classes, took more than one hour to execute. Indexes and execution plans were rebuilt to address the issue.
1. What exactly the partition_utils do in database?
2. Could partition_utils process cause slowness in the pcm_op_search process of Billing Revenue and Management (BRM)?
3. Could partition_utils change or erase the execution plan or indexes in database? If yes, what can be done to prevent or avoid this?
4. What could cause or impact on the pcm_op_search process slowness?
5. What is the logic that pcm_op_search uses to create the Structured Query Language (SQL) query and how data manager (DMO/dm_oracle) defines the arguments for the query?
Qn2: Is there documentation or explanation specifically to how the PCM_OP_SEARCH converts into Structured Query Language (SQL) query and defines the quantity of arguments used?
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