Time slicing job failing due to a corrupted object

Products

• Clarity FedRAMP
• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

The time slicing job has started failing continuously and we do not know why. The log file states:

 

ERROR 2026-08-11 06:13:44,739 [Dispatch Time Slicing - Every Minute : mybgservice (tenant=clarity) (BG Job Thread)] niku.blobcrack (clarity:myuser:mysession:Time Slicing - Every Minute) () Exception during blobcrack process

com.niku.union.persistence.PersistenceException: statementSet not found odf-pmd.z_mycustomobject.reset-TSV-status-z_mytsv.map

at com.niku.union.persistence.PersistenceController.<init>(PersistenceController.java:400)

at com.niku.union.persistence.PersistenceController.processRequest(PersistenceController.java:360)

Environment

Any supported Clarity release.

Cause

An object containing a custom slice is corrupted

Resolution

Looking at the bg-ca.log file that contains the job failure, we noticed the following errors too:

ERROR 2026-08-11 05:38:10,012 [Event Interest Registration Thread] odf.ObjectController (clarity:myuser:-1:bpm.startup.interestRegistration) () Error occurred trying to materialize object "z_mycustomobject"

com.niku.union.odf.exception.ODFException: Error resolving derived attribute "z_myvirtual_attribute". There is no attribute with code "z_myparent_attribute" defined for object "inv".

at com.niku.odf.object.ODFObjectImpl.resolveDerivedAttributes(ODFObjectImpl.java:862)

 

Note the object name highlighted in yellow above: z_mycustomobject

This is mentioned also by the time slicing job failure snip on this KB introduction: statementSet not found odf-pmd.z_mycustomobject.reset-TSV-status-z_mytsv.map

 

This z_mycustomobjectobject contains a custom Time Scaled Value that the time slicing job can not process due to the object corruption.

The object is corrupted, because there is a virtual attribute (z_myvirtual_attribute) that references an attribute at the Investment object (z_myparent_attribute) and this has been deleted. The z_myvirtual_attributeattribute is actually orphan.

 

Steps to resolve the object corruption.

• Go to the Investment object
• Create an attribute with the deleted attribute ID: z_myparent_attribute
• This in return will create the missing reference to the z_mycustomobjectobject virtual z_myvirtual_attribute field
• Once this is done, decide whether the field is necessary or it has been deprecated, hence the attribute deletion at the Investment object. If it is to be deprecated, delete the virtual field before you delete the Investment object referenced attribute 

Once the above is fixed, re-run the Time Slicing job