(OO) Support Tip: Purge Execution Summary flow and OO_EXECUTION_STATES table
This environment was upgraded. The Purge Execution Summary flow (HPE Solutions content pack) was used to delete old executions. Following that, it was discovered that the OO_EXECUTION_STATES table was very large (more than 80 GB in size). Why is this database table so large? What may have caused this? Is it possible to purge this database table and how to do so?
Before the upgrade, the purging scheduled task was not stopped in a clean way during Central shutdown. As a consequence, it could have left the status column in the BLOCKED state. After restarting Central following the upgrade, any subsequent attempts of this scheduled job to execute will not run until the status changes from BLOCKED to WAITING. On the other hand, the BLOCKED status can be reset only by the job that has finished running but there was no such job running because of the reason mentioned above. The solution was to set the queueCleanerJob trigger in the OO_TRIGGERS table to status WAITING and restart the Central service. The queueCleanerJob was triggered and managed to clean the OO_EXECUTION_STATES table after some time.
Enhancement QCCR8C32968 Before upgrade, make sure purging scheduled task has been stopped cleanly has been submitted and can be viewed at https://softwaresupport.hpe.com/km/KM02753326