OCMC SSU/PN: BRM Error Code Not Always Parsed and Printed Correctly
Last updated on OCTOBER 10, 2016
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 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms