Performance Issue on Pin_bill_accts
(Doc ID 2344214.1)
Last updated on AUGUST 26, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM), 22.214.171.124.0 version,
An user has recently upgraded the system from BRM 7.4 Patch Set (PS) 14 / AIX 6.1 to BRM 7.5PS17 / Solaris 10 with Oracle DataBase 11g.
During the last execution of the pin_bill_accts process, it reached the configured fetch size limit; and upon retry to make a new fetch, it became locked.
Here is the current configuration in $PIN_HOME/apps/pin_billd/pin.conf for the fetch size:
The process entered into a looping and taking a long time to finish. And, after 12 hours of the execution, there were just 4k accounts got processed, it was expected to process 130k accounts.
Verified with below two queries:
1. select actg_next_t, inf2_localtz_days(actg_next_t), dbtimezone, sessiontimezone
where poid_id0 = X
1509933600; 5; -03:00; -02:00
2. select poid_id0, actg_next_t, actg_cycle_dom, inf2_localtz_days(actg_next_t)
where actg_cycle_dom <> inf2_localtz_days(actg_next_t)
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