Solution : https://service.sap.com/sap/support/notes/1538437 (SAP Service marketplace login required)
Summary :
SAP's PI system may face extensive growth in PI message log tables (e.g., SXMSCLUP, SXMSPCLUR) even after reorganization, attributed mainly to the handling of failed messages, which are not considered final unless canceled. This retention occurs despite configured reorganization jobs due to the scheduled RSXMB_RESTART_MESSAGES job, which attempts to restart failed messages. If messages persist without cancellation, the log tables continue to expand. Solutions include canceling permanently errored messages and configuring RSXMB_RESTART_MESSAGES to limit message retries more stringently, aided by specific SAP notes depending on the version and technical adjustments in retry settings in JAVA stack environments.
Key words :
->configuration management->infrastructure->java system properties->services->xpi adapter, found pi message log related tables, runtime workbench->component monitoring->background jobs, configuration parameter deletion max_version batch_retry, runtime workbench java stack, set maximum retry times, related log tables, restart failed xi messages, pi main tables, pi reorganization jobs
Related Notes :
| 872388 | Troubleshooting Archiving and Deletion in PI |
| 791379 | XI Adapter service properties documentation |