Delete Orphaned records from the BPM_ERRORS table

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

There are orphaned entries in the BPM_ERRORS table that need to be deleted to improve performance.

Run the following query to determine how many records in the BPM_ERRORS table are orphaned.

SELECT count(1)
FROM bpm_errors
WHERE process_instance_id not in (select id from bpm_run_processes)

Environment

All Supported Clarity Releases

Resolution

Run the following query to delete the orphaned records:

DELETE
FROM bpm_errors
WHERE process_instance_id not in (select id from bpm_run_processes)

The number of records should match the one you had as result for the SELECT statement above

Commit;

Note: Starting 16.4.0, it is possible to leverage the internal DB Maintenance job to delete the orphan records as a fix for DE174050

Additional Information

Also check BPM_ERRORS table filling up impacting database performance