My Oracle Support Banner

Customer Updater Issue in Multi Schema Setup (Doc ID 2333463.1)

Last updated on AUGUST 23, 2020

Applies to:

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

Symptoms

On Oracle Communications Elastic Charging Engine(ECE), 11.3.0.2.0 version,

Scenario:

On a multi-schema setup the user have configured multiple CustomerUpdater, one for each schema as below:

Here CustomerUpdater1 has finished loading cross reference data & customer data and triggered transition to 'UpdaterBacklogProcessing'. But CustomeruUdater2 has failed and the state is left at state 9 'UpdaterBacklogProcessing'.


STEPS

The issue can be reproduced at will with the following steps:

1) On a multi-schema setup configure multiple CustomerUpdater, one for each schema,
2) ecc:000> start server  
3) ecc:000> start configLoader  
4) ecc:000> start pricingUpdater
5) ecc:000> start customer

Changes

 

Cause

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
Symptoms
Changes
Cause
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.