Issue With BRM Sequencer Pool (Doc ID 1597662.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

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

Goal

Need to understand why BRM Sequencer Pool skips some sequence numbers

When generating sequence numbers for a custom report using BRM sequencer pool, the report is getting generated by skipping some sequence numbers (randomly).

E.g: ASAPRE_detailed_20130920020600_000001.dat
ASAPRE_detailed_20130920020600_000002.dat
ASAPRE_detailed_20130920020600_000003.dat
ASAPRE_detailed_20130920020600_000005.dat
ASAPRE_detailed_20130920020600_000006.dat
ASAPRE_detailed_20130920020600_000009.dat

Sequencer pool is being used as follows:

MVNO_XXXXX

{
Source = Database
Controller
{
SequencerType = Generation
DatabaseConnection = ifw.DataPool.Login
ReuseGap = False
SequenceLength = 6
}
}
 

Solution

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