Last updated on NOVEMBER 21, 2014

Applies to:

Goal

In a multi-schema BRM implementation, there seems to be an issue in the sequence generation while using for some custom reports.

Scenario:

*  One is using the out of box (OOB) sequencer module to generate sequence number for some custom reports.
*  The table is on integrate schema and it is referred by all 10 PINs (schemas).
*  Below is the registry snippet :

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

*  See below for example, couple of reports generated with same sequence :

voice_000158_10_20140905124122.dat  ( generated by pipeline on schema 10 )
voice_000158_2_20140905124122.dat  ( generated by pipeline on schema 2 )

voice_000025_7_20140904055844.dat  ( generated by pipeline on schema 7 )
voice_000025_10_20140904055844.dat  ( generated by pipeline on schema 10 )

*  As the source for sequence number is same table, one would expect that the sequence number should never be same for different schema.

Question:

What is the issue in the sequencer module in this scenario ?
 

Solution