Sequencer(Checker) Does Not Log Message And Store The Used Number In State Table
(Doc ID 739757.1)
Last updated on FEBRUARY 20, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.3.0.0.0 [Release 7.3.0]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
There are two 2 issues here.
- IFW_SEQCHECK.SEQ_GAPNUMBERS is always -1.
- IFW_SEQCHECK.SEQ_ORIGNUMBER is override by the IFW_SEQLOG_IN.ORIG_SEQNO of last processed TAPIN file.
Steps to reproduce
-------------------
1) Sequencer configured in registry, as:
SEQ_CHECK_TAPIN
{
Source = Database
Controller
{
SequencerType = Check
ReuseGap = True
SequenceLength = 5
DatabaseConnection = ifw.DataPool.Login
Log
{
FileName = sequence.log
FilePath = /dbmb/opt/portal/pinxx/ifw/log
}
}
}
2) For Roaming, try to send three TAPIn File for a partner with following sequence number
1. CDTWNPCHKGM300001; then
2. CDTWNPCHKGM300002; then
3. CDTWNPCHKGM300007;
Following are sequencer state in the steps
SEQ_ORIGNUMBER SEQ_GAPNUMBERS
initial 0 -1
1. 1 -1
2. 2 -1
3. 7 -1
=> finally in ifw_seqcheck:
Sequence Name Key Seq Original Number Seq Gap Number
SEQ_CHECK_TAPIN CDTWNPC 7 -1
3) For Roaming, try to send one more TAPIn File for a partner with following sequence number
4. CDTWNPCHKGM300003;
Following are sequencer state in the steps
SEQ_ORIGNUMBER SEQ_GAPNUMBERS
initial 7 -1
4. 3 -1
=> finally in ifw_seqcheck:
Sequence Name Key Seq Original Number Seq Gap Number
SEQ_CHECK_TAPIN CDTWNPC 3 -1
Actual Results:
1. In step 2, the 3nd processed record, the gap numbers showing "-1".
2. In step 3, the seq_orignumber is showing 3.
Expect Results:
1. In step 2, the 3nd processed record, the gap numbers should be '3,4,5,6'.
2. In step 3, the seq_orignumber should remain as 7.
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 |
Cause |
Solution |
References |