ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Process errors due to Oracle deadlock when Time Slicing job runs at same time
Article ID: 122828
Updated On:
Products
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
A process that has been running fine for a long time encountered an error:Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00060: deadlock detected while waiting for resource.
Cause
The Time Slicing job is attempting to update the same table as a process, which you can observe in the bg-ca.log.
ERROR 2018-12-03 15:48:29,058 [Dispatch Time Slicing : [email protected](tenant=clarity)] niku.blobcrack (clarity:admin:sessionid: Time Slicing) Exception during blobcrack process 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
Resolution
- Check if the time slicing job is running before proceeding with an update within the process.
- If it is running, wait for it to complete (example: 30 seconds) and try again
- If it is not running, you can proceed with process updates.
Feedback
Yes
No
Powered by
