My Oracle Support Banner

ECE Nodes Down and Up with Error (Doc ID 2074943.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version to [Release 11.2.0]
Information in this document applies to any platform.


This note answers some questions to resolve a user reported issue in ECE 11.2 PS5, wherein (two times within a week) Customer Updater was not running.

It failed to be restarted and gave error in customerUpdater1.log.


The user has tried to stop ECE Coherence Nodes one by one following the below process:

i)  stop NODE1, start NODE1
ii)  stop NODE2, startNODE2
     The state suddenly become initial and ECE nodes were starting, but exception was occurring in the logs again and again.
     The splunk event has occurred over 46000 times in the SPLUNK logs (Splunk is third party Coherence monitoring tool)
iv) stop all the ECE processes and try to start again
     The same issue happened again.

Questions and Answers

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
Questions and Answers
 What Caused the ECE Node Crash? How to prevent this?
 What are the pre-requisites one needs to consider before extracting the customer using ODI?
 Is there anyway ECE can skip those failed customers and load only the valid customers?

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