The Investment Allocation Job and the Time Slicing Job should be incompatible out of the box.

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

Description:

The investment allocation and time slicing jobs access many of the same tables and create a large amount of db processing. These jobs should not run at the same as it will cause locking and deadlocking behaviors in the system. Out of box, these are allowed to run. This should not be.

Steps to Reproduce:

  1. Run the Investment Allocation job (immediately).

  2. Run the Time Slicing job (immediately).

Expected Results: The Time Slicing job should wait for the Investment Allocation job to finish before running.

Actual Results: The Time Slicing job will run concurrently with the Investment Allocation job.

Note: Deadlocks such as the following may occur from running both of these jobs concurrently.

i.e.

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

Solution:

Status/Resolution:

This issue has been documented as CLRT-52245 and is currently assigned to development for review.

Workaround:

  1. Access the Administration Tool in Clarity.
  2. Choose the reports and jobs link.
  3. Access the Time Slicing job properties.
  4. Choose the incompatible jobs link.
  5. Add Investment Allocation to the set of incompatible jobs.
    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.

STATUS / RESOLUTION:
This issue has been documented as CLRT-52245 and is currently assigned to development for review.

Keywords:CLARITYKB, CLRT-52245, clarity13open.