Last updated on JULY 04, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0]
Information in this document applies to any platform.
***Checked for relevance on 09-July-2014***
On one customer production system, the billing performance was very poor.
It was seen from awr reports that following queries are creating dead lock, when there are too many applications trying to generate POIDs (using POID_IDS2).
WHERE NAME = :b1 AND poid_type = '/data/sequence_lock'
The performance issue would happen especially when Payment processing is happening along with Billing. This issue gets resolved, if Payments process is stopped. Payment processing and Billling happens on two separate DM_Oracle chains.
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