SAP PI - RELATION_NOT_UNIQUE Error In SXMB_MONI

[vishnu_pallamreddy]

Hi All,

In production system, I got a new message failure.

when I try to reprocess the message it is showing like unable to process the message due to sequence issue.

This message is EOIO sequence.

Error: MAPPING">RELATION_NOT_UNIQUE

Mapping for interface . and sender is not unique Mapping from outbound interface http://sap.com/xi/AIN.EventCaptureNotificationOut and service BS_SAP_AP1_410 (, ) to inbound interface . and service BS_SAP_YP1_310 (, ) is not unique

Please help me to resolve this issue.

Thanks In Advance,

Vishnu.

[iaki_vila · Accepted solution]

Hi VIshnu,

What is your PI version?. The problem could be an inconsistency in the cache. Try to refresh the sxi_cache and test, if the error persists try to do a full cpa cache refresh.

Regards.

[vishnu_pallamreddy · Accepted solution]

Hi Inaki,

Our PI version is 7.3.

Ok I will do SXI_CACHE.

previously I tried with reprocessing, but it is showing like unable to process EOIO message.

[vishnu_pallamreddy · Accepted solution]

Hi Inaki,

i have done cache refresh, even though the message not going through.

it has stucked in SMQq2.

[former_member182412 · Accepted solution]

Hi Vishnu,

It is because of SXI_CACHE got duplicate entries for interface determination, check the cache does it contain multple entries for interface determination?

The below SAP note is for 6.40 version, i think the issue is similar.

709866 - Duplicate entries in the XI cache

Regards,

Praveen.

[vishnu_pallamreddy · Accepted solution]

Hi Praveen,

please find the below screen shot of ID in SXI_CACHE.

why it is showing 0 as sequence for 2 messages?

[former_member186851 · Accepted solution]

Vishnu its failing for all messages or for some particular ones?

[vishnu_pallamreddy · Accepted solution]

Hi Raghu,

It is failed only once.

new messages are running successfully.

[former_member182412 · Accepted solution]

Hi Vishnu,

If you have multiple mapping programs in interface determination then the sequence number will assign like below for interface and interface namespace combination.

• For your screen shot first two entries are two different interface determinations (one for receiver BPM_ASN.. and another one for receiver BS_SAP_YP1_310) for same interface EventCaptureNotificationOut and namespace http://sap.com/xi/AIN combination
• For all 0 to 8 are one interface determination with 9 different mappings, so assigning the sequence from 0 to 8, is this correct can you compare your interface determination in directory?

Why all entries contain same receiver service, namespace and interface? it should be different, can you paste interface determination screen shot here.

Regards,

Praveen.

[vishnu_pallamreddy · Accepted solution]

Hi Praveen,

Please find the ID screen shot.

[former_member186851 · Accepted solution]

Vishnu,

Did you check whether any 2 conditions are satisfied for a particular paylod?

[vishnu_pallamreddy · Accepted solution]

Hi Raghu,

I will check and let you now.

[iaki_vila · Accepted solution]

Hi Raghuraman,

Don't you think the two 0 sequence, one with another receiver service (BPM_...) could be the problem? as Praveen mentioned before. If Vishnu has only one scenario with this interface, why the sxi_cache refresh doesn't delete the old one entry?. I wonder this question right now.

Regards.

[former_member186851 · Accepted solution]

yes Inaki,as both have the same interface.

Delete the entry where?didnt get you,

[iaki_vila · Accepted solution]

Hi Raghuraman,

I wanted to mean that the BPM_ receiver service seems to be an incorrect value according Vishnu screen-shoot, may be i confused in this point.

Regards.

[vishnu_pallamreddy]

Hi All,

I am attaching error screen Shot...

[former_member186851]

Hello Vishnu,

Are you using any message split here?

I guess the same inbound interface is called  multiple times. Check the conditions.

[vishnu_pallamreddy]

Hi Raghu,

Yes, we are using Message split.

and we are using same inbound interface in multiple OM.

the message failed only once and in all the times it is successful.

[former_member186851]

We had the same issue Vishnu,

It was because of same inbound interface called 2 times.

Check the conditions, I believe the problem could be ter.

[vishnu_pallamreddy]

OK Raghu,

I will check.

it was failed only once. it is now running successfully for new messages.

[iaki_vila]

Good comment Raghuraman, i haven't tried to test what will happendif the same inbound interface was called two times in one call. I assume the issue is with sync scenario, isn't it?, with async scenario this problem would be raised as well?

Regards.

[former_member186851]

Even with Async Scenario Inaki.

If the same interface is called multiple times in the same interface determination.

We just sorted out the split condition it worked.

[vishnu_pallamreddy]

Hi Inaki,

in my case it is async message.