Data Inconsistency Between BRM and ECE
(Doc ID 2500846.1)
Last updated on SEPTEMBER 13, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
1) Regarding the data inconsistency between Billing and Revenue Management (BRM) and Elastic Charging Emgine(ECE) we have the following query.
if we have more accounts in ECE than in BRM because data were no committed by DM (Data Manager) -then how we should equal the data, is ECE cluster full restart with BRM sync method only one available option here ?
2) When upgrading the ECE Patch set - customer needs to stop the replication and start later. After starting the data inconsistency between Disaster Recovery (DR) and primary ECE site is reported - should not be that data during replication stop from the primary site should be queued and dequeued once DR is available ?
How should such scenario work ?
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