Clarity PPM

Expand all | Collapse all

Time Slice Issue in 15.2

  • 1.  Time Slice Issue in 15.2

    Posted 06-07-2017 05:39 AM

    Time Slice job is in processing state for a very long time(more then 12 hours now) . I have noticed last run date in Data administration--> Timeslices is now blank for some of the time slices and I have found this error in the bg log and its repating for many object and request id

     

    WARN  2017-06-07 00:27:55,057 [Dispatch Time Slicing-gl 06-07-2017 :  (tenant=clarity)] niku.blobcrack (clarity:lig3:222561901__F47EFE22-BB96-4837-B592-EB275984644F:Time Slicing-gl 06-07-2017) Slice value is not in the valid range.  Object ID = 5975486 Request ID = 3 Date = 2017-03-28T00:00:00 Value = 5.120054752503818E-13. Value will be set to 0

     

    Kindly help

    Regards

    Ritesh



  • 2.  Re: Time Slice Issue in 15.2

    Posted 06-07-2017 05:55 AM

    Hi Ritesh,

     

    Use the technical document to check if at the database it is processing the data or not 

     

    How do I completely check the status of the Time Slicing job? How long will it take my Time Slicing job to complete? 

     

    Timeslice takes longer post an upgrade or when there is roll over, the log you mentioned is not an error and its an warning and can be ignored. With the technical document you can see the count decreasing and its an indication that its progressing

     

    Regards

    Suman Pramanik  



  • 3.  Re: Time Slice Issue in 15.2

    Posted 06-07-2017 06:31 AM

    Hi Suman,

     

    I have run this query to check the whether its processing or not and my result count is not decreasing from past 12 hours.

    Upgrade was done 20 to 30 days back and time slice job ran successfully without any issues after upgrade, now it seems like its stuck for a very long time.

     

    SELECT 'Assignment' Slice_Object,
     Count(*) as records, SLICE_STATUS, max(last_updated_date) as last_updated
     FROM prassignment WHERE SLICE_STATUS in (1,2,3,4)
     GROUP BY SLICE_STATUS

     UNION
     SELECT 'Allocation' Slice_Object,
     Count(*) as records, SLICE_STATUS, max(last_updated_date) as last_updated
     FROM prteam WHERE SLICE_STATUS in (1,2,3,4)
     GROUP BY SLICE_STATUS

     UNION
     SELECT 'Availability' Slice_Object,
     Count(*) as records, SLICE_STATUS, max(last_updated_date) as last_updated
     FROM prj_resources WHERE SLICE_STATUS in (1,2,3,4)
     GROUP BY SLICE_STATUS

     Union
     SELECT 'Timeentries' Slice_Object,
     Count(*) as records, SLICE_STATUS, max(prmodtime) as last_updated
     FROM prtimeentry
     WHERE SLICE_STATUS in(1, 2,3,4)
     GROUP BY SLICE_STATUS

     

    Regards

    Ritesh



  • 4.  Re: Time Slice Issue in 15.2

    Posted 06-07-2017 09:33 AM

    Hi Ritesh,

     

    Can you ask the DBA to check what the timeslice query is doing at the database, is it stuck or there are some database issue. DId you try restarting the BG?

     

    Regards

    Suman Pramanik 



  • 5.  Re: Time Slice Issue in 15.2

    Posted 06-09-2017 03:28 AM

    HI Suman,

     

    We restarted BG and again ran the job but no improvement. We have notice that time slice is taking close to 1.5 hours to process each batch 1000 records and we have around 60k+ records to process.

    Currently DBA is looking into it.

     

    Regards

    Ritesh



  • 6.  Re: Time Slice Issue in 15.2

    Posted 06-09-2017 03:33 AM

    Hi Ritesh,

     

    Please let us know if you find anything at DB layer because the transaction slowness can occur due to multiple reasons at database. 

     

    Regards

    Suman Pramanik 



  • 7.  Re: Time Slice Issue in 15.2

    Posted 06-07-2017 11:50 AM

    We have the same issue and we are asking DBA to see if we can find out where it is stuck.



  • 8.  Re: Time Slice Issue in 15.2

    Posted 06-26-2017 06:14 AM

    Thanks everyone for your response.

     The things gets sorted out after Index rebuild on the data base tables by DBA.



  • 9.  Re: Time Slice Issue in 15.2

    Posted 06-27-2017 01:55 AM

    Great thanks for the update Ritesh

     

    Regards

    Suman Pramanik