Check the Time Slicing job incompatibility list. For OnPremise customers, the following query can also be run to check the incompatible jobs set:
j.job_code, K.JOB_CODE incompatible
Where I.Job_Definition_Id = J.Id
and I.NON_CONCUR_JOB_DEF_ID = K.id
and J.JOB_CODE in ('Time_Slicing','inv_alloc_job')
order by J.JOB_CODE
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.
Obtain the results of:
select * from PRJ_BLB_SLICEREQUESTS order by id
Set the Time Slicing job from running every minute to every 5 minutes. This will generate the same data without impact.
This theoretically would alleviate the contention considerably as the Time Slicing is not forced to process bulk data change, e.g. a XOG or process that reads/updates data such as allocation.
For MSSQL databases, reach out to the DBA team to see what configuration can be set to view the capture and view the deadlock graphs.
If a custom trigger is used, disable the trigger and check if the issue happens again.
Have the DBA team review the DDL of the custom trigger.