Solution : https://service.sap.com/sap/support/notes/1055431 (SAP Service marketplace login required)
Summary :
When managing INDX table growth that introduces performance issues for certain SAP applications, consider executing deletion transactions to prune the table size. Oversized INDX tables can slow down computer processes, but with the implementation of SAP Note 623659, entry accumulation can be preempted. Utilize transaction SE91 to include new messaging for packet size limits, modifying the default settings as necessary based on performance analyses. In addition, create and execute the ZINDL_DELETE report, or the INDX_KC_DELETE for newer releases, to selectively erase entries using specified criteria, ensuring operational efficiencies and sustained application performance.
Key words :
latest support package level, goto transaction se91, relid = 'kc'aedat = '00, log deletion functionality, message class gd, report named zindx_delete, report deletes entries, avoid performance problems, packet size determines, report zindx_delete
Related Notes :
| 1390942 | |
| 3992 | Purpose of the table INDX |