PCM_OP_WRITE_FLDS (even Custom Objects) Locks Account or Balance Group Object
(Doc ID 1632449.1)
Last updated on AUGUST 11, 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), after upgrading from 7.2.1 to 7.5, there is a significant increase in lock contention on the BAL_GRP_T table. This has been narrowed down to BRM's new (since 7.2.1) fixed policy of locking 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 the account or balance group objects.
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