Clarity PPM: Time Slicing job fails with generic error


Article ID: 97754


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


The generic "time slicing job has failed" error appears in the bg-ca logs but contains no additional information.


The error can be attributed to the following causes:

A. Expired time slices.

B. Multicast issue

C. Network/Database connection issue



Component: PPMTSL


Find out the reason by setting the Time Slicing component in the CSA as described in article

Based on the error, check if it falls into one or more of the following categories.

A. Expired time slices.

Make sure there are no fiscal time slices with expiration dates in the past.
Run the following query to find out if there any external time slices that have expired and have not rolled over.

select id, request_name, is_synchronous, num_periods, expiration_date, is_dwh_request, request_completed_date
where expiration_date < sysdate

and is_synchronous = 0 

If there are results returned, please open a case to have the update SQL be provided.

For SaaS customers, please refer to internal document PPM-0024

B. Multicast issue

Once the logging levels are set for the blobcrack component, run the job to see if it completes in the bg-ca logs.
If the job completes in the bg-ca logs but fails in the app, the multicast issue will need to be resolved.

Confirm the multicast address is set along with all bind addresses in the CSA.

Stagger restart the services: beacon,app,bg

C. Network/Database connection issue

Please configure the BG-ca log logging levels to produce additional information on why the job fails.

Common error is:

com.niku.union.persistence.DBConnectionException: [CA Clarity][Oracle JDBC Driver]No more data available to read.

Please reach out to the network/DBA team to resolve.