Performance Issue On AU_PURCHASED_PRODUCT_CYCLE_F_T Post Upgrade To PS6
(Doc ID 2964609.1)
Last updated on AUGUST 16, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
- Customer has upgraded from Patch Set 3 (PS3) to PS6.
- There was change in the table au_purchased_product_cycle_f_t structure.
- New column last_notification_t has been added.
- Customer is seeing performance issue on this table.
- Below is the sql query:
select rec_id, charged_from_t, charged_to_t, count, cycle_fee_end_t, cycle_fee_start_t, last_notification_offset, last_notification_t, unit
from au_purchased_product_cycle_f_t where obj_id0 = :1
Site database administrator (DBA) has reviewed and suggested to create indexes on au_purchased_product_cycle_f_t(obj_id0). Can customer go ahead with this?
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