Last updated on JANUARY 09, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, High Availability
Failed to stop a remote node from ECE driver machine with ECE in High Availability.
With ECE in HA, when trying to stop a remote node from the ECE driver machine, ecc status showing that the node is not running. However, the node is actually running in the same cluster created by ecs1.
ecc:000> status topology
Host 'xxx.xxx.x.13': ecs1 ecs2 loader query invocation pricingLoader customerLoader customerUpdater1 configLoader pricingUpdater brmGateway productOfferingCrossRefLoader customerGenerator emGateway1 ratedEventFormatter1 proxyServer
Host 'xxx.xxx.x.14': ecs3 ecs4
Host 'xxx.xxx.x.16': ecs5 ecs6
Host 'xxx.xxx.x.17': ecs7 ecs8
===> status: true
response: [ecs1, ecs2, ecs3, ecs4, ecs5, ecs6, ecs7, ecs8, loader, query, invocation, pricingLoader, customerLoader, customerUpdater1, configLoader, pricingUpdater, brmGateway, productOfferingCrossRefLoader, customerGenerator, emGateway1, ratedEventFormatter1, proxyServer]
ecc:000> stop ecs8
Are you sure you want to run the stop command? This COULD remove all data from memory (y/n):
-- Node ecs8 is not running, cannot stop it.
===> status: false
response: Node ecs8 is not running, cannot stop it.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms