Balance Group Lock is Resulting in Deadlock During PYMT_COLLECT
Last updated on SEPTEMBER 22, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Collections Manager
Scenario is like:
There are 2 billinfo ( B1 & B2 ) on the account one is active and one is inactive and 2 balance group.
The first billinfo which is inactive ( B1 ) has actg_cycle_dom as 1 and the other one ( Active B2 ) is having actg_cycle_dom as 30.
Now on the active one was created on 30th and was running BILL_NOW and PYMT_COLLECT under one transaction on 1st after the Active billinfo is created.
Now calling BILL_NOW on B2 and a lock is taken on the account as well.
local_tx = fm_utils_trans_open( ctxp, PCM_TRANS_OPEN_READWRITE|PCM_TRANS_OPEN_LOCK_OBJ, acct_pdp, ebufp );
This is how we are opening a transaction before calling BILL_NOW.
Now the BILL_NOW has happened fine and after this it is calling payment_collect on this billinfo. Which internally is calling MAKE_BILL and the account is due for billing. And which is internally resulting in a deadlock.
Please advise how to resolve the deadlock?
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