1330 - Mismatched UA Routing Context

This message is issued in the following scenarios:

1. If routing context is present in a M3UA Data message received by the EAGLE 5 ISS, and no routing key for the receiving M3UA association contains a matching routing context value.

2. If routing context is absent in a M3UA Data message received by the EAGLE 5 ISS, and the receiving M3UA association’s application server is referenced by a routing key containing routing context.

3. If routing context is present in a M3UA ASP-Active or ASP-Inactive or DAUD message received by the EAGLE 5 ISS, and no routing key for the receiving M3UA association contains a matching routing context value, then a UIM will be generated.

4. If routing context is present in a SUA message received by the EAGLE 5 ISS, and no routing key for the receiving SUA association contains a matching routing context value.

Example

RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
3409.1330 CARD 1305,A INFO Mismatched UA Routing Context
ANAME = m3ua_assoc_0003 M3UA RC=3

Legend

ANAME

The name of the M3UA or SUA Association. This is followed by the user adapter type (M3UA or SUA) and the value of the Routing Context received in the message. If the Routing Context is absent from the message, RC will be displayed as “none.”

Alarm Level: No alarm condition. The message is informational only.

Recovery

1. The use of Routing Context in the Eagle Routing Key configuration and the use of the Routing Context by the far-end Application Server should be made to match so that they are either both using Routing Context –OR- they are both not using Routing Context.
2. Contact My Oracle Support (MOS).