My Oracle Support Banner

IgnoreEDROnDeadlock Setting Creates Endless Loop (Doc ID 1603778.1)

Last updated on MARCH 14, 2023

Applies to:

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

Goal

On Oracle Communications Billing and Revenue Management(BRM), 7.3.0.0.0 version, Pipeline Manager

IgnoreEDROnDeadlock setting creates endless loop during pipeline rerating.

Scenario:

*  In order to decrease possibility of Out Of Order Events occurrence to minimum one has tried to set IgnoreEDROnDeadlock registry entry to "False" in the rerating pipeline.
*  Expected that after deadlock occurs, the processing will be rolled-back and after retry, the EDR would be processed correctly.
*  But when testing this setting with multiple files, the transactions open were being repeatedly rolled back and unsuccessfully reprocessed (due to deadlock).
*  After approximately 1 hour, processing was manually terminated.
*  pin_event_extract is used to extract events to be re-rated.
*  All accounts use account level balance groups.

Detailed use case:

1) There are 3 types of usage being rated for 200 - 300 accounts. For example, VOICE, DATA, OTHER.

a) Two EDR files for each type of usage (DATA, OTHER, VOICE) and each file contain approximately 2000 records or more.
b) Each file contain only one type of usage e.g. VOICE EDR file contain only VOICE type of usage.
c) There is no issue observed during rating because, parameter IgnoreEDROnDeadlock in main pipeline registry is set to True.

2) Rerate the above mentioned usage with IgnoreEDROnDeadlock registry entry set to 'False' and parallel processing of (three rerate) pipelines dedicated for each usage type.

Expectated result:

Usage is rerated within reasonable time (several minutes).

Actual result:

Sessions processing EDR files of different usage type but containing the same account are repeatedly deadlocked and rolled back. As a result rerating runs for hours.

Process log snippet showing deadlock messages:

What is the recommendation in this production situation?

Solution

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
Goal
Solution
References


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