BRM CNE: Localized Strings Are Not Persistent Between CM Pod Restarts
(Doc ID 2824223.1)
Last updated on DECEMBER 08, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-----------------------
reasons.en_US localizes strings are loaded to the BRM database by using loadme.sh file (this is a Billing and Revenue Manager Cloud Native Deployment - BRM CNE).
Entry in the file looks like this:
: load_localized_strings /oms/load/reasons.en_US
Then, loadme.sh and the reasons.en_US are included in the config_jobs directory and helm upgrade is executed.
Later on, it was observed that the previous configuration is deleted from the DB, after a CM POD restart.
EXPECTED BEHAVIOR
-----------------------
The loaded information should be kept on the BRM DataBase, between CM POD restarts.
Changes
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 |
Changes |
Cause |
Solution |