TAP Files Are Inconsistently Rejected By Batch Rating Pipeline With 'Double Sequence Number' Error
Last updated on OCTOBER 24, 2014
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
When processing TAP files out of order through the Batch Rating Pipeline, it was found that some files are inconsistently rejected with 'Double sequence number' error.
This issue was detected in test environment but cannot be reproduced in development environment.
The test scenario is as following:
1. Created a sequencer “SEQ_CHECK_TAPIN_0311” for the Batch Rating Pipeline that processes TAP3.11 format files.
2. When processed TAP files with sequence in the order of 1,2,3,4,5,6,7,8,9,10,11,12,14,23,24,25,26 and then 15 on different days.
3. When tried to process TAP file with sequence number 15, the error “Double sequence number found (sequence number: '15')” occurred even though it was not processed earlier.
4. On the same day (the day file with sequence number 15 was processed) when tried to process TAP file with sequence number 22 for the first time, the error “Double sequence number found (sequence number: '22')” occurred.
And when processed the same file again, this file information got recorded in IFW_SEQLOG_IN table, but the file got rejected due to other reason.
The same issue is occurring for some other operators also.
What is the root cause of the issue ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms