Some of the tables of SAP PI grow very quickly and can cause severe performance problems if archiving or deletion does not take place frequently.
Log on to your Integration Server and call transaction SE16. Enter the table names as listed below and execute. In the following screen simply press the button “Number of Entries”. The most important tables are:
- SXMSPMAST (cleaned up by XML message archiving/deletion). If you use the switch procedure, you have to check SXMSPMAST2 as well.
- SXMSCLUR / SXMSCLUP (cleaned up by XML message archiving/deletion). If you use the switch procedure, you have to check SXMSPCLUR2 and SXMSCLUP2 as well.
- SXMSPHIST (cleaned up by the deletion of history entries). If you use the switch procedure, you have to check SXMSPHIST2 as well.
- SXMSPFRAWH and SXMSPFRAWD (cleaned up by the performance jobs, see SAP Note 820622 – Standard Jobs for XI Performance Monitoring).
- SWFRXI* (cleaned up by specific jobs, see SAP Note 874708 – BPE HT: Deleting Message Persistence Data in SWFRXI*)
- SWWWIHEAD (cleaned up by work item archiving/deletion).
- Check for all tables if the number of entries is reasonably small or remains roughly constant over a period of time. If that is not the case, check your archiving/deletion setup.
- Use an appropriate database tool, for example, SQLPLUS for Oracle for the database tables of the J2EE schema. There are currently only two central tables known to fill up quickly: BC_MSG and BC_MSG_AUDIT (when audit log persistence is enabled).