My Oracle Support Banner

Charging Node Reported Error During Startup (Doc ID 2610508.1)

Last updated on NOVEMBER 20, 2019

Applies to:

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

Symptoms

One of the charging nodes, ecs9, reported that it had not started properly during startup while the rolling upgrade process.

However, the Operating System (OS) process was running, and the node was connected to the cluster. The node can be restarted successfully this time.

The following message is what the Elastic Charging Controller (ECC) console returned:

ecc:000> start ecs9
-- Node 'ecs9' started with PID 108449
Cannot access mbean Coherence:type=Node,nodeId=76
 Coherence:type=Node,nodeId=76
-- Node 'ecs9' did not start. Please check logs for potential cause.
===> status: false
[
Status: false
Node: ecs9


What is the cause of this behavior?


 

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
References


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