SAP PI71 production SXMB_MONI is very slow

[Former Member]

Hi All,

we have SAP PI71 in development/quality/production.

But when I am checking SXMB_MONI in Production it is very very slow compared to development/quality SAP PI servers.

some time we are getting time out in SXMB_MONI if we give more date range.

And some time we are getting ST22 "Time out dump" saying "CL_XMS_PERSIST================CP" has exceeded the maximum permitted uninterrrupted runtime.

Even when we increase time limit to 1200 seconds of profile parameter "rdisp/max_wprun_time". we are facing PI production very slow.

We already configured Archive/delete jobs and which are archiving/deleting 30 days old messages in SAP PI in development/quality/production.

But still SXMB_MONI in production is very very slow.

Can any one guide any other maintainer activity/cleanup activity we need to perform in SAP PI71 production servers. by BASIS & by PI developer? which will make PI server faster.

Regards

[marksmyth · Accepted solution]

Hello

What DB do you use? If Oracle, apply the note #1020260 Delivering Oracle statistics. This will improve the performance in sxmb_moni.

Regards

Mark

[Former Member]

Hi Rohan,

did you already setup Message deletion and archiving.

Please check SXMB_MONI=>Persistence Layer analysis. There you will see how many messages you have in the system.

If you have not setup deletion/archiving you should do so in SMXB_ADM

First you will need to define the retention period (i.e. how long messages are kept in system) and which interfaces you want to archive. All other interfaces are only deleted not archived.

Please note, that the setting for archiving only has effect for new messages after this setting has been made. All previous messages will be deleted once you scheduled the deletion job.

Hope this was helpful.

Best regards,

Markus

[Former Member]

Hi,

Check below link :-

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2016a0b1-1780-2b10-97bd-be3ac6221...

many document available on SDN pertaining to sizing and performance on PI server.

Ur case might be of heap memory issue.

chirag