Customer Are Not Getting Segregated Into Groups During Loading Customer Through Loader
(Doc ID 2894758.1)
Last updated on FEBRUARY 07, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
In CN instance, during customer load from BRM-DB to ECE cache through customerLoader or customerUpdater, the customers are not getting segregated into groups. This will impact the active-active deployment.
Kindly validate the on-prem preselect_customers.groovy script and align the similar changes in oracle.communication.brm.charging.migration.customer.loader.ECEPreselectCustomer.
Abbreviations:
CN - Cloud Native
BRM - Oracle Communications Billing and Revenue Management
ECE Elastic Charging Engine
DB - Database
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 |
Cause |
Solution |
References |