Performance Issue During Open Billing
(Doc ID 2913837.1)
Last updated on DECEMBER 09, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM), 18.104.22.168.0 Version,
Running "pin_cycle_fees -regular_cycle_fees" utility cause occasional stuck which significantly impact billing performance. It is also observed that the CM stop responding during thread stuck.
Here Customer used "pin_deferred_act utility" for testing which also have the same symptom. When they execute "pin_deferred_act" utility to call their customized API, it got hang because it locked when calling "op_bill_record_event" to get sequence
After tuning the dm_oracle configurations, they are able to process open billing without thread stuck. However the billing performance is still noticeably slower, compared with their BRM 7.5 setup.
The last Bill Run which they tried for approximately for 12.2 Million accounts with total 100000 products took more than 24 hours to complete.
How to resolve this?
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