My Oracle Support Banner

Customer Update Requests Fail to Publish to ECE and Lead to ECE Cluster Instability (Doc ID 2727128.1)

Last updated on MARCH 01, 2024

Applies to:

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

Symptoms

On : 11.3.0.9.0 version, Integration with other product

Custom change or updates from Customer Relationship Management(CRM)system are failing with -304 publish error in connection Manager/Data Manager(CM / DM).
The issue is not consistent and fails randomly, most failure are having timeout error or node failure error in emGateway.
When these error occur, ECE nodes start losing from cluster and in hung state. They re-join very long time later and meantime some customers are also lost in ECE grid.

 





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.