Status HA Changes to ENDANGERED And Never Goes to NODE-SAFE
(Doc ID 2295146.1)
Last updated on DECEMBER 26, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.2.0 and laterInformation in this document applies to any platform.
Symptoms
After a rolling upgrade, the distribution of the partition data never ended, so the StatusHA never returned to NODE-SAFE status.
There was an exception that happened in ecs1 when the rollingUpgrade was running:
ERROR
-----------------------
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 |