My Oracle Support Banner

Enabling Subscriber Trace Requires Rolling Upgrade in Cloud Native Deployment (Doc ID 2992912.1)

Last updated on JANUARY 08, 2024

Applies to:

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

Goal

Scenario:

User is following the below steps to update the Subscriber Trace in the Cloud Native setup:

i) Add or delete or modify all subscriber MSISIDN in subscriberList with space separated values in override-values.yaml
ii) Perform helm install with increased restart count which triggers a rolling upgrade and updates subscriber-trace.xml inside elastic charging server (ecs) pod
iii) updateSubscriber Trace in mbeans via jconsole

- In the above steps one can see that for enabling subscriber trace the rolling upgrade needs to be performed.
- User has 32 ecs nodes in production and performing helm upgrade/rolling upgrade will take around two and a half hours.
- Hence rolling upgrade does not look like a viable option.

Expectation:

What is the solution to update the subscriber trace without performing a rolling upgrade.
 

 

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


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