Our CA PPM DataWarehouse Job failed with ORA-04020: deadlock detected while trying to lock object Error

Document ID : KB000111760
Last Modified Date : 21/08/2018
Show Technical Document Details
Issue:
Our CA PPM DataWarehouse Job failed. The error log shows the followings: ORA-04020: deadlock detected while trying to lock object. The job was re-started and it did not fail again. Typically when the deadlock error occurs it is because two different database sessions each attempt to update rows in the same table.
Environment:
CA PPM 15.2, 15.3, 15.4
Jaspersoft 6.4
Resolution:
The following scenarios are potential reasons for deadlock issue:
- Multiple users accessing and updating same tables
- The same job is running or multiple jobs are running concurrently - Check PPM Job Incompatibility List 
- 3rd party tool is accessing the table
For On-Premise customers when deadlocks happens the DBA can check the Oracle deadlock trace (.trc). This may help troubleshoot as it will show DEADLOCK DETECTED.