Query Causing Excessive CPU During Business Hours
(Doc ID 2688809.1)
Last updated on JULY 14, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
The following query seems to be causing excessive CPU usage during business hours:
SELECT DISTINCT collections_action_t.poid_DB,
FROM collections_action_t ,
WHERE collections_action_t.account_obj_ID0 = :1
AND collections_scenario_t.exit_t = :2
AND collections_action_t.scenario_obj_ID0 = collections_scenario_t.poid_ID0
AND collections_action_t.status = :3
AND config_action_obj_id0 IN ( 926, 850, 851 )
The user's DataBase Administrator (DBA) has recommended the following index for better performance, which has been tested in non-prod and results are expected.
PIN.COLLECTIONS_ACTION_T(ACCOUNT_OBJ_ID0, CONFIG_ACTION_OBJ_ID0, STATUS)
Would Oracle also aligned with this recommendation?
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