Usage Flow Delay or No Response When ECE DB Is Down (Doc ID 2909736.1)

Last updated on JUNE 23, 2024

Applies to:

Symptoms

Testing the scenario for usage flow when the ECE DB is down. Usage flow works in the write-behind mode, so even if DB is not available, usage flow should go through fine.

Below are the 2 use cases not working:

• Usage flow for site1 works fine and only first usage will not work.   
  During this scenario, ECE will fail the request due to DB unavailability, but the response time is very high. If DB is not available during conditional RUM scenario, it should send failure response immediately. Otherwise it will create timeout in network and lot of re-transmissions.
  
  
• Normal usage flow for site2 customers is not working though it works for site1 customers.
  With active active setup, when the diameter request is sent to site1, based on customer group, it will send request to site1 or site2. In case of site2 customers, the flow is triggered using http gateway. But it is getting timed out.

Steps:

1. Create conditional RUM bundle.
2. Make ECE DB down
3. Start the first usage using DGW after persistence DB is down.

Abbreviations Used:

DB - Database
DGW - Diameter gateway
ECE - Elastic Charging Engine
RUM - Ratable Usage Metric

Cause

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