Errors While Processing Cycle-Monthly Sync Events (Doc ID 758593.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 6.5.0.1.1 and later
Information in this document applies to any platform.
Checked for relevance on 23-May-2011


Symptoms

-- Problem Statement:
Sometimes these type of errors are seen in the ifw process log (in a production environment):

18.11.2008 09:23:16 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996532'. Could not determine accounting cycle.

18.11.2008 09:23:17 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996532'. Could not determine accounting cycle.

18.11.2008 09:23:18 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996534'. Could not determine accounting cycle.

18.11.2008 09:23:18 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996534'. Could not determine accounting cycle.

18.11.2008 09:23:18 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996535'. Could not determine accounting cycle.

18.11.2008 09:23:18 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996535'. Could not determine accounting cycle.

18.11.2008 09:23:19 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996536'. Could not determine accounting cycle.

18.11.2008 09:23:19 ese2igs1 ifw IFW CRITICAL 00000 -
(ifw.DataPool.DiscountModelDataModule.Module) Account Id: '16340933745562'. Archive period:
'1226996536'. Could not determine accounting cycle.



The entire list of events dequeued for the above account is:

$ grep 16340933745562 EventBuffer.acc
3799237;CycleMonthly;16340933745562;1100016;3900;1226996532;1228086000;21;0
3799238;CycleMonthly;16340933745562;701100016;3900;1226996532;1228086000;21;0
3799241;CycleMonthly;16340933745562;1201137;52000;1226996534;1228086000;21;0
3799242;CycleMonthly;16340933745562;701201137;52000;1226996534;1228086000;21;0
3799243;CycleMonthly;16340933745562;1201138;13000;1226996535;1228086000;21;0
3799244;CycleMonthly;16340933745562;701201138;13000;1226996535;1228086000;21;0
3799247;CycleMonthly;16340933745562;1201139;303;1226996536;1228086000;21;0
3799248;CycleMonthly;16340933745562;701201139;303;1226996536;1228086000;21;0
3799251;CycleMonthly;16340933745562;701201140;130;1226996536;1228086000;21;0
3799252;CycleMonthly;16340933745562;1201140;130;1226996536;1228086000;21;0
3799257;CustCreate;16340933745562;0;0;1226940758;0;0;0
3799258;CustCreate;16340933745562;0;0;0;1228086000;0;0
3799277;CycleMonthly;16340933745562;701201141;2600;1226996537;1228086000;21;0
3799278;CycleMonthly;16340933745562;1201141;2600;1226996537;1228086000;21;0
3799279;CycleMonthly;16340933745562;701201142;45438293;1226996537;1228086000;21;0
3799280;CycleMonthly;16340933745562;1201142;45438293;1226996537;1228086000;21;0
3799283;CycleMonthly;16340933745562;701201143;465288124;1226996538;1228086000;21;0
3799284;CycleMonthly;16340933745562;1201143;465288124;1226996538;1228086000;21;0
3799285;CycleMonthly;16340933745562;701201168;465288124;1226996539;1228086000;21;0
3799286;CycleMonthly;16340933745562;1201168;465288124;1226996539;1228086000;21;0


Note how the CustCreate is not the first event processed. Among the above, the ones preceding the CustCreate are indeed found in the error log:

$ grep 16340933745562 EventError.acc
3799237;CycleMonthly;16340933745562;1100016;3900;1226996532;1228086000;21;0
3799238;CycleMonthly;16340933745562;701100016;3900;1226996532;1228086000;21;0
3799241;CycleMonthly;16340933745562;1201137;52000;1226996534;1228086000;21;0
3799242;CycleMonthly;16340933745562;701201137;52000;1226996534;1228086000;21;0
3799243;CycleMonthly;16340933745562;1201138;13000;1226996535;1228086000;21;0
3799244;CycleMonthly;16340933745562;701201138;13000;1226996535;1228086000;21;0
3799247;CycleMonthly;16340933745562;1201139;303;1226996536;1228086000;21;0
3799248;CycleMonthly;16340933745562;701201139;303;1226996536;1228086000;21;0


(Except event #3799251 and 3799252; not clear why).

Since the event # is assigned in the same order as the events are dequeued by DAT_Listener and CustCreate must be the first one enqueued, it seems like dequeue ordering is sometimes not the same as the enqueue ordering. Need further verification.

Cause

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