FCT_DuplicateCheck Temporary Data Files Are Deleted Instead Of Renamed To .dat
(Doc ID 1246466.1)
Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 18.104.22.168.0
Information in this document applies to any platform.
In BRM 7.4 PS4, the data files (e.g. dupSBS_<TransactionId>.dat) are not created. To be more precise, the temporary data files is always created and populated but it is always deleted at the end of the transaction, even if it is not empty and the transaction commits.
How to reproduce the issue:-
Assumption: BufferLimit = 20100815, StoreLimit = 20100717
1) Process a file that contains :
cdr_1 with date 20100814110000 (yyyymmddhh24miss)
cdr_2 with date 20100816110000
The search key of cdr_1 is stored into DB fine
The search key of cdr_2 is kept in memory but the data file DOES NOT exist so this is not right
The temporary data file was deleted
2) Process a file that contains:
cdr_3 with date 20100814100000 (processed, search key stored into DB fine)
cdr_1 with date 20100814110000 (rejected because it is a duplicate so that's good)
cdr_2 with date 20100816110000 (rejected because it is a duplicate so that's good)
cdr_4 with date 20100816120000 (processed, search key stored into memory , but the data file DOES NOT exist so not good)
3) Stop and Restart IFW
4) Process a file that contains :
cdr_2 with date 20100816110000 (WRONGLY processed and NOT rejected as duplicate)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!