My Oracle Support Banner

DB Persistence Cache Partition Loss Is Not Loading The Customer Group Cache (Doc ID 2851533.1)

Last updated on FEBRUARY 28, 2022

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.4.0 version, Customer data management

ACTUAL BEHAVIOR
---------------
DB Persistence cache partition loss is not loading the customer group cache

When there is a cache partition loss, ECE will trigger the loading of data from database to cache. This is working fine for customer and balance cache. But the CustomerGroup cache is not getting loaded.

This results in data mismatch in ECE cache (customer group data) and also if such scenario happens in production system, then cluster needs to be restarted.

EXPECTED BEHAVIOR
----------------
During the partition loss, customer group data should get loaded into the cache.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. On ECE 12.0.0.4.0 environment having multiple ECE Nodes across multiple machines ( For example, 3 machines and in each machine 2 ecs nodes are running), kill ECE nodes 
    of machine 2 and 3 to create partition loss scenario.
2.Make sure ECE will trigger the loading of data from database to cache and customer and balance cache loading is working fine.
3.Check whether CustomerGroup cache is not getting loaded.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.