My Oracle Support Banner

ECE CustomerUpdater DID Not Sync All BRM Accounts During Cold Startup (Doc ID 2496789.1)

Last updated on MARCH 19, 2024

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.8.0 and later
Information in this document applies to any platform.

Goal

On Elastic Charging Engine (ECE) 11.3.0.8.0 version, Customer data management

During the cold startup, ECE customerUpdater is not synchronizing all Billing and Revenue Management (BRM) accounts and ECE goes into usageProcessing state.

In one of the user environments, 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 has 1.7 million such hierarchies. The problem is that customerUpdater synchronizes only 1.6 million accounts and ECE goes into usageProcessing state, leaving almost 50% accounts not synchronized.

Below is the startup procedure when ECE customerUpdater mis-behaviour was observed:

1. cd $ECE_HOME/bin
2. ./ecc
3. ecc:> start server
4. ecc:> start configLoader
5. ecc:> start pricingUpdater
6. wait until ECE goes into PricingDataLoaded state
7. ecc:> start customerUpdater

ERROR:

 
How to resolve this?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.