Receiving Deadlock Errors In CMN_ERROR_LOG Table
(Doc ID 2667550.1)
Last updated on DECEMBER 04, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.1.2 and laterInformation in this document applies to any platform.
Symptoms
Deadlock errors are received as shown below in CMN_ERROR_LOG table from ag services like priority, audit log, scheduling check
Error 1:
Argus Safety.COM :- Oracle error 1 occurred.ORA-00060: deadlock detected while waiting for resourceSQL: update case_master set PRIORITY_DATE_ASSESSED = null where PRIORITY_DATE_ASSESSED is not nullPL/SQL Call Stack: SQL673 PKG_CONSOLE_COMMON.P_ERROR_LOG1 __anonymous_block
Similarly a different type of deadlock error as below.
Error 2:
PKG_CONSOLE_SYS_CONFIG.P_AUTO_ARCHIVE :- AUTO ARCHIVING:-60:ORA-00060: deadlock detected while waiting for resource:
PL/SQL Call Stack:
SQL
673 PKG_CONSOLE_COMMON.P_ERROR_LOG
3276 PKG_CONSOLE_SYS_CONFIG.P_AUTO_ARCHIVE
3172 PKG_CONSOLE_SYS_CONFIG.P_AUTO_ARCHIVE_ALL
1 __anonymous_block
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |