Last updated on NOVEMBER 09, 2015
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Observed that there is a performance bottleneck when there are purchase or cancel operations on product or services on an account with multiple subscriptions. From a closer look on DB side, it showed that the below query is taking longer time. As per analysis by the site DBA, creating an index on AU_BILLINFO_T.au_parent_obj_ID0 would improve performance.
select distinct actg_last_t, actg_next_t, actg_future_t, actg_cycle_dom, created_t, poid_DB, poid_ID0, poid_TYPE, poid_REV
where au_billinfo_t.au_parent_obj_ID0 = :1 order by au_billinfo_t.created_t desc
Question is whether creating such index would impact any functionality in an adverse way.
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