How to Improve Performace of SXI_MONITOR?

[former_member228357]

How to Improve Performace of SXI_MONITOR?

Dear Experts!,

I have faced  Performace's Issues on SXI_MONITOR @ PI

When I try to open a XML Message, it's exagerated slow. I can open the messages, but It takes forever.

I'd like to know if someone knows how to improve and optimize the Performace.

Is there any cacher or parameter I could change?

Best Regards,

Denner da Silva Florentino Andrade

[former_member186851 · Accepted solution]

Check the below discussion

SXI_MONITOR is slow | SCN

[former_member228357 · Accepted solution]

Hello Mr Sritharan,

It was helpful but I'd like the procedures to :

- reogranized tables

- how to archived messages.

best regards,

Denner Andrade

[former_member186851 · Accepted solution]

You can call me Raghu.

That solves ur issue?

[former_member228357 · Accepted solution]

Hello Raghu!

I did statistics using DB20 on tables: SXMSPMAST and SXMSPEMAS. I also executed jobs to clean and archive XML messages on SXMB_ADMIN.

but I didn't realize significant improviment. I'd to know what else I could try.

thank you for your help.

Best Regards,

Denner S. F. Andrade

[former_member186851 · Accepted solution]

Hello Denner,

Is the performance affected while opening huge volume message or for every message?

[former_member228357 · Accepted solution]

Hello Raghu,

Yes .  I take 5 minutes when I try to open a single message.

*Duble Click on Message SXI_MONITOR.

thank you again.

Best Regards,

Denner

[former_member228357 · Accepted solution]

Anybody knows if the report: RSXMB_DEL_CLUST_TABLE  on SE38 COULD BE HELPFUL?

[former_member186851 · Accepted solution]

Archiving should help and also talk to Basis team they will have more ideas on this.

[bhavesh_kantilal · Accepted solution]

Hello Denner,

This issue is typically because your SAP PI Archival and Deletion Jobs are not set.

I would strongly recommend going through this document : http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0afdd69-a8a7-2d10-7e9a-cbf6fa21c...

For now would say , trigger the deletion job to clear up the tablespace in your DB..

Regards

Bhavesh

[Bhargavakrishna · Accepted solution]

Hi Denner,

once you activate the switch delete procedure, i suggest you to Run the report

RSXMB_TABLE_SWITCH [Copy XML Messages That Cannot Be Deleted (Incl. Restart)]

Report "RSXMB_DEL_CLUST_TABLE"

Cleanup of tables SXMSCLUP and SXMSCLUR | SCN

Please go though the below links for archive and deletion step by step guide.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0afdd69-a8a7-2d10-7e9a-cbf6fa21c...

PI Archiving Conceptual Overview - Process Integration - SCN Wiki

Also refer the note "1581279"

Regards

Bhargava Krishna

[former_member228357 · Accepted solution]

Hello my friends.

We solve it.

I had to set some parameters on SXMB_ADMIN

then I run the cleaning (delete xml files) on SXMB_ADMIN - I schedule a job for that twice a month.

It was dificult because we never cleaned the xml messages and it was HUGE!

It was important disable archive logs on database  - because this procedure generate too many files - and it is important  to keep the enough space on the datafiles.

thanks for all

best regards

Denner

[former_member228357 · Accepted solution]

You were right.

I set the right parameters on SXMB_ADMIN

than the jobs could delete and archive the XML PI messages.

thank you Bhavesh!

Best regards.

Denner

[former_member187587]

Seems like you describe a message size issue.

As far as I know there is no solution for that.

It is possible that you are sending very large files beyond the PI capabilities.

[former_member228357]

Hello my friends.

We solve it.

I had to set some parameters on SXMB_ADMIN

then I run the cleaning (delete xml files) on SXMB_ADMIN - I schedule a job for that twice a month.

It was dificult because we never cleaned the xml messages and it was HUGE!

It was important disable archive logs on database  - because this procedure generate too many files - and it is important  to keep the enough space on the datafiles.

thanks for all

best regards

Denner

[former_member186851]

Great Denner.

[benedikt_bludau2]

1. Goto transaction SAT.

2. Then insert transaction sxi_monitor and Execute.

3. Open a message and go back.

4. Now you can see a Runtime Analysis. There you can see on which step you have performance problems. Please post a screenshot.

You also can see there some tables. Take the name from the tables with the biggest running time.

Go to transaction DB20 insert the table name and klick on Refresh (Ctrl + F1). With create statistics (Ctrl + F2) you can create new statistics.

regards,

Benedikt

[Eoin_Kierans]

Hello Denner,

If you have applied the statistics (If you're DB is Oracle use the note #1020260) and the archive and deletion jobs are also running you may wish to check if you have a large number of messages in a non final message or adapter status.

Any messages in non final status will not be removed by these jobs. To check this you can run the reports RSXMB_SHOW_REORG_STATUS and RSXMB_SHOW_STATUS.

You may also refer to the KBA #2191585 - The Final Message and Adapter Statuses of PI Messages.

Regards

Eoin