During Cold Startup ECE CustomerUpdater Is Not Synchronizing All BRM Accounts
(Doc ID 2496789.1)
Last updated on SEPTEMBER 18, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On ECE 18.104.22.168.0 version, Customer data management
During the cold startup ECE customerUpdater is not synchronizing all BRM accounts and ECE goes into usageProcessing state.
In one of the user environment, there are 3.4 million accounts in BRM. Each BRM subscriber is represented by two accounts 1 billing/paying account and 1 service account (where all services are subscribed).Here the user have 1.7millon such hierarchies.The problem is that customerUpdater synchronizes only 1.6million accounts and ECE goes into usageProcessing state, leaving almost 50% accounts not synchronized.
Below Startup procedure used when ECE customerUpdater misbehaviour was observed.
1. cd $ECE_HOME/bin
3. ecc:> start server
4. ecc:> start configLoader
5. ecc:> start pricingUpdater
6. wait until ECE goes into PricingDataLoaded state
7. ecc:> start customerUpdater
How to resolve this?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document