My Oracle Support Banner

Unable To Publish Messages Containing Custom Fields To AQ Due to EAI Errors (Doc ID 753337.1)

Last updated on MARCH 01, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.
***Checked for relevance on 10-Aug-2011***
*** Checked for relevance on 05-27-2016 ***


When calling the publish opcode (opcode # 1301 ) from testnap or when
publishing a message just by replacing the custom field in payload by a standard BRM field, it is
successful (checked both in cm, eai_js logs and in AQ).

Following are the output at the testnap prompt:-

nap(698)> r publishcall 1
nap(698)> xop 1301 0 1
xop: opcode 1301, flags 0
XOP "1301" failed: err 42:PIN_ERR_NONEXISTANT_ELEMENT, field 0/0:0,
loc 16:PIN_ERRLOC_JSAPP, errclass 0:UNKNOWN, rec_id 0, resvd 0
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] /error_poid -1 0
<location=PIN_ERRLOC_JSAPP:16 class=UNKNOWN:0
<field num=0:0,0 recid=0 reserved=0 reserved2=0
<facility=0 msg_id=0 version=0>

When a custom field is added in the payload config file, account creation fails as is not able to publish messages to AQ.




To view full details, 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 a vibrant support community of peers and Oracle experts.