OCMC SSU/PN: BRM Error Code Not Always Parsed and Printed Correctly
(Doc ID 1675974.1)
Last updated on APRIL 17, 2019
Applies to:Oracle Communications Online Mediation Controller - Version 6.1.0 and later
Information in this document applies to any platform.
In most cases except for 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 Oracle Communications Online Mediation Controller (OCMC) treats Billing and Revenue Manager's (BRM) response as successful (as designed) and prints ErrorCode=0 in the logs.
The issue causes difficulty to troubleshoot the communication and responses form BRM. Especially when Wireshark doesn't have PCP plugin and in situation when Debug is not enabled on BRM CM side.
From BRM log:
The Error Code is errCode=0
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