Real-Time Rating Problems Due To Rise In The Business Traffic Volume
(Doc ID 787015.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
-- Problem Scenario:
With the rise in real-time traffic (for business-type subscribers), deadlocks as well as long-lasting locks were observed on /balance_group table (bal_grp_t) in the database. These locks are the reason for rejections by the AAA-gateway (high batch-rating rate, above 20-30%), due to timeouts or errors from the real-time engine.
While real-time rating (both consumer- and business-type) was going on, the following processes also were carried out on the same DB:
- UEL (batch rating)
- massive provisioning (that is, CRM operations; e.g. plan purchase, etc.)
Stopping UEL, nothing changed. Stopping provisioning also changed the situation a lot, removing the previously observed long-lasting locks. As a consequence, overall batch-rating rate went down below 0.3%.
Restarting again UEL did not change the batch rating percentage, confirming that the performance issue on rating is indirectly introduced by provisioning, also because each of the CRM event processing lasted too long.
-- Steps To Reproduce:
1) Define a single business account with several (i.e. 1000) services (i.e. SIM lines)
2) Make the customers do traffic (about 3.000 events/hour)
3) Perform CRM activity on that account in parallel (e.g. Purchase Deal operations)
4) Check locks and deadlocks on reservation_list and bal_grp occurring
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