Problem when processing process instance due to deadlock issue

Dear Sir,

User is using camunda spring boot 2.0.0 with Camunda v7.6. User is facing below error, could you please help for solution for this issue?

Cause: java.sql.SQLException: ORA-00060: deadlock detected

org.camunda.bpm.engine.ProcessEngineException: ENGINE-03004 Exception while executing Database Operation ‘DELETE MessageEntity[SRF_AJSC:40182c25-1e7a-11e9-859b-0a580af42113]’ with message ’

Error updating database. Cause: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource

The error may involve org.camunda.bpm.engine.impl.persistence.entity.JobEntity.deleteMessage-Inline

The error occurred while setting parameters

SQL: delete from ACT_RU_JOB where ID_ = ? and REV_ = ?

Cause: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource

'. Flush summary:
[
INSERT HistoricJobLogEventEntity[SRF_AJSC:47a63950-1e7a-11e9-859b-0a580af42113]
INSERT HistoricTaskInstanceEventEntity[SRF_AJSC:43e400f1-1e7a-11e9-859b-0a580af42113]
INSERT HistoricActivityInstanceEventEntity[SRF_AJSC:43ca104e-1e7a-11e9-859b-0a580af42113]
INSERT HistoricActivityInstanceEventEntity[Task_18m09d4:SRF_AJSC:43e400f0-1e7a-11e9-859b-0a580af42113]
INSERT TaskEntity[SRF_AJSC:43e400f1-1e7a-11e9-859b-0a580af42113]
DELETE MessageEntity[SRF_AJSC:40182c25-1e7a-11e9-859b-0a580af42113]
UPDATE ExecutionEntity[SRF_AJSC:4013e662-1e7a-11e9-859b-0a580af42113]
]
at org.camunda.bpm.engine.impl.db.EnginePersistenceLogger.flushDbOperationException(EnginePersistenceLogger.java:115)
at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flushDbOperationManager(DbEntityManager.java:305)
at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flush(DbEntityManager.java:281)
at org.camunda.bpm.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:203)
at org.camunda.bpm.engine.impl.interceptor.CommandContext.close(CommandContext.java:132)
at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:113)
at org.camunda.bpm.engine.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:42)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:133)
at org.camunda.bpm.engine.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:40)
at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:66)
at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)
at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobHelper.executeJob(ExecuteJobHelper.java:36)
at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobHelper.executeJob(ExecuteJobHelper.java:29)
at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobsRunnable.executeJob(ExecuteJobsRunnable.java:88)
at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobsRunnable.run(ExecuteJobsRunnable.java:57)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.ibatis.exceptions.PersistenceException:

Set your database isolation level to READ COMMITTED globally.

Thanks Aravindhrs, let me try it.