Last updated on JULY 08, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Please advise if there is any BRM functionality impact on de-fragmenting to the following tables:
AU_COLLECTIONS_ACTION_T, SCHEDULE_T, COLLECTIONS_SCENARIO_T, and SCHEDULE_INPUT_FLIST_BUF.
And clarify the following questions:
• BRM uses rowids?
• Does it using a materialized view?
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