Customer Updater Issue in Multi Schema Setup
(Doc ID 2333463.1)
Last updated on DECEMBER 11, 2017
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 Oracle Communications Elastic Charging Engine(ECE), 18.104.22.168.0 version,
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'.
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
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