PCM_OP_WRITE_FLDS Locks Account or Balance Group Object
(Doc ID 1632449.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Billing and Revenue Management (BRM), upgraded from 7.2.1 to 7.5, there is a significant increase of lock contention on the BAL_GRP_T table.
This has been narrowed down to BRM (since 7.2.1) newly fixed locking policy either balance group or the account object on any update of any object with a PIN_FLD_ACCOUNT_OBJ reference.
This was also causing deadlock issues with custom batch programs that were doing nothing more than updating or deleting custom objects. It was expected that customer base classes at the least should be able to function (be updated) without unconditional locking of an account or balance group objects.
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 |