Federation Is Not Working When ECE DB Is Down
(Doc ID 2880419.1)
Last updated on FEBRUARY 12, 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
Elastic Charging Engine (ECE) is configured with persistence to Oracle Database enabled (customer is not using NoSQL).
During the High Availability Testing (HA), it was observed that Federation is not working when Database is brought down for the secondary node.
Customer has started creating few accounts and found out that accounts are not synced to site2 from site1.
Here are some Cache details, after accounts were created:
----------------------------------------------------------------------------------------------------------------------------------------
| Cache Count | DB Count | Cache-vs-DB |
---------------------------------------------------------------------------------------------------------------------------------------
Cache Name | Site1 | Site2 | Status | Site1 | Site2 | Site1| Site2 |
---------------------------------------------------------------------------------------------------------------------------------------
Balance | 216582 | 216561 | NOT OK | 216582 | ---- | OK | ---- |
Customer | 207266 | 207256 | NOT OK | 207266 | ---- | OK | ---- |
CustomerGroup | 207266 | 207253 | NOT OK | 207266 | ---- | OK | ---- |
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 |