Some of the tables in SAP PI grow very quickly and can cause severe performance problems if archiving or deletion does not take place frequently. For more information on troubleshooting - SAP Note 872388 – Troubleshooting Archiving and Deletion in PI.
Log in to the 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
Table :SXMSPMAST, cleaned up by XML message archiving/deletion,If the switch procedure is used, please check SXMSPMAST2 as well.
Table :SXMSCLUR / SXMSCLUP ,cleaned up by XML message archiving/deletion.If the switch procedure is used, please check SXMSPCLUR2 and SXMSCLUP2 as well.
Table :SXMSPHIST ,cleaned up by the deletion of history entries.If the switch procedure is used, please check SXMSPHIST2 as well.
Table :SXMSPFRAWH and SXMSPFRAWD, cleaned up by the performance jobs,For more information, go thru SAP Note 820622.
Table :SWFRXI*, cleaned up by specific jobs, For more information, go thru SAP Note 874708. for deleting Message Persistence Data in SWFRXI*
Table :SWWWIHEAD, cleaned up by work item archiving/deletion
PI Message tables: BC_MSG and BC_MSG_AUDIT,when audit log persistence is enabled.
PI message logging information when staging/loging is used, Table : BC_MSG_LOG_VERSION
Table :XI_AF_MSG ,stores incoming and outgoing messages in Adapter Engine
Table :XI_AF_MSG_AUDIT,audit log entries for messages stored in XI_AF_MSG in Adapter Engine
Table :XI_SEC,for security message archiving in Adapter Engine
In general, 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 set up.