More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_c. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_c. ORA-00060: deadlock detected while waiting for resource error while doing API calls that involve multiple updates to the table LdLegDetlt. 1 Hello, We run stress tests on our platform and after 2 hours, we meet deadlocks on 2 tables. Thread starter Fredo Start date Fredo Member. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_c. ORA-00060: deadlock detected while waiting for resource. The hanganalyze will show if there was another condition that led to the ORA-60.ZBCORP(4):ORA-00060: Deadlock detected.
RSA Support needs that trace file that is listed in the alert_AVDB.log ( it will have a different name on each customer system). More info in file /u01/app/oracle/diag/rdbms/avdb/AVDB/trace/AVDB_ora_c I read about this but I am not able to understand that if the exception is because of competing DMLs then it should have happened in the first query also though with a lower probability but that was non the case. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. But the later one is giving ' ORA-00060: deadlock detected while waiting for resource' exception.
Ora 00060 deadlock detected while waiting for resource update#
When it triggers, you would see something similar to this in the alert log: ITL shortage deadlocks are those dead locks ORA-00060 errors that occur during the execution of UPDATE and DELETE statements where two processes wait for S mode locks on each others TX enqueues. OS Pid: 4527 executed alter system set events 'deadlock trace name hanganalyze level 4' Tail /u01/app/oracle/diag/rdbms/avdb/AVDB/trace/alert_AVDB.log SQL> alter system set events 'deadlock trace name hanganalyze level 4' This setting will disappear when you restart the database. This will only produce a trace file if and when when the ORA-60 happens and does not have any other effect on the database. In order to know if there was some sort of hang situation involved to create the ORA-60, you can enable an event in the database that will produce more information to analyze.
0 kommentar(er)
