ECE Pricing Cache Update Failure with Huge Pricing Configuration (Doc ID 2078571.1)

Last updated on MAY 17, 2017

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.2.0.7.0 and later
Information in this document applies to any platform.
Checked for relevance on 17-May-2017.

Goal

On : 11.2.0.7.0 version, Pricing Migration

Scenario:

* The user is having issues with the ImportExport tool to update the ECE cache and force a state transition in ECE from state 3 to 4.
* The user is following the below steps to start ECE and to update ECE cache and is expecting to be able to transit to state 10 to start processing records in ECE:

/*** Start PDC-BRM transformation processes ***/
>> cd ~/opt/PDC_BRM/apps/bin
>> ./startRRETransformer
>> ./startBRETransformer
>> ./startSyncPDC

/*** Start ECE ***/
>> ecebin
>> ./ecc
>> start
>> start configLoader
>> start pricingUpdater
>> start customerUpdater

/*** ImportExportPricing ***/
>> cd ~/opt/PDC/apps/bin
>> ./ImportExportPricing -export -metadata
>> ./ImportExportPricing -export -config
>> ./ImportExportPricing -export -pricing
>> ./ImportExportPricing -ow -import -metadata export_metadata.xml
>> ./ImportExportPricing -ow -import -config export_config.xml
>> ./ImportExportPricing -ow -import -pricing export_pricing.xml

Question:

1) If ECE needs to be stopped (for some reason), are the above steps the correct way to update ECE cache?
2) If there is a huge pricing configuration, does it have to be split into many small files?
 

Solution

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