CA PPM : The Time Slicing job is not completing, is in indefinite processing status

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

The following example error is found in the BG logs:

niku.blobcrack (none:none:none) Bad prAllocSum value.  Object ID =5038995 Object type = 4

 

Environment

Release:
Component: TIME & DATA MANAGAEMENT"

Cause

The error is caused by a corrupt value in the allocation record.

Resolution

To locate the corrupt allocation record, do the following:

1. Use the object id in the error message to run the following query:

    select P.unique_name as project_code , R.UNIQUE_NAME as resource_code
    from srm_projects P , prteam T, srm_resources R
    where P.id = T.PRPROJECTID
    and R.ID = T.PRRESOURCEID
    and T.PRID =  'enter object id from the error message'

    e.g. this is the query for the above error:

    select P.unique_name as project_code , R.UNIQUE_NAME as resource_code
    from srm_projects P , prteam T, srm_resources R
    where P.id = T.PRPROJECTID
    and R.ID = T.PRRESOURCEID
    and T.PRID = 5038995

2. Use the project_code to filter for the Project > Team > Staff > Resource > properties > Allocation

3.  Check the allocation segment/record for any corrupt values.

If there are any special characters that are non-numeric, proceed to update it to a valid percentage.

4. Restart the background (bg) services.

5. Run the Time Slicing job and allow it to complete.