Time Slicing job is not completing, Bad prAllocSum value error message in the background (bg) logs

Document ID : KB000051335
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Details:

Time Slicing job is not completing , the following error was in the bg logs:

ERROR 2010-08-25 22:15:15,792 [Dispatch Thread-2329 : bg10@ax0010]
niku.blobcrack (none:none:none) Bad prAllocSum value.  Object ID =5038995 Object type = 4

Steps to Reproduce:

  1. Run the time slicing job
  2. Check the background logs (bg-niku.log) for errors

Expected: No errors

Actual: Following error message:

ERROR 2010-08-25 22:15:15,792 [Dispatch Thread-2329 : bg10@ax0010]
niku.blobcrack (none:none:none) Bad prAllocSum value.  Object ID =5038995 Object type = 4

Solution:

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

To locate the 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 locate the project and the resource_code to locate the resource and allocation record.

  3. Check the allocation record for any corrupt values.

    In this case the allocation percentage field had a non numeric value i.e. '~'

  4. Update the value to a valid one.

  5. Restart the background (bg) services.

  6. Run the Time Slicing job.