The Time Slicing job fails intermittently with a deadlock error in the BG logs. This KB provides guidance on troubleshooting this issue.
Transaction (Process ID) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
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
com.niku.union.persistence.PersistenceDeadlockException:
SQL error code: 0
Error message: ERROR: deadlock detected
Note: The failure is not fatal, as the job will recover and process the records the next time it runs. It's generally recommended to ignore this error
All Databases: MSSQL, Oracle, and Postgres
If you see repeated failures: Contact the DBA with the full message from the bg-ca.log to ask him what was the other process that is getting deadlocked. This is going to help you understand how to deal with the issue going further.
Pause the Waiting/Scheduled Time Slicing job when the XOG is running or make sure they don't run at the same time.
Disable/remove/redesign the customization accordingly