Last updated on AUGUST 04, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Core Billing
This query with the - SQL_ID - 6d5tfynxyu3gr had bad performance:
It has been executed in pin_bill_accts process, the flist has received a number value as parameter which was an account_obj_id0, and the flist was performed in the OOB fm_bill_utils_bal_grp_lock.c policy.
The query did not have low performance, this query was always in any implementation of BRM, and would appear in the AWRs as it took so much time. What actually happened was that every time you call any opcode, first it blocked the account through this sentence; and at the end of the opcode full execution, it did commit.
Whats was the particular operation that is causing performance problems?
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