DB Deadlocks Occurred and Application Could not Process New Requests
(Doc ID 2308689.1)
Last updated on SEPTEMBER 26, 2017
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
DB deadlocks occurred and application couldn't process new requests
DB deadlocks happened on production and new orders could not be processed. As the locks didn't clear on their own, DBA killed the blocker SIDs. Still application was not able to process new orders and had to be restarted. The number of CMs kept on increasing during this time frame.
In the cm.pinlog, it shows the below stack trace:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!