AIA 2.0 - Getting Data From AIA.BSR_SYSTEMS Stops Working After A While (Doc ID 1284295.1)

Last updated on FEBRUARY 14, 2022

Applies to:

Symptoms

On : AIA Comms 2.0 version, Composite App Validation

After clean installation of SOA and AIA 2.0.0 system seems to work correctly.
Executing OOTB AIA ProcessSalesOrderSiebelReqABCSImpl with example xml input data ends fine, i.e. process is closed with status Completed.
All AIA CAVS tests are working fine; all Passed. After some time running the same process ProcessSalesOrderSiebelReqABCSImpl (the same input) ends with status Faulted.
AIA CAVS tests end with Passed status except one, i.e. getEBMHeaderSenderSystemNode, which ends with Failed status, below is the error that occurs.

ERROR
-----------------------
<2010-11-04 08:50:20,284> <ERROR> <default.collaxa.cube.xml> ORABPEL-09500

XPath expression failed to execute.
Error while processing xpath expression, the expression is "ora:processXSLT('SiebelMessage_To_ProcessSalesOrderEBM.xsl',bpws:getVariableData('inputVariable','payload'))", the reason is file:///../app/oracle/product/10.1.3/mtsoa/bpel/domains/default/tmp/.bpel_ProcessSalesOrderSiebelReqABCSImpl_1.0_<xxx>.tmp/SiebelMessage_To_ProcessSalesOrderEBM.xsl<Line 944, Column 31>: XML-22044: (Error) Extension function error: Error invoking 'lookupXRef':'oracle.tip.xref.exception.ValidationException: Reference Column Name is empty for Cross Refrence Table Name "SALESORDER_ID"
Please ensure Reference Column Name is not-empty'
.
Please verify the xpath query.

<2010-11-04 08:50:20,421> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
oracle.as.j2ee.transaction.tpc.ProtocolErrorWithNotification: Branch [oracle.oc4j.sql.xa.EmulatedXAResource@<connection_string>, Xid( Global Id<global id>, Format Id <format id>, Branch Id <branch id>), oracle.oc4j.sql.xa.EmulatedXAResource@<connection_string>, state={PREPARED}, exception error code=] in transaction Global Transaction Xid( Global Id <global id>, Format Id <format id>), type=orabpel, state=COMMITTING, time in completion or recovering=2)
{
[oracle.oc4j.sql.xa.EmulatedXAResource@<connection_string>, Xid( Global Id <global id>, Format Id <format id>, Branch Id <branch id>), oracle.oc4j.sql.xa.EmulatedXAResource@<connection_string>, state={PREPARED}, exception error code=],
[oracle.oc4j.sql.xa.EmulatedXAResource@<connection_string>, Xid( Global Id <global id>, Format Id <format id>, Branch Id <branch id>), oracle.oc4j.sql.xa.EmulatedXAResource@<connection_string>, state={PREPARED}, exception error code=]
} returned RB* during commit.
at oracle.as.j2ee.transaction.tpc.Coordinator$Action.processRB(Coordinator.java:1133)
at oracle.as.j2ee.transaction.tpc.Coordinator$Action.interpretException(Coordinator.java:1090)
at oracle.as.j2ee.transaction.tpc.Coordinator$Action.processException(Coordinator.java:1049)
at oracle.as.j2ee.transaction.tpc.Coordinator$Action.act(Coordinator.java:1013)
at oracle.as.j2ee.transaction.tpc.Coordinator.doAction(Coordinator.java:687)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Restart Server
2. Run ProcessSalesOrderSiebelReqABCSImpl (with example xml provided in already uploaded files) - works fine
3. Run AIA CAVS tests - All ok
4. Wait few hours
5. Run ProcessSalesOrderSiebelReqABCSImpl - this time errors
6. Run AIA CAVS tests - One of the tests failes, i.e. getEBMHeaderSenderSystemNode ends with Failed status

Cause

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