RSA Identity Governance & Lifecycle Data Purging is slow in "Step 7/12 Purging Workflow Custom Tasks". The Data Purging may show Status "In Progress" indefinitely. In addition, the Data Purging process may exceed the (4 hours) configured Data Purging time.
The Database Logs for Run for the Data Purging event will show the following as the last line in the file indicating that Purge Custom Task started but did not complete.
47495347 – Data_Purging_Pkg Purge_Custom_Tasks INFO 12/30/2020 7:32 Starting deleting data from WP_PROCI
This is a known issue in the following versions.
RSA Identity Governance & Lifecycle 7.2.0
RSA identity Governance & Lifecycle 7.2.1
This issue can occur if the customer is using the optional Custom Task Workflow feature.
These versions introduced additional Data Purging for Custom Task Workflow data that was not purged in earlier versions. The first time Data Purging is run on an upgraded version the Data Purging may encounter issues when attempting to purge large volumes of legacy workflow data from Custom Task Workflows. This may occur if the customer historically had a Custom Task Workflow that looped indefinitely and generated a large amount of WorkPoint data.
This issue is resolved in the following versions.
RSA Identity Governance & Lifecycle 7.2.0 P08
RSA identity Governance & Lifecycle 7.2.1 P04
These versions introduce changes to size of batch processing done by the Data Purging routines.
Which results in:
Increase efficiency (speed) of Purging of WorkPoint data.
Reduce size of commits and size of undo space which increases the efficiency of Purging of WorkPoint data.
Allows for incremental forward progress in case of a failure of processing (UNDO).
Prevents failures specifically in purging Custom Task Workflow Data
Prevents Data Purging from exceeding configured Data Purge time.
If Data Purging does progress past this step no further action is required. This typically is a one time cleanup event. If Data Purging cannot be completed and the customer cannot patch to the version where this issue is resolved, please open an RSA Customer Support case and ask for assistance.