My Oracle Support Banner

DB Persistence Site Crashes During Performance Test Causes Data Lost (Doc ID 2794783.1)

Last updated on AUGUST 08, 2023

Applies to:

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


The customer is doing performance test once the persistence database (DB) is enabled on top of Active-Active architecture.
When the usage processing is triggered, after few hours there is a DB archive log error. So Elastic Charging Engine (ECE) is not able to access the ECE DB.
Even when the DB connection is lost, ECE will be able to process the usage because it works in Write-behind mode.
It is noticed that ECE nodes went into ENDANGERED state and there are loss of data in cache. The usage flow is stopped.
It is seen that there are enough heap space, so ECE nodes should not crash.


If DB is down, the usage processing should continue. And if it is hitting some threshold and see the DB is down then it can stop processing without losing data.



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

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