Ora-00060 Deadlock Detected While Waiting For Resource Error Code 60
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of
Ora-00060 Deadlock Detected While Waiting For Resource Ora-06512
this site About Us Learn more about Stack Overflow the company Business ora 00060 solution Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask ora 00060 deadlock detected more info in file Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up
Oracle Deadlock Resolution
ORA-00060: deadlock detected while waiting for resource up vote 14 down vote favorite 5 I have a series of scripts running in parallel as a nohup on an AIX server hosting oracle 10g. These scripts are written by somebody else and are meant to be executed concurrently. All the scripts are performing updates on a table. I am getting the error, ORA-00060: deadlock
How To Check Deadlock In Oracle
detected while waiting for resource As I googled for this, I found, http://www.dba-oracle.com/t_deadly_perpetual_embrace_locks.htm Even though the scripts are performing updation on the same table concurrently, they are performing updates on different records of the table determined by the WHERE clause with no overlaps of records between them. So would this have caused the error?. Will this error happen regardless of where the updates are performed on a table?. Should I avoid concurrent updates on a table at all times?. Strangely I also found on the nohup.out log, PL/SQL successfully completed after the above quoted error. Does this mean that oracle has recovered from the deadlock and completed the updates successfully or Should I rerun those scripts serially? Any help would be welcome. Thanks in advance. database oracle unix plsql aix share|improve this question edited Dec 15 '14 at 21:20 Lajos Veres 10.8k72446 asked Jun 19 '10 at 8:00 wowrt 242238 add a comment| 3 Answers 3 active oldest votes up vote 7 down vote accepted You can get deadlocks on more than just row locks, e.g. see this. The scripts may be competing for other resources, su
January 15, 2014 - 9:12 pm UTC Category: Database � Version: 11.2 Whilst you are here, check out ora-00060 deadlock detected while waiting for resource in informatica some content from the AskTom team: On Connecting, Pivoting, and
How To Remove Deadlock In Oracle
Learning New Things Latest Followup You Asked *** 2011-09-20 14:29:09.745 DEADLOCK DETECTED ( ORA-00060 ) attempting to break deadlock by signaling ora-00060 [Transaction Deadlock] The following deadlock is not an ORACLE error. It is a deadlock due to user error in the design of an application or http://stackoverflow.com/questions/3074827/ora-00060-deadlock-detected-while-waiting-for-resource from issuing incorrect ad-hoc SQL. The following information may aid in determining the deadlock: Deadlock graph: ---------Blocker(s)-------- ---------Waiter(s)--------- Resource Name process session holds waits process session holds waits TM-0000f4bc-00000000 42 575 SX SSX 48 5 SX SSX TM-0000f4bc-00000000 48 5 SX SSX 42 575 SX SSX session 575: DID 0001-002A-000002F0 session https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:3932525800346405986 5: DID 0001-0030-00000831 session 5: DID 0001-0030-00000831 session 575: DID 0001-002A-000002F0 Rows waited on: Session 575: no row Session 5: obj - rowid = 0000F38C - AAAPOMACrAABodTAAA (dictionary objn - 62348, file - 171, block - 427859, slot - 0) ----- Information for the OTHER waiting sessions ----- Session 5: sid: 5 ser: 13809 audsid: 4295982 user: 63/MI520SAASPERFT1_APP flags: 0x41 pid: 48 O/S info: user: oracle, term: UNKNOWN, ospid: 14422 image: oracle@aedbperf01 client details: O/S info: user: Administrator, term: AEBL009, ospid: 1680:2480 machine: DIUS\AEBL009 program: DrteFrameworkServer.exe application name: DrteFrameworkServer.exe, hash value=3560566261 current SQL: DELETE FROM event WHERE event_id = &0 ========================= Tom, This is my first ever question on this website. I have heard a lot about u. We are getting deadlock when running our benchmark on table EVENT. Table EVENT has 9 FK constraints and no indexes on FK constraints. What should I look to get more information regardi
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog http://www.dba-oracle.com/t_parallel_dml_deadlock_detected.htm
Oracle parallel DML: Deadlock Detected:ORA-00060 Oracle Database Tips by Burleson Consulting Question: I'm having trouble running a parallel DML statement. Here is the code for Parallel DML, I'm running only one session which is current. I don't know how comes I got an error saying DEADLOCK DETECTED: SQL> alter session enable parallel dml; deadlock detected Session altered. SQL> SQL> alter session set db_file_multiblock_read_count=128; Session altered. SQL> set timin on SQL> SQL> SQL> UPDATE /*+ full(myobjects) parallel(myobjects, 8)*/ myobjects 2SET object_name = upper(object_name); update /*+ full(myobjects) parallel(myobjects, 8)*/ * ERROR at line 1: ORA-12801: error signaled in parallel query server P015 ORA-00060: deadlock detected while waiting for resource Answer:It's one of two issues: Deadly embrace - Competing DML tasks cause perpetual deadlock 00060 deadlock detected ITL shortage - More ITL's needed for parallel DML ORA-00060 and Competing Updates Do you have competing updates running? This may be an age-old issue known as the perpetual embrace! The docs note that a retry may work: ORA-00060: deadlock detected while waiting for resource Cause: Transactions deadlocked one another while waiting for resources. Action: Look at the trace file to see the transactions and resources involved. Retry if necessary. If your ORA-00060 is caused by competing resources, the perpetual embrace happens when the aborted task (Task B) attempts to lock a row which is being held by another task (Task A), which, in-turn, is waiting for task B to release a lock. To prevent a perpetual wait, Oracle aborts the transaction that caused the deadlock.ORA-00060 and INITRANS Shortage There can also be a ORA-00060 "deadlock detected" where the table and index INITRANS is set too low. The "Interested Transaction List" and deadlocks caused by an ITL-shortage as described in MOSC note 62354.1. The eBook "Oracle Space Management Handbook" also has notes on the internals of ITL.You can also see ITL waits in a STATSPACK or AWR report, in the segments section