Getting PIN_ERR_DEADLOCK Error During Billing And Adjustment
(Doc ID 2748050.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.22.0 and laterInformation in this document applies to any platform.
Symptoms
Scenario 1. Observed PIN_ERR_DEADLOCK error thrown while getting the lock on account object, during Billing when account has multiple ACTIVE Bill info's with same Billing DayOfMonth (BDOM).
Scenario 2. PIN_ERR_DEADLOCK error thrown when account received usage and adjustment in parallel while acquiring lock on same account object.
ERROR
--------
dm_oracle.pinlog:
E Fri May 22 00:37:03 2020 <HOSTNAME> dm:20620 dm_subr.c(173):9064 2:<HOSTNAME>:19616:-4005571300110:1590133019:2111:root.0.0.0.1:::
ORACLE error: do_sql_mr_select: PINStmtExecute: code 60, op 0
=ORA-00060: deadlock detected while waiting for resource
..
cm.pinlog:
E Fri May 22 00:37:03 2020 <HOSTNAME>cm_billing:19670 cm_utils.c(153):6372 2:<HOSTNAME>:pin_bill_accts:19616:-4005571300110:1590133022:2054:root.0.0.0.1:::
CM FM->DM input flist: opcode=PCM_OP_LOCK_OBJ, flags=0x30000, errno=PIN_ERR_DEADLOCK:79
..
STEPS
-----------------------
Steps to Reproduce scenario 1:
- Create an account with multiple billinfo, all having the same BDOM with some charges.
- Run regular billing using pin_bill_accts
Steps to Reproduce scenario 2:
- Create an account with multiple billinfo, all having the same BDOM with some charges.
- Run regular billing using pin_bill_accts
- At the same time, raise an adjustment to one of the item / event in one of the billinfo
Cause
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
Symptoms |
Cause |
Solution |
References |