Open Billing Fails with Deadlock While Trying to Update the Journal Object
(Doc ID 2003851.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM) version 7.5PS8, deadlocks are seen in the cm and dm_oracle logs during open billing for accounts.
op_bill_make_bill error, Failed billinfo POID = 0.0.0.1 /billinfo 11267427657810 39
<location=PIN_ERRLOC_DM:4 class="UNKNOWN":0 errno=PIN_ERR_DEADLOCK:79>
<field num=^Aopsflds:0,0 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>
DM Logs around the same time:
ERROR op_incflds: do_sql main "update journal_t set poid_rev = poid_rev+ 1,mod_t = :mod_t, cr_ar_disc_amt=NVL(cr_ar_disc_amt, 0)+:cr_ar_disc_amt, db_ar_net_amt=NVL(db_ar_net_amt,0)+:db_ar_net_amt where poid_id0 = :poid_id0" failed 79,id 287397437813328367
E Tue Sep 23 03:06:04 2014 vfaus522 dm:22237 dm_back.c(34):15821:vans074003:UnknownProgramNam4:1411405557:88
DMbe #198: process_op: op 8(PCM_OP_INC_FLDS), err 79(PIN_ERR_DEADLOCK)
The deadlock appears to happen while trying to update journal_t entries.
1 day billing delay is configured in the system and on the Billing Day of the Month (DOM) day, open billing is executed for the accounts.
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