Time Slicing job failures - troubleshooting / known causes

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

This article provides some tips to aid in troubleshooting time slicing job failures including links to KBs on known causes/solutions.

Resolution

Table of Contents

• Check bg-ca.logs for blobcrack errors
• Related KBs on time slicing job failing
• Additional troubleshooting help

Check bg-ca.logs for blobcrack errors

• See KB Accessing the app-ca.log or other Clarity Logs for steps on how to access the bg-ca.logs (and other logs for both On Premise and SaaS customers)
• Debugging configuration: If there are no relevant errors related to time slicing found in the logs, for each server's logging configuration, confirm the following components are set accordingly:

Priority	Name (Component)	Appender
WARN	com.niku	STDOUT
FATAL	org.jgroups	STDOUT
ERROR	org.logicalcobwebs.proxool	STDOUT
ERROR	com.niku.blobcrack	STDOUT
ERROR	com.niku.njs	STDOUT

See KB Setting Logging Levels in Clarity for more details on verifying/setting up the above debugging. 

Related KBs on time slicing job failing

• Time Slicing job fails with deadlock error
• Time Slicing Job Fails with ORA-01426 Error 
• Time slicing job fails with ORA-01752 error Post upgrade to Oracle 12 
• Time Slicing Job Fails With Exception: [CA Clarity][Oracle JDBC Driver]Object has been closed
• Time Slicing job fails due to deadlock issue on MSSQL database 
• Time Slicing job fails due to duplicate records being inserted
• 'Slice value is not valid range' in bg logs -
• Time Slicing job fails with generic error 
• Time Slicing job failing with ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

Additional troubleshooting help

If Broadcom support assistance is needed, the below information can aid in troubleshooting:

1. Do other jobs appear to be running okay?  
2. If On Premise, please provide a copy of the bg-ca.logs and bg-system.logs for the time frame the issue occurred. 
3. Is the Administration > Time Slices page up-to-date or behind? (It should all be caught up by the frequency of the scheduled Time Slicing job.
4. If the job is supposed to run every minute, then the "Last Run Date" should be reflecting the closely to that frequency.)
5. Does the job fail consistently or intermittently?