Performance issue on deleting a custom object with 40K custom subobject instances

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When deleting a custom object with many thousands subobjects, this results in app performance issue and may even lead to an outage /  OOM error

1. On a large system with a custom object and many thousands of subobjects each
2. Connect to Clarity in either Classic or MUX
3. Select an instance of custom object with 40K subobject instances added on it
4. Click Delete

Expected Results: The object and the subobjects to be deleted within reasonable time

Actual Results: The application is spinning for over 2 hours and caused row lock contention in Oracle

Error message in logs is continuously thrown although none of the objects is enabled for DWH:

ERROR 2025-08-22 08:22:35,659 [http-nio-80-exec-2] object.ODFObjectImpl (clarity:admin:89942158__58C5D8BE-C186-474D-9F50-46A36A90BA9E:odf.deleteObjectInstances) (3254d1ff-b07b-4c9f-b28c-e842ea2f65d5) Unexpected modified DWH attributes during delete operation.

ERROR 2025-08-22 08:22:35,660 [http-nio-80-exec-2] object.ODFObjectImpl (clarity:admin:89942158__58C5D8BE-C186-474D-9F50-46A36A90BA9E:odf.deleteObjectInstances) (3254d1ff-b07b-4c9f-b28c-e842ea2f65d5) Modified DWH attrs are:

Environment

Clarity 16.2.3, 16.3.0, 16.3.1, 16.3.2

Cause

DE174899

Resolution

Fixed in:

• Clarity 16.4.0
• Clarity 16.3.3.2 (Patch 2)