PCM_OP_WRITE_FLDS (even Custom Objects) Locks Account or Balance Group Object
Last updated on APRIL 13, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, DM & Upgrade
After upgrading from 7.2.1 to 7.5, there were a measurable 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.
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