Time Slicing Job deadlock failure in GCP/PG environment

Products

• Clarity PPM SaaS

Issue/Introduction

The Time Slicing job fails with notification:
This scheduled job failed.  Job:Time Slicing Run ID: 8860240 Scheduler ID: [email protected] Failure message: The timeslice job has failed.

The BG logs show example error:

ERROR 2020-11-23 07:25:34,583 [Dispatch Time Slicing : [email protected] (tenant=clarity)] niku.blobcrack (clarity:[email protected]:xxxx_XXXXXXXXXXXXX:Time Slicing) Exception during blobcrack process
com.niku.union.persistence.PersistenceException: 
SQL error code: 0
Error message: ERROR: deadlock detected
  Detail: Process 31747 waits for ShareLock on transaction 605153047; blocked by process 28449.
Process 28449 waits for ShareLock on transaction 605153013; blocked by process 31747.
  Hint: See server log for query details.
  Where: while locking tuple (11,16) in relation "prteam"
Executed:
 UPDATE PRTEAM
                SET prAllocSum = ?, odf_pralloccurve = ?
                WHERE prID = ? 
Derived from statement:
<?xml version="1.0" encoding="UTF-8"?>
<statement batchable="true" sortColumnPath="/data/header/sortInfo/@sortColumn" sortDirectionPath="/data/header/sortInfo/@sortDirection" slicePath="/data/header/pagination/sliceInfo/@slice" sliceSizePath="/data/header/pagination/sliceInfo/@sliceSize" inputSource="map" xmlns="http://schemas.niku.com/2002/pmd">
  <sql dbVendor="all">
    <text>
                UPDATE PRTEAM
                SET prAllocSum = ?, odf_pralloccurve = ?
                WHERE prID = ?
             </text>
    <param name="value" type="double" direction="IN" expressionListDelimiter=","/>
    <param name="curve" type="blob" direction="IN" expressionListDelimiter=","/>
    <param name="objectID" type="long" direction="IN" expressionListDelimiter=","/>
  </sql>
</statement>

Cause

This is caused by a database contention issue and logged as DE58053.

Environment

Release : 15.8.1, 15.9, 15.9.1

Component : CLARITY TIME SLICING

Resolution

Fixed in 15.9.2 and 15.9.1.1

Workaround: The job will recover at its next run.

Additional Information

• See also: Time Slicing job failures - troubleshooting / known causes