The users are stuck and they can not proceed as they may end up waiting indefinitely for the resources form each other.
Ora 00060 deadlock detected while waiting for resource how to#
What is dead lock, when it occurs and how to fix it?ĭead lock occurs when two or more users waiting for the resources locked by each other. These dead locks can occur in different scenarios: They can occur while doing parallel DML operations, while updating/deleting data from same tables from different sessions, while performing transactions on bitmap index tables and so on but the mentioned scenarios are the most common ones.Īt this point I think we would like to explore more about dead locks, so here are the in depth details on dead locks: Your current sessions rolled backed statements needs to be resubmitted for the execution after the required resources are available. The other session can proceed further as usual. ORA-00060 error indicates that a dead lock occurred due to a resource contention with another session and Oracle rolled back your current statement to resolve the dead lock. Why were the two statements waiting for the resource and why was this resource unavailable.ORA-00060: deadlock detected while waiting for resourceĬause: Transactions deadlocked one another while waiting for resources.Īction: Look at the trace file to see the transactions and resources involved. If it is a bug, a sign the filesystem may be having issues, or that the raid controller couldn't handle the load. What I am after is an idea what it might be, someone who had this happen before who could make an informed guess. The stacktrace and memory dump could provide more information however I am not a specialist in troubleshooting those. Current SQL Statement for this session (sql_id=6bvzdgdn8vqqt8).
Pid: 38 O/S info: user: example_user, term: UNKNOWN, ospid: 14589
Information for the OTHER waiting sessions. Resource Name process session holds waits process session holds waits Relevant trace file output: Deadlock graph: This is not a production system by the way. Does it indicate a bug or impeding filesystem failure? I understand running an import and adding datafiles to a tablespace at the same time may be a lot to ask of a server, however this is server has 4 CPUs, 64 GB and a few TB of SAS raid10 at its disposal. I am asking why this happens because it is unusual to me. I can restart the alter tablespace statement and it mostly will go all right the second attempt.
ORA-00060: deadlock detected while waiting for resource I sometimes get the following error when running the above statement: ERROR at line 1:
I am importing a dumpfile and at the same time I am increasing the tablespace using statements such as this: alter tablespace example add datafile '/path/to/oradata/instance/exampleXX.dbf' size 31000m In this case it's an Oracle11 instance (Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit running on Linux to be precise). Though I frequently do this kind of thing for many years now. I have noticed something in Oracle which never happened before to me.
0 kommentar(er)
