My Oracle Support Banner

Queue Processing Is Not Shifting To CDR Processing When MinNumEvents Is Reached (Doc ID 844917.1)

Last updated on MARCH 17, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

On using the Interleaving and defining the MaxNumEvents and MinNumEvents, though the queue processing shifts from CDR processing to Queue processing when the MaxNumEvents is reached, the reverse does not take place when MinNumEvents is reached.

Example:

1> First give some value for MaxNumEvents = 1000 and MinNumEvent = 400
1> Keep the Units per transaction in the Input Module of the pipeline as around 10
2> Create some 2000 CDRs for Input.
3> Create the events >= 1100 in a queue by doing bulk adjustments or any other activity
4> Now observe in the process logs that the CDR processing is shifted to queue processing.
5> But when the queue size reduces to below 400, still the queue processing is not stopped, and the queue size reduces to 0. Then the CDR processing starts.

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.