Pipeline Becomes Unusable When A "Double Sequence" Error Is Thrown By The Sequencer
(Doc ID 976065.1)
Last updated on MARCH 29, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.0]Information in this document applies to any platform.
Symptoms
Pipeline becomes unusable when Double Sequence Number error is thrown by Sequencer.
Steps To Reproduce:
Sequence Checking is enabled for TAPIN processing, but when you process the same file that was already processed, Sequencer given Double Sequencer error, which is a valid scenario, but the Pipeline becomes unusable, with the following errors shown in the pipeline log:
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |