Message mapping Activation Error

[Former Member]

Hi All,

We have been facing a peculiar problem on Message mapping activation. We are trying to create a new mapping with simple one to one mapping with NO lookups, UDfs. Its a plain one-one mapping. After saving successfully and trying to activate the mapping the following error is displayed up on the Process log. We have observed that even the correct message mappings which were running successfully earlier when attempted to Edit and activate, the same error is repeating and it is across all SWCVs. Please note that we are NOT facing this when trying to create/edit a DTs, MTs and other objects in ESR.

PI Env: PI 7.1

Doubting possible memory issue (as mentioned in earlier threads for similar problem), we have restarted the PI Server including both the ABAP and J2EE server and not met with any success.

Error Details:

Activation of the change list canceled 
Check result for Message Mapping: TEST1 | urn:xxxxx:pi:xxx:poc
Starting compilation
Source text of object Message Mapping: TEST1 | urn:xxxxx:pi:xxx:poc has syntax errors: 
Source code has syntax error:

The development came to a stall due to this problem. Kindly provide your inputs

Regards,

Santosh Kumar

[sriram_devarapalli · Accepted solution]

Hi Santoosh,

Please ask basis to archive or delete the messages.

To Archive:

For this goto tcode SXMB_ADMIN--> Define Interfaces for Archiving and Retention Periods --> select multiple interface which you want to archive and schedule the archiving job in tcode SXMB_ADMIN

To delete

Deleting: All messages with ITFACTION=DEL will be deleted by report RSXMB_DELETE_MESSAGES as soon as message processing is complete (message status is final) and adapter status allows deletion. The Delete job deletes only Payload.

So this will free your space in tables and message mappings will be working now.

Thanks

Sriram

[Former Member · Accepted solution]

Hi Jai & Sriram,

Thank you for your inputs.

I checked with the Basis team and asked for possible Table sizing issues. They confirmed that old messages are filled and some of the records are archived/ deleted. The probelm is solved now.

However we came to face this problem repeated and Basis team has to clear the tables in SXMBADMN one more time.

I can only see a permanent solution being increasing the table size and expand memory allocation. Any suggestions on that?

Regards,

Santosh

[former_member200962 · Accepted solution]

I can only see a permanent solution being increasing the table size and expand memory allocation. Any suggestions on that?

For how long will you keep on increasing the table size? normally to avoid overflowing of tables Archiving and deletion jobs are scheduled.....these take care of releasing the table space.....if you have a high-volume message flow then do schedule it quite often......if messages are not required for further reference then you can even schedule the delete job only.

[Former Member]

Hi Santosh Kumar,

We faced the issue as well a while ago. The root cause of the issue was table space getting filled.

I am not sure if the BASIS team added extra table space or freed up some data base to get rid of the issue.

Regards

Jai