IFW Duplicate Check Implementation
Last updated on JULY 10, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Pipeline Manager
IFW Duplicate Check implementation
Customer is going to implement the IFW duplicate check - in order to reject non-unique EDRs. To evaluate this method below are some of the questions needs to be answered prior to the implementation start.
1) Buffer Limit vs memory occupancy: - Let's assume customer is going to set buffer limit 3 days back, X - the daily number of CDRs generated, Y - the average size of the EDR in the flat file.
Do we have any method/calculator to estimate extra memory sizing which will be consumed by IFW ?
2) The additional memory mentioned in the above will be consumed immediately after restart and visible from OS perspective ?
3) In the below mentioned related documentation:
https://docs.oracle.com/cd/E16754_01/doc.75/e16710/ifw_rate_pipe_processing.htm#BRMPI254, there is a note:
Do not use the DETAIL.CHARGING_START_TIMESTAMP field for duplicate checking"
Please share some background here as why we can not use this "start_timestamp" ?
4) Customer is using the multi-schema setup with BRM account routers in the front. While the integrated schema is a common one in the multischema setup - One can implement the IFW duplicate check as a part of the account router functionality (then the additional memory should be planned on 2 boxes (account routers) instead of the 6 BRM application nodes ? Or it should be implemented on BRM application boxes rather and linked to the different IFW_DUPLICATECHECK tables - each dedicated for particular schema ? Is there any best practice available ?
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