Running IFS Cloud 24.2, remote deployment, we have in the oracle alert log noticed deadlocks related to time reporting.
There can be handful per day and we have not found a way to reproduce the error and provide a testcase.
From alert log:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "IFSAPP.TIME_PERS_DIARY_CALC_API", line 967
2025-03-19T15:15:30.505585+01:00
ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file …
Extract from related trace file:
...
*** 2025-03-19T15:15:28.435427+01:00
*** SESSION ID:(3084.46836) 2025-03-19T15:15:28.435435+01:00
*** CLIENT ID:(xxx) 2025-03-19T15:15:28.435438+01:00
*** SERVICE NAME:(xxx) 2025-03-19T15:15:28.435440+01:00
*** MODULE NAME:(Time_Card_Employee_Handling_SVC) 2025-03-19T15:15:28.435442+01:00
*** ACTION NAME:(Do_Remove_Time) 2025-03-19T15:15:28.435444+01:00
*** CLIENT DRIVER:(jdbcthin : 19.20.0.0.0) 2025-03-19T15:15:28.435446+01:00
...
Deadlock graph:
------------Blocker(s)----------- ------------Waiter(s)------------
Resource Name process session holds waits serial process session holds waits serial
TX-00110001-00280AD0-00000000-00000000 173 3084 X 46836 173 3084 X 46836
...
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x4e45d4c68 5165 package body IFSAPP.TIME_PERS_DIARY_CALC_API.SET_PERS_ERROR___
0x4e45d4c68 579 package body IFSAPP.TIME_PERS_DIARY_CALC_API.EMP_EXEC
0x4be2a8bb8 1510 package body IFSAPP.TIME_PERS_DIARY_UTIL_API.DO_CALCULATE_ACCOUNT_DATE
0x4ea62d478 977 package body IFSAPP.REPORT_TIME_UTIL_API.REMOVE_INTERVAL
0x4d1e56758 9968 package body IFSAPP.TIME_CARD_EMPLOYEE_HANDLING_SVC.REMOVE_TIME___
0x4d1e56758 6714 package body IFSAPP.TIME_CARD_EMPLOYEE_HANDLING_SVC.DO_REMOVE_TIME
0x2e4c83200 5 anonymous block
…
Anyone facing the same issue?