Cache Differences Between Primary and Secondary Site
(Doc ID 3060100.1)
Last updated on NOVEMBER 29, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Goal
In a cloud native deployment of Elastic Charging Engine, with a Disaster Recovery (DR) setup as active - warm standby, there were differences in cache count observed in below scenario:
Scenario:
- Stopped traffic to production (active site)
- Stopped federation from production to DR site (warm standby site)
- Stopped production by shutting down ECE and Billing and Revenue Management. (The reason for this procedure was a hardware upgrade on the production database servers)
- DR Diameter Gateways were down with DR Elastic Charging Server (ECS) nodes running but not receiving any requests
- Restarted production from persistence
- Performed replicate_all from production to DR
- Performed rolling restart of DR ECS nodes
- Performed replicate_all from production to DR
- Cache counts were compared between the two sites and below differences were observed (first line is from production, second is from DR site):
< AggregateObjectUsage : 16
---
> AggregateObjectUsage : 10< ServiceContext : 99
---
> ServiceContext : 38< ActiveSession : 2788
---
> ActiveSession : 102956< BillingTriggerCycleInfo : 0
---
> BillingTriggerCycleInfo : 114035
What could be the reason behind the differences?
Solution
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
Goal |
Solution |
References |