My Oracle Support Banner

Diameter Errors 5012 When BrmPostCommitEnabled Is Enabled (Doc ID 2569992.1)

Last updated on AUGUST 14, 2019

Applies to:

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

Purpose

 About displaying PCM_OP_ECE_POST_COMMIT opcode in cm process log.

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
Purpose
Questions and Answers
 User enabled brm Post (brmPostCommitEnabled="true") commit in ECE and BRM. After enabling they observed PCM_OP_ECE_POST_COMMIT is not being called by BRM. Why ?
 After enabled brm Post commit in ECE and BRM. brmPostCommitEnabled="true". Diameter errors DIAMETER_UNABLE_TO_COMPLY (5012). The below is the error from ECE
 
User is not sure reason for error CUSTOMER_IN_TRANSACTION. What is the cause of this error ?
 What happens to ongoing session if this error occurs. If customer transaction is in progress and network sends UPDATE request and ECE sends CUSTOMER in transaction error, what happens to session in progress. Will Used Service Units [USU] will be captured in session object and session is terminated ? What happens to request?
 Is it diameter gateway has intelligence to retry such failed requests itself ?

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