My Oracle Support Banner

OCMC SSU/PN: BRM Error Code Not Always Parsed and Printed Correctly (Doc ID 1675974.1)

Last updated on SEPTEMBER 24, 2018

Applies to:

Oracle Communications Online Mediation Controller - Version 6.1.0 and later
Information in this document applies to any platform.

Symptoms

In most cases except of ErrorCodes with some additional parameters (eg. code=ERR_TIMEOUT (108) , code=ERR_BAD_ARG (4) code=ERR_PERF_LIMIT_REACHED (118) ,code=ERR_BAD_ARG (4), errField=EBUF_PIN_FLD_MSID) the OCMC treats BRM response as successful (as designed) and prints ErrorCode=0 in the logs.

The issue cause difficulty to troubleshoot communication and responses form BRM. Especially in fact the Wireshark doesn't have PCP plugin and in situation when Debug not enabled on BRM CM side.

 

From BRM log:

The Error Code is errCode=0.

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
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.