Time Slicing job Failing with ORA-00060: deadlock error

Document ID : KB000052175
Last Modified Date : 16/07/2018
Show Technical Document Details
Issue:

Time Slicing job Failed with ORA-00060: deadlock detected while waiting for resource error. Excerpt of error found in the bg-ca.logs below:

com.niku.union.persistence.PersistenceDeadlockException:
SQL error code: 60
Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00060: deadlock detected while waiting for resource

Cause:
There are a couple of causes of this failure including:
  1. The Investment Allocation job running at the same time as the Time Slicing job (CLRT-52245). These two jobs access many of the same tables and create a large amount of db processing
  2. Large amount of XOG Activity while the time slicing job is running
Resolution:

Solution 1: Make sure the Investment Allocation job and Time Slicing job are incompatible. 

  1. In PPM, go to Administration->Reports and Jobs 
  2. Click on the Time Slicing job and click Add 
  3. Select Investment Allocation and click Add 
Note: it is not necessary to add the incompatibility to the Investment Allocation job. This is done automatically for you when you add the incompatibility to the Time Slicing job.

The cause of this issue: CLRT-52245 was reviewed and it was determined the issue would not be fixed, reference the above Workaround.

Solution 2: As referenced in KB000027257, pause the Time Slicing job while doing a large amount of XOG activity 

Note: The failure is not critical, as the job will recover and process the records the next time it runs.