Purge outdated entries of indexes inside IBM IRIS Safer Payments does not support the concept of span control to limit the scope of removal of all index entries that are older than a defined maximum lifetime period.
The IBM Safer Payments uses a fully automated system for cleaning outdated entries within the limit of maximum lifetime. The lack of limiting the scope of entries to clean does not allow for IBM Safer Payments user control closing the Start End of Day (EoD) job before high traffic time, as the procedure does not stop until it completes purging whole data. For example: The amount of records marked for purging by the system is 50 million, the Start End of Day (EoD) job does not stop until it deletes all unnecessary data, and IBM Safer Payments enters the high traffic period with job running.
Customizing the number of entries to be purged will solve the crucial issue. With proper analysis and configuration, closing the task Start End of Day (EoD) job before peak load period is guaranteed and index will not intensely increase in size without creating unwanted load on CPU.
Do not place IBM confidential, company confidential, or personal information into any field.