Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.0.0 to 7.4.0]
Information in this document applies to any platform.
Checked for relevance on 24-Jan-2010
Checked for relevance on 05-Dec-2013
In order to fix some product issues, the entry relative_cycle_offset was changed from 0 (default) to 1 for all cycle_forward products in production. With the product configuration change in test environment, it was observed that bal_grp_sub_bals_t table size grows very fast.
With current number of subscribers in the user's production system, it will create millions of new rows into bal_grp_sub_bals_t table for non-currency balance impacts each month.
How to manage this table's growth (purge the data) as the user has concern about rating performance?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms