on 07-19-2016 3:13 PM
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,
Check the below discussion
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
PI Archiving Conceptual Overview - Process Integration - SCN Wiki
Also refer the note "1581279"
Regards
Bhargava Krishna
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.