Real-Time Rating Problems Due To The Business Traffic Volume Raising
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
checked for relevance on 20th Oct 2010
***Checked for relevance on 29-June-2016***
-- Problem Statement:
With the raising of the business-type real-time traffic, deadlocks, as well as long-lasting locks, were observed on /balance_group table (bal_grp_t). These locks are the reason of 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 same DB it also insisted:
- UEL (batch rating)
- massive provisioning (that is, CRM operations; e.g. plan purchase, etc.)
Stopping UEL nothing changed. Stopping also provisioning 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 accont in parallel (e.g. Purchase Deal operations)
4) Check locks and deadlocks on reservation_list and bal_grp occurring
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms