Last updated on JUNE 22, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.1 [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 26-Feb-2012***
***Checked for relevance on 16-Dec-2013***
Minor modifications in USC_Map configuration are resulting into significant increase in memory usage for the realtime processing pipeline. After our latest modifications, Pipeline allocates significantly more memory (greater than 100% increase), resulting in memory allocation errors.
Currently there are ~3000 lines configured in IFW_USC_MAP. We have modified 5 of them and after these modifications Realtime Pipeline loading stops at the USC_DATA_Module.
- Can you please provide us with summary of known limitations and recommendations for IFW_USC_MAP configuration regarding pipeline memory usage (i.e. best practice recommendation)?
- Can you please provide benchmarks / guidelines for estimating memory usage based on IFW_USC_MAP complexity and/or number of records in configuration?
- Can you please provide more detailed documentation regarding the OptimizeFor parameter for DAT_USC_Map pipeline module?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms