SQL> ALTER INDEX paymt_pk REBUILD INITRANS 8 To increase the initrans value for the indexes, the user rebuilds the index and specifies the new value. To resolve the deadlocking error, the user must re-create the payments table indexes or table and increase the value for the number of initial transaction slots in the objects block's header.įor review Oracle Metalink document 62354.1 "TX Transaction locks - Example wait scenarios" under the section, "Waits due to Insufficient 'ITL' slots in a Block".
The blocking condition being encountered is likely to be on either the payments table or on one of its two indexes: paymt_pk or ptmytidx2. Can read from Ī trace file is generated for the offending session in diag destination. In a database, a deadlock is a situation in which two or more transactions are waiting for one another to give up locks. Why were the two statements waiting for the resource and why was this resource unavailable.ORA-00060: deadlock detected while waiting for resource
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. Posted by previoustoolboxuser on Jun 22nd, 2010 at 12:21 AM. Resource Name process session holds waits process session holds waits Autoinvoice import program failed with error APP-AR-11526: ORA-00060: deadlock detected while waiting for resource. 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. There are a few reasons why your application may. I have noticed something in Oracle which never happened before to me. Oracle deals with deadlocks pretty much immediately by raising an exception (ORA-00060) in one of the sessions.
0 kommentar(er)
