Highly DB-Intensive Query During Cancel Deal
(Doc ID 978512.1)
Last updated on JUNE 26, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.3.0 to 7.5.0]
Information in this document applies to any platform.
During a cancel_deal operation, it is sometimes observed that the query below is spending a long time returning data, though it appears to be optimized (standing to DB trace logs).
The query is found while the CM pstack shows the process hanging within a call to "fm_act_handle_system_events".
We need to understand what the query is called for and if any optimization is possible?
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