My Oracle Support Banner

Deadlocks On BAL_GRP_T Table (Doc ID 2030335.1)

Last updated on JULY 08, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.1 to 7.5.0]
Information in this document applies to any platform.


On : version, Balances


Deadlocks are occurring at different times, the select for update on bal_grp_t is causing a problem.

When the account has many service level balance groups, and concurrent operations are being carried out on the service level balance groups of same account, the deadlock is occurring. This occurring at different times.


Deadlocks are observed on global-enqueue of the database.
user session for deadlock lock 0x2f1a470278
sid: 3015 ser: 35045 audsid: 129609086 user: 119/PIN
flags: (0x8100045) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
flags2: (0x40009) -/-/INC
pid: 559 O/S info: user: grid, term: UNKNOWN, ospid: 104244
image: oracle@machine1
client details:
O/S info: user: pin, term: , ospid: 29420
machine: machine1 program: dm_oracle@machine (TNS V1-V3)
application name: dm_oracle@machine1 (TNS V1-V3), hash value=3882011342
current SQL:
select   poid_DB, poid_ID0, poid_TYPE, poid_REV from bal_grp_t   where bal_grp_t.account_obj_ID0 = :1  order by bal_grp_t.poid_id0  for update of bal_grp_t.poid_id0
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
possible owner[xxxx] on resource TX-0xxx00D-0000D789

Deadlocks should not occur.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.