Deadlock detected

Hello

all applying patch workers got faile dand I checked the logs and newspaper said dected deadlock.
So I checked the newspaper alert... and alert a mistake to show who headed one of the trace files...
and I got the following info from the trace file

Release 9.2.0.8.0 - Production jserver
ORACLE_HOME = /bustools/oracle/v01/product/9.2.0.8
Name of the system: AIX
Name of the node: AIXAPP01
Press release: 3
Version: 5
Machine: 00SBFC005A01
Instance name: DPAPPL01
Redo thread mounted by this instance: 1
Oracle process number: 44
The Unix process PID: 1269774, image: oracle@aixapp01 (TNS V1 - V3)

SESSION ID: (103.4753) 2009-06-27 08:15:37.952
DEADLOCK DETECTED (ORA-00060)
The following deadlock is not an ORACLE error. It's a
deadlock due to the error of the user in the design of an application
or deliver incorrect SQL ad hoc. What follows
information can help determine the impasse:
Deadlock graph event:
-Blockers - Waiter (s).
Resource name process session held process session expected holds expected
TX-00020015-00017e5b 44 50 103 X 42 X
TX-00060013-000274aa 42 50 X 44 103 X
session 103: IS 0001-002C-00002EFE session 50: 0001-002 a-00002E67
session 50: FACT a 0001-002 - 00002E67 session 103: have you 0001-002C-00002EFE
Expected number of lines:
Session 50: obj - rowid = 000A2C20 - AACiwgAFbAAAI5zAAZ
(dictionary objn - 666656, file - 347, block - 36467, sub - 25 machine)
Session 103: obj - rowid = 000A2C20 - AACiwgAFbAAAI5yACK
(dictionary objn - 666656, file - 347, block - 36466, machine slot - 138)
Information about OTHER sessions of waiting:
Session 50:
PID = 42 series = 18272 audsid = user 1382965: 69/APPS
Info of the o/s: user: dpaappl01, term: pts/1, ospid: 1478862, machine: aixapp01
program:
Customer Info: 055 AY385 N
Current SQL statement:

so now, how to get the SID and SPID and serail #.

and in the light of the foregoing, I see unix process pid 1269774 and ospid = 1478862...
I'm not clear on this topic so plese I want what sid pid spid and and ospid...

Thank you

Hello

You can refer to the following ML doc to get a complete idea about the issue.

[ORA-60 / locks the more frequent Causes | https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=164661.1]

[What to do with ORA-60 deadlock errors | https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=62365.1]

Thank you
Anchorage :)

Tags: Oracle Applications

Similar Questions

ORA-00060: Deadlock detected while you wait the cursor CLOSE resource
Hello

I am a new Member of this forum. I work with a problem that we have obtained a few weeks ago. It runs in the lot C Pro executable on 10 threads dealing with > 800 data accessed from more than one table. The error, such as reported was a package.function call.

This is the error I encountered:
process_item ~ G *, D * ~-60 ~ ORA-00060: Deadlock detected while you wait resources ~ PACKAGE ERROR = cursor CLOSE C_ * in the R package *. I * 7641

The slider is a simple SELECT without Table or record locking.

My questions are:
* During the occurrence of this error, execution is already in the line of the CLOSE cursor or did the error has occurred between the OPEN and the CLOSE slider? There are several lines of code between the OPENING and CLOSING:
-one who calls to a package.function that simply stores the values of parameter to a variable
-another one that retrieves the cursor. The group that contains the values of the cursor is used only by a single function in the package

* Is it possible for this CLOSE cursor cause a deadlock? What could have caused this?

* From what I know, Oracle treats blocks by abandoning the blocking process, while others continue, but this impasse caused our program to hang. How is that possible? The origin of the impasse might be our Threading program? This is a rare event and has past that twice this year.

Thank you
RAF
RAF Serrano wrote:
I see, so it be that blocking has occurred before the CLOSE cursor or it occurred during CLOSING? The cause could be executable ProC

first cause is NOT ProC

or is it really an error in PL/SQL

first cause is NOT PL/SQL.

cause of ORA-00060 is DML (INSERT, UPDATE, or DELETE)

ORA-00060: Deadlock detected while you wait resource
Hello

I have a trigger to an underlying table. It fires after that insertion of the events in the underlying table. When I try to update some columns in a table underlying even within the trigger, I get the error below.

ORA-00060: Deadlock detected while you wait resource

Can anyone clear or correct me.

Thank you
Ignore the Aurélie. It is just a spammer who is trying to promote some criminal website.

A deadlock occurred if two different sessions lock resources. Each session can wait the other session ends.

I suppose that you set up a trigger and use the 'autonomous transaction' wrongly to a commit. This function creates a new session. Now you have two (or more) session that could create deadlock. Committing inside a trigger from the table is ALWAYS bad (with some exceptions).

Solution: remove the pragma of your relaxation. Then the other problems you get with it.

DEADLOCK DETECTED - DELETE statement - how/why he expects in SHARING mode?
Hello

I wonder if anyone can advise here. The environment is:

Microsoft Windows 2003 Server
Standard Oracle 10.2.0.4 Edition

We had a deadlock detected in our application on a customer site - I enclose the corresponding part of the trace file below. While we think we have found the reason for the deadlock (looks like it is due to a foreign key in cascade), I'm confused as the lock mode that is requested.

Here is the track information:
```
Deadlock graph:
                       ---------Blocker(s)--------  ---------Waiter(s)---------
Resource Name          process session holds waits  process session holds waits
TX-00120012-00003b59        28     475     X             29     481           S
TX-000a0029-0003508b        29     481     X             28     475           X
session 475: DID 0001-001C-000F96B0     session 481: DID 0001-001D-00000079
session 481: DID 0001-001D-00000079     session 475: DID 0001-001C-000F96B0
Rows waited on:
Session 481: no row
Session 475: obj - rowid = 00014625 - AAAUYlAAIAAAAawAAo
  (dictionary objn - 83493, file - 8, block - 1712, slot - 40)
Information on the OTHER waiting sessions:
Session 481:
  pid=29 serial=18261 audsid=202192707 user: 51/info
  O/S info: user: SYSTEM, term: our_term, ospid: 5244:940, machine: our_machine
            program: our_exe.exe
  client info: GUI
  application name: app, hash value=3864155245
  action name: our_action, hash value=3631189430
  Current SQL Statement:
  DELETE FROM TABLE_1 T WHERE T.T_ID = :B1
End of information on OTHER waiting sessions.
Current SQL statement for this session:
UPDATE TABLE_1 T SET T.STATUS_ID = :B2 WHERE T.T_ID = :B1 
```
It seems to me like session * 481 * trying to do a deletion when the block is raised:
```
 DELETE FROM TABLE_1 T WHERE T.T_ID = :B1
```
and ask which mode (dynamique31) S .
```
                                   ---------Blocker(s)--------  ---------Waiter(s)---------
Resource Name          process session holds waits  process session holds waits
TX-00120012-00003b59        28     475     X             29     481           S
```
(also the 'no line' for lines didn't wait)
```
Session 481: no row
```
I thought it would be in mode (e) X (clusive) (for the line being deleted). Actually Yes, I set up a test of fast and simple locking and mode (e) X (is) expected the final delete .

So, am I misinterpreted the tracing information, or is the DELETE statement requesting the lock in mode S (Hare)? If this is the case, I'd appreciate a quick explanation of how/why it's...

Kind regards

ADOS
I think we have almost the same reason to wait in S mode as in [single key application | http://books.google.pl/books?id=14OmJzfCfXMC&dq=oracle+wait+interface+practical+guide&q=unique+key+enforcement].
If two sessions want to insert the same key value, the other must wait, because the outcome depends on a commit / rollback of the first session. In the case of validation, session 2 must generate an error in case of cancellation, it must insert his record.

In the test provided by ADOS, at session 1 there is an insert in session 2 - delete. The result of the delete operation depends, once again, commit or rollback in the first session. In the case of validation, it must remove, and cancellations, there is nothing to remove.

If the insert in session 1 has been replaced by the Update, there is no S lock but 'normal' eXclusive

Bartek

ORA-000060: Deadlock detected. More info in file filename.trc

Friends,

DB: oracle 9iR2

*** 2008-11-12 11:22:11.895
*** SESSION ID:(112.20587) 2008-11-12 11:22:11.884
DEADLOCK DETECTED
Current SQL statement for this session:
UPDATE SCM_MR_ENGR_DTL SET.........................(deleted space consuming)
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or 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
TX-00080007-000148b4        97     112     X             80     104           X
TX-0004000a-00014e7f        80     104     X             97     112           X
session 112: DID 0001-0061-000007BC     session 104: DID 0001-0050-00000733
session 104: DID 0001-0050-00000733     session 112: DID 0001-0061-000007BC
Rows waited on:
Session 104: obj - rowid = 000079E2 - AAAHniAAGAAA7LrAAR
  (dictionary objn - 31202, file - 6, block - 242411, slot - 17)
Session 112: obj - rowid = 000079E0 - AAAHngAAGAAA0lrABc
  (dictionary objn - 31200, file - 6, block - 215403, slot - 92)
Information on the OTHER waiting sessions:
Session 104:
  pid=80 serial=19532 audsid=971660 user: 45/NMS
  O/S info: user: matur, term: ANOP-KMCH-151, ospid: 3668:2272, machine: NMS\ANOP-KMCH-151
            program: 
  Current SQL Statement:
  
UPDATE SCM_MR_HD SET ................ (deleted space consuming)
End of information on OTHER waiting sessions.

is this block will be automatically released?
It will cause any problem?
What should I do?

Hello..

This lock will be automatically released. If you encounter a lot of blocking issues, you can increase the INITRANS of this parameter. We also had a blocking problem on a production database, we found was due to a trigger. So, you can also check the triggers.

You can find some good Articles on Metalink:

1 doc ID: Note: 164661.1

2 doc ID: Note: 115467.1

3 doc ID: Note: 62365.1

HTH
Anand

ORA - 04020:deadlock detected while trying to lock object when running catqm
I am a newbie. Help, please.
I improved my db from 10g to 11g using dbua and found that xmldb didn't settle. so, I install the catqm script xmldbthrough and he finds himself in a bind. My alert log complained abput the impasse. How can I stop the script now?
As far as I KNOW, the process level to level only those components that are installed. It adds no new components. :-)

HTH
Srini

The transaction deadlock

Hello
I used am EMP3 named with structure of the table below:
CREATE TABLE EMP3
(
ACTIVATE THE "EMPNO" NUMBER (4,0) NOT NULL,
'ENAME' VARCHAR2 (10 BYTE),
VARCHAR2 (BYTE 9) "JOB."
"MGR" NUMBER (4,0).
"HIREDATE" DATE,
"SAL" NUMBER (7.2).
NUMBER (7.2) "COMM"
"DEPTNO" NUMBER (2.0).
NUMBER (10.0) 'INCOME_TAX '.
);
insert into emp3 values ('1', 'abc', 'clerks', '7902', 1 October 2010 ", 800,", '20,' ");
Then, I created a trigger on this table, which updates the table EMP3 itself.
create or replace
relaxation CALC_TAX
after insertion or update of the sal on EMP3
for each line
declare
pragma autonomous_transaction;
Start
update set INCOME_TAX = EMP3: new. SAL * 1.20 where EMPNO =: new. EMPNO;
commit;
end;
/
But when I update the table EMP3
Update emp3 set sal = 1000 where empno = '1';
It givesme error:
00060 00000 - 'deadlock detected while you wait for resource'
* Cause: Transactions each other an impasse while you wait resources.
* Action: Look at the trace file to identify operations and resources
in question. Repeat if necessary.
Please advise. It is possible to update the same table does not use PRAGMA_AUTONONOUS in relaxation.
Thank you

2913938 wrote:

If I do my trigger as BEFORE, in this case validation and update should arrive on EMP3 inside the trigger, before the real on EMP3 update...

Before you change the data, you must lock the line.

The two transactions trying to lock the same line.

"Lock" has to do with locks, not with the updates.

Try this code:
```
create or replace trigger CALC_TAX
after insert or update of sal on EMP3
for each row
declare
  pragma autonomous_transaction;
  l_rec emp3%rowtype;
begin
  select * into l_rec from emp3 where EMPNO = :new.EMPNO for update;
  commit;
end;
/
```
Now, do a update: you will get blocked, even if the trigger is not updated anything!

Deadlock Graph-Help needed

I'm trying to post this question several times, that the question is automatically deleted, not sure because his envoy on other forums as well.
I have removed the issue from other groups, in order to avoid duplication of work, which I had posted, and it is the only asset.
Then I would ask to the administrator of the group do not delete this question without answering.
Now causes a blocking issue.
I have a few questions about the same thing:
- How to find who is the resource involved in the deadlock?
  - I already checked with the command SQL - select object_name, data_object_id from dba_objects where data_object_id = 39341
    - I have no line when I run.
- The name of the resource, which can be decrypted?
The inserts are all sorted by the primary key value, but still we end up with blocking. This could be due to the lock on the Unique key constraint
If so, how do you know if it is a lock acquired on Table - DeviceDetails GOLD on the Unique key of the table DeviceDetails constraint?
Under what scenarios would serve mode lock "S"? We do not select it for editing anywhere and in any case, this seems to be the command insert according to the chart below.
DEADLOCK DETECTED (ORA-00060)
[Transaction blocking]
The following deadlock is not an ORACLE error. It's a
deadlock due to the error of the user in the design of an application
or deliver incorrect SQL ad hoc. What follows
information can help determine the impasse:
Deadlock graph event:
-Blockers - Waiter (s).
Resource name process session held process session expected holds expected
TX-0007001f - 5-38-486 X 47 731 S 000131c
TX-00020005-000131f6 47 731 X 38 486 S
session 486: IS 0001-0026-000000E2 session 731: have you 0001-002F - 0000001 B
session 731: MADE 0001-002F - 0000001 B session 486: have you 0001-0026-000000E2
Expected number of lines:
Session 486: obj - rowid = 000099AD - AAAJ4xAAKAAACgrAAA
(dictionary objn - 39341, file - 10, block - 10283, machine slot - 0)
Session 731: obj - rowid = 000099AD - AAAJ4xAAKAAACgrAAA
(dictionary objn - 39341, file - 10, block - 10283, machine slot - 0)
-Information for OTHER waiting sessions-
Session 731:
SID: 731 ser: 1603 audsid: 896907 user: 37/User1
indicators: (0 x 8000045) USR /-flags_idl: (0 x 1) BSY /-/ - /-/ - / -.
Flags2: (0 x 40009) - /-/ INC.
PID: 47 info o/s: user: oracle, duration: UNKNOWN, ospid: 22799
Image: oracle@term7252
Customer details:
Info of the o/s: user: root, term: unknown, ospid: 1234
machine: term7252 program: JDBC Thin Client
application name: JDBC Thin Client, hash value = 2546894660
SQL courses
INSERT in DeviceDetails (INSTANCE_VERSION, term2, lastModifiedAt, term3DiscoveredFrom, hostUserName, profile, userPassword, description, length of life, startTime, endTime, campus, building, floorArea, outdoorArea, configGroup, emailID, disclaimerText, startDate, endDate, weekday, ishostUser, applyUserTo, serviceDomainId, isScheduledUser, userStatus, isNewUserName, validity, isDefaultEditable, userRole, createdBy, converted, term6, rebootterm4, term1Years, term1Months, term1Days, term1Hours, term1Mins, term1Secs, isPasswordEncr, attributeList, term1StartTime, term1FirstLoginTime, term5EntityId, term5EntityClass, id) values (: 1,: 2: 3: 4: 5: 6). ,: 7: 8,:, 9: 10:11,: 12,: 13:14,: 15,: 16,: 17,: 18,: 19,: 20,: 21,: 22,: 23,: 24,: 25,: 26,: 27.
-End of information for OTHER waiting sessions-
Information for the session:
-Run SQL statement for the current session (sql_id = dnj1vu47agct7).
INSERT in DeviceDetails (INSTANCE_VERSION, term2, lastModifiedAt, term3DiscoveredFrom, hostUserName, profile, userPassword, description, length of life, startTime, endTime, campus, building, floorArea, outdoorArea, configGroup, emailID, disclaimerText, startDate, endDate, weekday, ishostUser, applyUserTo, serviceDomainId, isScheduledUser, userStatus, isNewUserName, validity, isDefaultEditable, userRole, createdBy, converted, term6, rebootterm4, term1Years, term1Months, term1Days, term1Hours, term1Mins, term1Secs, isPasswordEncr, attributeList, term1StartTime, term1FirstLoginTime, term5EntityId, term5EntityClass, id) values (: 1,: 2: 3: 4: 5: 6). (,: 7: 8: 9:10,: 11,: 12,: 13:14,: 15,: 16,: 17,: 18,: 19,: 20,: 21,: 22,: 23,: 24,: 25,: 26,: 27,: 28,: 29,: 30,: 31,: 32,: 33,: 34,: 35,: 36: 37,: 38,: 39,: 40,: 41,: 42,: 43,: 44,: 45,: 46,: 47)
===================================================

Choose the two most relevant bits:

The Session sampled session 486 history series the 6421

sampling interval: 1 s, max 120 sec history

---------------------------------------------------

[3 samples, 23:03:30 - 23: 03:32]

waited for ' enq: TX - line lock conflict ", seq_num: 41278"

P1: ' name. mode'= 0 x 54580004

Ago 1 sessions blocked by this session.

A boy dumping:

Inst: 1, sid: 731, ser: 1603

wait for the event: "enq: TX - line lock conflict '"

P1: ' name. mode'= 0 x 54580004

The p1 decodes mode TX 4

The wait is "enq: TX - line lock conflict"-it is linked to the single character (or referential integrity)

If we wait ITL, the wait would be "enq: TX - allocate entry ITL.

Concerning

Jonathan Lewis

deadlock occurred but not recorded in the log of alerts

We are using Oracle 11.2.0.3. We have a job every night that injects dynamic package through sql. We get some time after error. I've yet to be able to reproduce the error.
"
DECLARE
*
ERROR on line 1:
ORA-00060: Deadlock detected while you wait resource
"ORA-06512: at line 24"
I checked log alerts to find more information on the impasse but did not find anything.
alert_db1.log | more grep ORA-00060 returns nothings. Please suggest what I can try.

The pieces that you have demonstrated (if they ' are actually the things that underlie your problem and not a miserable coincidence - you done overlaps with timestamps) suggest that you see a problem that should be reported as ORA-04020. (viz: you are blocking on the library cache, not data). This unexpected error number is perhaps a side effect of the problem called SQL dynamic within PL/SQL code. I think you should spend your using Oracle trace file in a SR, who may be able to diagnose all the content as quickly as we could.

You shouldn't be falling and creating packages as part of the production, of course, the ideal strategy is to know why you're doing and working on a better way to achieve the same result. In the short term, however, you can be able to identify what actions may be the cause of this problem. This is a hypothesis that I would seek to based on the information received to date.

(a) are there several different packages that could be dropped / re-created as part of the batch

(b) is it possible for simultaneous sessions do this kind of work

(c) is it possible that a single session could running A package that includes a line to remove the package B, while another session is running package B which includes a line to it left the package A

By the way, you can repeat the search for alert logs and trace files but look for ORA-04020 because this could be something that makes its appearance in the traces, but gets hidden by PL/SQL.

Concerning

Jonathan Lewis

Get blocking detected when waiting for resource query error select...

Hi all
I get an error below each time that the execution of the select query below...
a few times, it will show lock detected while you wait resource and finished...
a few times, it runs and give the result...
but all the time, he writes a journal to alert to the alert
Plesae suggest how to solve the problem...
Thanks in advance
.
Env: Linux / Oracle 11.2.0.3.3
.
.
Alerts log error:
Errors in the /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc file:
ORA-00060: Deadlock detected while you wait resource
ORA-10387: interruption of server a (normal) parallel query
Trace file... information bdrdb_p017_6076.trc:
Trace file /U01/Oracle/Oracle/diag/RDBMS/bdrdb/bdrdb/trace/bdrdb_p017_6076.TRC
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/oracle/oracle/product/11.2.0/dbhome_1
Name of the system: Linux
Name of the node: bdrdb.cteplindia.com
News Release: 2.6.18 - 308.el5PAE
Version: #1 SMP kills Jan 27 17:40:09 EST 2012
Machine: i686
Instance name: bdrdb
Redo thread mounted by this instance: 1
Oracle process number: 92
Unix process pid: 6076, image: [email protected] (P017)
2013-11-04 23:18:57.915
SESSION ID: (423.59970) 2013-11-04 23:18:57.915
CUSTOMER ID :() 23:18:57.915 2013-11-04
SERVICE NAME: (bdrdb) 2013-11-04 23:18:57.915
MODULE NAME :() 23:18:57.915 2013-11-04
ACTION NAME :() 23:18:57.915 2013-11-04
.
.
2013-11-04 23:18:57.915
DEADLOCK DETECTED (ORA-00060)
.
[Transaction blocking]
Deadlock graph event:
-Blockers - Waiter (s).
Resource name process session held process session expected holds expected
PS-00000001-00000011 92 423 S 33 128 S X
BF-2ed08c01-00000000 33 128 S 92 423 S X
session 423: C 005-0001-00081126 session 128: DONE 01/21/67 D 23
session 128: MADE 21/01/67 D session 23 423: have you 0001-005 C-00081126
DEADLOCK DETECTED (ORA-00060)
[Transaction blocking]
Deadlock graph event:
-Blockers - Waiter (s).
Resource name process session held process session expected holds expected
PS-00000001-00000011 92 423 S 33 128 S X
BF-2ed08c01-00000000 33 128 S 92 423 S X
session 423: C 005-0001-00081126 session 128: DONE 01/21/67 D 23
session 128: MADE 21/01/67 D session 23 423: have you 0001-005 C-00081126
Expected number of lines:
Session 423: no line
Session 128: obj - rowid = 00021DC1 - AAAh3BAAVAAAQL/AAA
(dictionary objn - 138689, file - 21, block - 66303, machine slot - 0)
-Information for OTHER waiting sessions-
Session 128:
SID: 128 ser: 46176 audsid: 1836857 user: 102/DBLOCAL
indicators: (0 x 8000041) USR /-flags_idl: (0 x 1) BSY /-/ - /-/ - / -.
Flags2: (0 x 40009) - /-/ INC.
PID: 33 info o/s: user: oracle, duration: UNKNOWN, ospid: 31611
image: [email protected]
Customer details:
Info of the o/s: user: hidden, term: hidden, ospid: 5924:568
machine: hidden program: Toad.exe
application name: TOAD background query session, the hash value = 526966934
SQL courses
application name: TOAD background query session, the hash value = 526966934
SQL courses
SELECT DISTINCT B_FP_TEST. TEST_ID
OF B_FP_TEST.
B_USER_INFO,
J_FP_INVESTIGATOR,
L_TEST_STATUS,
L_ATMS_TEST_TYPE,
j_op_test_anml
WHERE B_FP_TEST. TEST_ID = J_FP_INVESTIGATOR. TEST_ID
AND B_FP_TEST. TEST_TYPE_ID = L_ATMS_TEST_TYPE. ATMS_TEST_TYPE_ID
AND B_USER_INFO. B_USER_INFO_ID = J_FP_INVESTIGATOR. INVESTIGATOR_ID
AND B_FP_TEST. BATCH = L_TEST_STATUS. BATCH
AND B_FP_TEST.IS_DELETED =: "SYS_B_00."
AND B_FP_TEST. TEST_NUM NOT IN (: 'SYS_B_01,': 'SYS_B_02': 'SYS_B_03')
AND L_ATMS_TEST_TYPE.IS_DELETED =: "SYS_B_04."
AND J_FP_INVESTIGATOR.is_pi =: "SYS_B_05."
AND L_TEST_STATUS. STATUS (: 'SYS_B_06': 'SYS_B_07': 'SYS_B_08')
AND j_op_test_anml.test_id = B_FP_TEST. TEST_ID
.
.
-End of information for OTHER waiting sessions-
.
.
2013-11-04 23:18:57.916
dbkedDefDump(): from a dump of diagnosis non-event (flags = 0 x 0, level = 3, mask = 0 x 0)
-Error stack dump-
ORA-00060: Deadlock detected while you wait resource
ORA-10387: interruption of server a (normal) parallel query
-SQL statement (none).
Run SQL information not available - no cursor.
-Call trace stack memory-
call call entered the argument values in hex
location point type (? means dubious value)
More...
.
.
.
.
Query:
SELECT DISTINCT B_FP_TEST. TEST_ID
OF B_FP_TEST.
B_USER_INFO,
J_FP_INVESTIGATOR,
L_TEST_STATUS,
L_ATMS_TEST_TYPE,
j_op_test_anml
WHERE B_FP_TEST. TEST_ID = J_FP_INVESTIGATOR. TEST_ID
AND B_FP_TEST. TEST_TYPE_ID = L_ATMS_TEST_TYPE. ATMS_TEST_TYPE_ID
AND B_USER_INFO. B_USER_INFO_ID = J_FP_INVESTIGATOR. INVESTIGATOR_ID
AND B_FP_TEST. BATCH = L_TEST_STATUS. BATCH
AND B_FP_TEST.IS_DELETED = 0
AND B_FP_TEST. TEST_NUM NOT IN (1, 2, 99)
AND L_ATMS_TEST_TYPE.IS_DELETED = 0
AND J_FP_INVESTIGATOR.is_pi = 1
AND L_TEST_STATUS. STATUS ('regular', 'In progress', 'completed')
AND j_op_test_anml.test_id = B_FP_TEST. TEST_ID
AND ((j_op_test_anml.end_date ENTRE TO_DATE (28 octobre 2013 ") - 1))
AND TO_DATE (4 November 2013 ') + 1).
OR (j_op_test_anml.start_date BETWEEN TO_DATE (28 October 2013 "") - 1).
AND TO_DATE (4 November 2013 ') + 1).
OR (TO_DATE (28 October 2013') BETWEEN j_op_test_anml.start_date)
AND j_op_test_anml.end_date)
OR (TO_DATE (4 November 2013") BETWEEN j_op_test_anml.start_date)
(AND j_op_test_anml.end_date))
AND L_ATMS_TEST_TYPE.IS_DELETED = 0
AND B_FP_TEST. DATASOURCE_ID = 9
.
.
.
Exp query plan:
Hash value of plan: 3398228788
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
| ID | Operation                                          | Name                | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |    TQ | IN-OUT | PQ Distrib.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT |                     | 1501 |   102K | 1929 (1) | 00:00:24 |       |       |        |      |            |
|   1. HASH UNIQUE                                       |                     | 1501 |   102K | 1929 (1) | 00:00:24 |       |       |        |      |            |
|   2.   CONCATENATION.                     |       |       |            |          |       |       |        |      |            |
|   3.    COORDINATOR OF PX |                     |       |       |            |          |       |       |        |      |            |
|   4.     PX SEND QC (RANDOM). : TQ30005 |   241. 16870 |   800 (1) | 00:00:10 |       |       | Q3, 05 | P > S | QC (RAND) |
|* 5 |      HASH JOIN                                     |                     |   241. 16870 |   800 (1) | 00:00:10 |       |       | Q3, 05 | SVCP |            |
|   8 2       PX RECEIVE                                   |                     |   246. 15990.   797 (1) | 00:00:10 |       |       | Q3, 05 | SVCP |            |
|   7.        PX SEND HASH | : TQ30004 |   246. 15990.   797 (1) | 00:00:10 |       |       | Q3, 04 | P > P | HASH |
|* 8 |         HASH JOIN                                  |                     |   246. 15990.   797 (1) | 00:00:10 |       |       | Q3, 04 | SVCP |            |
|   9.          RECEIVE PX |                     |   573. 29223 |   793 (1) | 00:00:10 |       |       | Q3, 04 | SVCP |            |
| 10.           PX SEND HASH | : TQ30003 |   573. 29223 |   793 (1) | 00:00:10 |       |       | Q3, 03 | P > P | HASH |
| * 11 |            HASH JOIN                               |                     |   573. 29223 |   793 (1) | 00:00:10 |       |       | Q3, 03 | SVCP |            |
| 12.             KIND OF BUFFER.                     |       |       |            |          |       |       | Q3, 03 | ISSUE |            |
| 13.              RECEIVE PX |                     |       |       |            |          |       |       | Q3, 03 | SVCP |            |
| 14.               PX SEND BROADCAST | : TQ30000 |       |       |            |          |       |       |        | S > P | BROADCAST |
| 15.                NESTED LOOPS |                     |       |       |            |          |       |       |        |      |            |
| 16.                 NESTED LOOPS |                     |   485. 20855 |   781 (0) | 00:00:10 |       |       |        |      |            |
| 17.                  TABLE ACCESS BY INDEX ROWID | J_OP_TEST_ANML |   485. 10185 |   296 (0) | 00:00:04 | ROWID | ROWID |        |      |            |
| * 18.                   INDEX RANGE SCAN | IDX$ $_2D190001 |   485.       |     4 (0) | 00:00:01 |       |       |        |      |            |
| * 19.                  INDEX UNIQUE SCAN | FT_TEST_ID_PK |     1.       |     0 (0) | 00:00:01 |       |       |        |      |            |
| * 20.                 TABLE ACCESS BY INDEX ROWID | B_FP_TEST |     1.    22.     1 (0) | 00:00:01 | ROWID | ROWID |        |      |            |
| 21.             ITERATOR BLOCK PX |                     | 70382 |   549KO |    11 (0) | 00:00:01 |       |       | Q3, 03 | ISSUE |            |
| * 22.              TABLE ACCESS FULL | J_FP_INVESTIGATOR | 70382 |   549KO |    11 (0) | 00:00:01 |       |       | Q3, 03 | SVCP |            |
| 23.          KIND OF BUFFER.                     |       |       |            |          |       |       | Q3, 04 | ISSUE |            |
| 24.           RECEIVE PX |                     |     3.    42.     3 (0) | 00:00:01 |       |       | Q3, 04 | SVCP |            |
| 25.            PX SEND HASH | : TQ30001 |     3.    42.     3 (0) | 00:00:01 |       |       |        | S > P | HASH |
| * 26.             TABLE ACCESS FULL | L_TEST_STATUS |     3.    42.     3 (0) | 00:00:01 |       |       |        |      |            |
| 27.       KIND OF BUFFER.                     |       |       |            |          |       |       | Q3, 05 | ISSUE |            |
| 28.        PX RECEIVE                                  |                     |    30.   150.     3 (0) | 00:00:01 |       |       | Q3, 05 | SVCP |            |
| 29.         PX SEND HASH | : TQ30002 |    30.   150.     3 (0) | 00:00:01 |       |       |        | S > P | HASH |
| * 30 |          TABLE ACCESS FULL | L_ATMS_TEST_TYPE |    30.   150.     3 (0) | 00:00:01 |       |       |        |      |            |
| 31.    NESTED LOOPS |                     |       |       |            |          |       |       |        |      |            |
| 32.     NESTED LOOPS |                     |     3.   210 |   329 (1) | 00:00:04 |       |       |        |      |            |
| 33.      NESTED LOOPS |                     |     3.   195.   329 (1) | 00:00:04 |       |       |        |      |            |
| * 34 |       HASH JOIN                                    |                     |     2.   114.   325 (1) | 00:00:04 |       |       |        |      |            |
| 35.        NESTED LOOPS |                     |       |       |            |          |       |       |        |      |            |
| 36.         NESTED LOOPS |                     |     6.   258.   322 (1) | 00:00:04 |       |       |        |      |            |
| 37.          RANGE OF SINGLE PARTITION |                     |     6.   126.   316 (1) | 00:00:04 |     7.     7.        |      |            |
| * 38 |           TABLE ACCESS FULL | J_OP_TEST_ANML |     6.   126.   316 (1) | 00:00:04 |     7.     7.        |      |            |
| * 39 |          INDEX UNIQUE SCAN | FT_TEST_ID_PK |     1.       |     0 (0) | 00:00:01 |       |       |        |      |            |
| * 40 |         TABLE ACCESS BY INDEX ROWID | B_FP_TEST |     1.    22.     1 (0) | 00:00:01 | ROWID | ROWID |        |      |            |
| * 41.        TABLE ACCESS FULL | L_TEST_STATUS |     3.    42.     3 (0) | 00:00:01 |       |       |        |      |            |
| * 42 |       TABLE ACCESS BY INDEX ROWID | J_FP_INVESTIGATOR |     1.     8.     2 (0) | 00:00:01 |       |       |        |      |            |
| * 43.        INDEX RANGE SCAN | FI_TEST_ID_PK |     1.       |     1 (0) | 00:00:01 |       |       |        |      |            |
| * 44 |      INDEX UNIQUE SCAN | L_ATMS_TEST_TYPE_PK |     1.       |     0 (0) | 00:00:01 |       |       |        |      |            |
| * 45 |     TABLE ACCESS BY INDEX ROWID | L_ATMS_TEST_TYPE |     1.     5.     1 (0) | 00:00:01 |       |       |        |      |            |
| 46.    COORDINATOR OF PX |                     |       |       |            |          |       |       |        |      |            |
| 47.     PX SEND QC (RANDOM). : TQ20003 |       |       |            |          |       |       | Q2, 03 | P > S | QC (RAND) |
| 48.      NESTED LOOPS |                     |       |       |            |          |       |       | Q2, 03 | SVCP |            |
| 49.       NESTED LOOPS |                     |    33. 2310 |   399 (2) | 00:00:05 |       |       | Q2, 03 | SVCP |            |
| * 50 |        HASH JOIN                                   |                     |    33. 2145.   397 (2) | 00:00:05 |       |       | Q2, 03 | SVCP |            |
| 51.         RECEIVE PX |                     |    78. 3978 |   393 (1) | 00:00:05 |       |       | Q2, 03 | SVCP |            |
| 52.          PX SEND HASH | : TQ20002 |    78. 3978 |   393 (1) | 00:00:05 |       |       | Q2, 02 | P > P | HASH |
| * 53 |           HASH JOIN                                |                     |    78. 3978 |   393 (1) | 00:00:05 |       |       | Q2, 02 | SVCP |            |
| 54.            KIND OF BUFFER.                     |       |       |            |          |       |       | Q2, 02 | ISSUE |            |
| 55.             RECEIVE PX |                     |       |       |            |          |       |       | Q2, 02 | SVCP |            |
| 86 M |              PX SEND BROADCAST | : TQ20000 |       |       |            |          |       |       |        | S > P | BROADCAST |
| 57.               NESTED LOOPS |                     |       |       |            |          |       |       |        |      |            |
| 58.                NESTED LOOPS |                     |    66. 2838 |   382 (1) | 00:00:05 |       |       |        |      |            |
| 59.                 RANGE OF SINGLE PARTITION |                     |    66. 1386 |   316 (1) | 00:00:04 |     7.     7.        |      |            |
| * 60 |                  TABLE ACCESS FULL | J_OP_TEST_ANML |    66. 1386 |   316 (1) | 00:00:04 |     7.     7.        |      |            |
| * 61.                 INDEX UNIQUE SCAN | FT_TEST_ID_PK |     1.       |     0 (0) | 00:00:01 |       |       |        |      |            |
| * 62 |                TABLE ACCESS BY INDEX ROWID | B_FP_TEST |     1.    22.     1 (0) | 00:00:01 | ROWID | ROWID |        |      |            |
| 63.            ITERATOR BLOCK PX |                     | 70382 |   549KO |    11 (0) | 00:00:01 |       |       | Q2, 02 | ISSUE |            |
| * 64 |             TABLE ACCESS FULL | J_FP_INVESTIGATOR | 70382 |   549KO |    11 (0) | 00:00:01 |       |       | Q2, 02 | SVCP |            |
| 65.         KIND OF BUFFER.                     |       |       |            |          |       |       | Q2, 03 | ISSUE |            |
| 66.          RECEIVE PX |                     |     3.    42.     3 (0) | 00:00:01 |       |       | Q2, 03 | SVCP |            |
| 67.           PX SEND HASH | : TQ20001 |     3.    42.     3 (0) | 00:00:01 |       |       |        | S > P | HASH |
| * 68 |            TABLE ACCESS FULL | L_TEST_STATUS |     3.    42.     3 (0) | 00:00:01 |       |       |        |      |            |
| * 69 |        INDEX UNIQUE SCAN | L_ATMS_TEST_TYPE_PK |     1.       |     0 (0) | 00:00:01 |       |       | Q2, 03 | SVCP |            |
| * 70 |       TABLE ACCESS BY INDEX ROWID | L_ATMS_TEST_TYPE |     1.     5.     1 (0) | 00:00:01 |       |       | Q2, 03 | SVCP |            |
| 71.    COORDINATOR OF PX |                     |       |       |            |          |       |       |        |      |            |
| 72.     PX SEND QC (RANDOM). : TQ10003 |       |       |            |          |       |       | Q1, 03 | P > S | QC (RAND) |
| 73.      NESTED LOOPS |                     |       |       |            |          |       |       | Q1, 03 | SVCP |            |
| 74.       NESTED LOOPS |                     |    33. 2310 |   399 (2) | 00:00:05 |       |       | Q1, 03 | SVCP |            |
| * 75 |        HASH JOIN                                   |                     |    34. 2210 |   397 (2) | 00:00:05 |       |       | Q1, 03 | SVCP |            |
| 76.         RECEIVE PX |                     |    78. 3978 |   393 (1) | 00:00:05 |       |       | Q1, 03 | SVCP |            |
| 77.          PX SEND HASH | : TQ10002 |    78. 3978 |   393 (1) | 00:00:05 |       |       | Q1, 02 | P > P | HASH |
| * 78 |           HASH JOIN                                |                     |    78. 3978 |   393 (1) | 00:00:05 |       |       | Q1, 02 | SVCP |            |
| 79.            KIND OF BUFFER.                     |       |       |            |          |       |       | Q1, 02 | ISSUE |            |
| 80.             RECEIVE PX |                     |       |       |            |          |       |       | Q1, 02 | SVCP |            |
| 81.              PX SEND BROADCAST | : TQ10000 |       |       |            |          |       |       |        | S > P | BROADCAST |
| 82.               NESTED LOOPS |                     |       |       |            |          |       |       |        |      |            |
| 83.                NESTED LOOPS |                     |    66. 2838 |   382 (1) | 00:00:05 |       |       |        |      |            |
| 84.                 RANGE OF SINGLE PARTITION |                     |    66. 1386 |   316 (1) | 00:00:04 |     7.     7.        |      |            |
| * 85 |                  TABLE ACCESS FULL | J_OP_TEST_ANML |    66. 1386 |   316 (1) | 00:00:04 |     7.     7.        |      |            |
| * 86 |                 INDEX UNIQUE SCAN | FT_TEST_ID_PK |     1.       |     0 (0) | 00:00:01 |       |       |        |      |            |
| * 87.                TABLE ACCESS BY INDEX ROWID | B_FP_TEST |     1.    22.     1 (0) | 00:00:01 | ROWID | ROWID |        |      |            |
| 88.            ITERATOR BLOCK PX |                     | 70382 |   549KO |    11 (0) | 00:00:01 |       |       | Q1, 02 | ISSUE |            |
| * 89 |             TABLE ACCESS FULL | J_FP_INVESTIGATOR | 70382 |   549KO |    11 (0) | 00:00:01 |       |       | Q1, 02 | SVCP |            |
| 90.         KIND OF BUFFER.                     |       |       |            |          |       |       | Q1, 03 | ISSUE |            |
| 91.          RECEIVE PX |                     |     5:    42.     3 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
| 92.           PX SEND HASH | : TQ10001 |     5:    42.     3 (0) | 00:00:01 |       |       |        | S > P | HASH |
| * 93 |            TABLE ACCESS FULL | L_TEST_STATUS |     5:    42.     3 (0) | 00:00:01 |       |       |        |      |            |
| * 94 |        INDEX UNIQUE SCAN | L_ATMS_TEST_TYPE_PK |     1.       |     0 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
| * 95 |       TABLE ACCESS BY INDEX ROWID | L_ATMS_TEST_TYPE |     1.     3:     1 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Information of predicates (identified by the operation identity card):
---------------------------------------------------
5 - access("B_FP_TEST".") TEST_TYPE_ID "=" L_ATMS_TEST_TYPE. " ("' ATMS_TEST_TYPE_ID")
8 - access("B_FP_TEST".") BATCH "=" L_TEST_STATUS. " ("' BATCH ')
11 - access("B_FP_TEST".") TEST_ID "=" J_FP_INVESTIGATOR. " ("' TEST_ID")
18 - access("J_OP_TEST_ANML".") Start_date"> = TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND"J_OP_TEST_ANML. " "" Start_date "< = TO_DATE (' 2013-11-05)
00:00:00 ', "syyyy-mm-dd hh24:mi:ss"))
19 - access("J_OP_TEST_ANML".") TEST_ID "=" B_FP_TEST. " ("' TEST_ID")
20 - filter("B_FP_TEST".") DATASOURCE_ID '= 9 AND 'B_FP_TEST'." ' IS_DELETED '= 0 AND 'B_FP_TEST'.' <>TEST_NUM ' 1 AND 'B_FP_TEST '. "" TEST_NUM "<>2 AND
'B_FP_TEST '. ("' TEST_NUM" <>99)
22 - filter("J_FP_INVESTIGATOR".") IS_PI "= 1)
26 - filter("L_TEST_STATUS".") STATUS "="Finished"OR"L_TEST_STATUS"". "" STATUS '= 'In progress' OR 'L_TEST_STATUS'." STATUS "="Regular")"
30 - filter("L_ATMS_TEST_TYPE".") IS_DELETED "= 0)
34 - access("B_FP_TEST".") BATCH "=" L_TEST_STATUS. " ("' BATCH ')
38 - filter("J_OP_TEST_ANML".") End_date"> = TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND"J_OP_TEST_ANML. " "' End_date ' < = TO_DATE (' 2013-11-05)
00:00:00 ', "syyyy-mm-dd hh24:mi:ss") AND (LNNVL ("J_OP_TEST_ANML". "Start_date" > = TO_DATE (' 2013-10-27 00:00:00 ',' syyyy-mm-dd hh24:mi:ss')) OR) "
LNNVL ("J_OP_TEST_ANML". "Start_date" < = TO_DATE (' 2013-11-05 00:00:00 ',' syyyy-mm-dd hh24:mi:ss')))) "
39 - access("J_OP_TEST_ANML".") TEST_ID "=" B_FP_TEST. " ("' TEST_ID")
40 - filter("B_FP_TEST".") DATASOURCE_ID '= 9 AND 'B_FP_TEST'." ' IS_DELETED '= 0 AND 'B_FP_TEST'.' <>TEST_NUM ' 1 AND 'B_FP_TEST '. "" TEST_NUM "<>2 AND
'B_FP_TEST '. ("' TEST_NUM" <>99)
41 - filter("L_TEST_STATUS".") STATUS "="Finished"OR"L_TEST_STATUS"". "" STATUS '= 'In progress' OR 'L_TEST_STATUS'." STATUS "="Regular")"
42 - filter("J_FP_INVESTIGATOR".") IS_PI "= 1)
43 - access("B_FP_TEST".") TEST_ID "=" J_FP_INVESTIGATOR. " ("' TEST_ID")
44 - access("B_FP_TEST".") TEST_TYPE_ID "=" L_ATMS_TEST_TYPE. " ("' ATMS_TEST_TYPE_ID")
45 - filter("L_ATMS_TEST_TYPE".") IS_DELETED "= 0)
50 - access("B_FP_TEST".") BATCH "=" L_TEST_STATUS. " ("' BATCH ')
53 - access("B_FP_TEST".") TEST_ID "=" J_FP_INVESTIGATOR. " ("' TEST_ID")
60 - filter("J_OP_TEST_ANML".") End_date"> = TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND"J_OP_TEST_ANML. " "" Start_date "< = TO_DATE (' 2013-11-04)
00:00:00 ', "syyyy-mm-dd hh24:mi:ss") AND (LNNVL ("J_OP_TEST_ANML". "End_date" > = TO_DATE (' 2013-10-27 00:00:00 ',' syyyy-mm-dd hh24:mi:ss')) OR) "
LNNVL ("J_OP_TEST_ANML". "End_date" < = TO_DATE (' 2013-11-05 00:00:00 ',' syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL ("J_OP_TEST_ANML".) " Start_date"> = TO_DATE (' 2013-10-27)
00:00:00 ', "syyyy-mm-dd hh24:mi:ss")) or LNNVL("J_OP_TEST_ANML".") Start_date"< = TO_DATE (' 2013-11-05 00:00:00 ',' syyyy-mm-dd hh24:mi:ss'))))
61 - access("J_OP_TEST_ANML".") TEST_ID "=" B_FP_TEST. " ("' TEST_ID")
62 - filter("B_FP_TEST".") DATASOURCE_ID '= 9 AND 'B_FP_TEST'." ' IS_DELETED '= 0 AND 'B_FP_TEST'.' <>TEST_NUM ' 1 AND 'B_FP_TEST '. "" TEST_NUM "<>2 AND
'B_FP_TEST '. ("' TEST_NUM" <>99)
64 - filter("J_FP_INVESTIGATOR".") IS_PI "= 1)
68 - filter("L_TEST_STATUS".") STATUS "="Finished"OR"L_TEST_STATUS"". "" STATUS '= 'In progress' OR 'L_TEST_STATUS'." STATUS "="Regular")"
69 - access("B_FP_TEST".") TEST_TYPE_ID "=" L_ATMS_TEST_TYPE. " ("' ATMS_TEST_TYPE_ID")
70 - filter("L_ATMS_TEST_TYPE".") IS_DELETED "= 0)
75 - access("B_FP_TEST".") BATCH "=" L_TEST_STATUS. " ("' BATCH ')
78 - access("B_FP_TEST".") TEST_ID "=" J_FP_INVESTIGATOR. " ("' TEST_ID")
85 - filter("J_OP_TEST_ANML".") End_date"> = TO_DATE(' 2013-10-28 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND"J_OP_TEST_ANML. " "" Start_date "< = TO_DATE (' 2013-10-28)
00:00:00 ', "syyyy-mm-dd hh24:mi:ss") AND (LNNVL ("J_OP_TEST_ANML". "End_date" > = TO_DATE (' 2013-11-04 00:00:00 ',' syyyy-mm-dd hh24:mi:ss')) OR) "
LNNVL ("J_OP_TEST_ANML". "Start_date" < = TO_DATE (' 2013-11-04 00:00:00 ',' syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL ("J_OP_TEST_ANML".) " End_date"> = TO_DATE (' 2013-10-27)
00:00:00 ', "syyyy-mm-dd hh24:mi:ss")) or LNNVL("J_OP_TEST_ANML".") End_date"< = TO_DATE (' 2013-11-05 00:00:00 ',' syyyy-mm-dd hh24:mi:ss'))) AND)
(LNNVL ("J_OP_TEST_ANML". "Start_date" > = TO_DATE (' 2013-10-27 00:00:00 ',' syyyy-mm-dd hh24:mi:ss')) or LNNVL ("J_OP_TEST_ANML".) " Start_date"< = TO_DATE (' 2013-11-05)
00:00:00 ', "syyyy-mm-dd hh24:mi:ss")))
86 - access("J_OP_TEST_ANML".") TEST_ID "=" B_FP_TEST. " ("' TEST_ID")
87 - filter("B_FP_TEST".") DATASOURCE_ID '= 9 AND 'B_FP_TEST'." ' IS_DELETED '= 0 AND 'B_FP_TEST'.' <>TEST_NUM ' 1 AND 'B_FP_TEST '. "" TEST_NUM "<>2 AND
'B_FP_TEST '. ("' TEST_NUM" <>99)
89 - filter("J_FP_INVESTIGATOR".") IS_PI "= 1)
93 - filter("L_TEST_STATUS".") STATUS "="Finished"OR"L_TEST_STATUS"". "" STATUS '= 'In progress' OR 'L_TEST_STATUS'." STATUS "="Regular")"
94 - access("B_FP_TEST".") TEST_TYPE_ID "=" L_ATMS_TEST_TYPE. " ("' ATMS_TEST_TYPE_ID")
95 - filter("L_ATMS_TEST_TYPE".") IS_DELETED "= 0)

aanto wrote:

Thanks for the update... but if we perform also using Toad... showing the same error...

Thanks for this update, but it does not change the reality.

If it hurts when you push you in the eyes, the only way to stop the pain should stop poking you in the eye.

Oracle is not related ORA-00060 just to make life more difficult.

ORA-000600 is thrown when a deadlock between two session is detected. PERIOD!

The order in which the DML is run needs to change.

Strange problem deadlock (no foreign key not indexed)

Hello
We are on 11.2.0.2 on Linux. There is a blockage in our database (I first checked that no foreign key is not indexed). This impasse has this type of data in the alert file (after it cuts a lot). Can anyone suggest what might be the cause?

--FROM Alert log: "Global Enqueue Services Deadlock detected. More info in file....trc"
--below from trace file:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /oracle/product/database/1120/db1
System name:     Linux
Node name:     NODE1
Release:     2.6.32.59-0.3-default
Version:     #1 SMP 2012-04-27 11:14:44 +0200
Machine:     x86_64
Instance name: db02
Redo thread mounted by this instance: 0 <none>
Oracle process number: 12
Unix process pid: 17454, image: oracle@db01 (LMD0)


*** 2012-09-16 00:54:00.094
*** SESSION ID:(181.1) 2012-09-16 00:54:00.094
*** CLIENT ID:() 2012-09-16 00:54:00.094
*** SERVICE NAME:() 2012-09-16 00:54:00.094
*** MODULE NAME:() 2012-09-16 00:54:00.094
*** ACTION NAME:() 2012-09-16 00:54:00.094
 
* Load Monitor used for high load check 
* Old Low - High Load Threshold Range = [0 - 0] 
* hlcpu 5 (kjihpc 5), slpct 90, llpct 75 
* New Low - High Load Threshold Range = [30720 - 40960] 

*** 2012-09-16 00:54:02.690
KSXPCINI: kjxgnpub KSXP 2.2.0GESR000 13, 0

*** 2012-09-16 00:54:11.168
ftd (4) received from node 1 (84 5.0/0.0) 
all ftds received 
* kjxhvmaph: domain 0 valid = 1 according to instance 1 
ftd (6) received from node 1 (84 7.0/0.0) 

all ftds received 
ftd (19) received from node 1 (84 20.0/0.0) 
all ftds received 
* Initialize deadlock detection * 
ftd (21) received from node 1 (84 22.0/0.0) 
all ftds received 
ftd (23) received from node 1 (84 22.0/0.0) 
all ftds received 

*** 2012-09-16 00:54:11.460
* kjxpnpgoh: PnP Go Ahead received from 1 (pnp inc 84) 

*** 2012-09-16 00:54:31.988
Begin DRM(399) (swin 1) - AFFINITY transfer pkey 4.1 to 2 oscan 1.1
kjiobjscn 1 
ftd (30) received from node 1 (84 0.31/0.0) 
all ftds received 
ftd (33) received from node 1 (84 0.34/5.0) 
all ftds received 
ftd (35) received from node 1 (84 0.36/6.0) 
all ftds received 
ftd (37) received from node 1 (84 0.38/7.0) 
all ftds received 
2012-09-16 00:54:32.061349 : 

* End DRM for pkey remastering request(s) (locally requested)

*** 2012-09-16 00:55:02.914
2012-09-16 00:55:02.914301 : Setting 3-way CR grants to 1 global-lru off? 0
2012-09-16 03:00:44.727542 : Setting 3-way CR grants to 1 global-lru off? 0

*** 2012-09-16 03:04:25.696
Begin DRM(400) (swin 0) - AFFINITY transfer pkey 74335.0 to 2 oscan 0.0
kjiobjscn 1 
ftd (30) received from node 1 (84 0.30/0.0) 
all ftds received 



* kjxftdn: break from kjxftdn, post lmon later 
ftd (37) received from node 1 (84 0.38/0.0) 
all ftds received 
ftd (30) received from node 1 (84 0.31/0.0) 
all ftds received 
ftd (33) received from node 1 (84 0.34/0.0) 
all ftds received 
ftd (35) received from node 1 (84 0.35/0.0) 
all ftds received 


* kjxftdn: break from kjxftdn, post lmon later 
ftd (37) received from node 1 (84 0.38/0.0) 
all ftds received 
ftd (30) received from node 1 (84 0.30/0.0) 
all ftds received 

(repeated such entry removed)
* End DRM for pkey remastering request(s) (locally requested)

*** 2012-09-17 07:20:51.111
Begin DRM(401) (swin 0) - AFFINITY transfer pkey 88491.0 to 2 oscan 0.0
kjiobjscn 1 
ftd (30) received from node 1 (84 0.31/0.0) 
all ftds received 
ftd (30) received from node 1 (84 0.30/0.0) 
all ftds received 


* kjxftdn: break from kjxftdn, post lmon later 
ftd (33) received from node 1 (84 0.34/0.0) 
all ftds received 
ftd (35) received from node 1 (84 0.36/0.0) 
all ftds received 

* kjxftdn: break from kjxftdn, post lmon later 
2012-09-17 07:20:51.407739 : 

* End DRM for pkey remastering request(s) (locally requested)

*** 2012-09-17 22:04:10.873
Begin DRM(402) (swin 0) - AFFINITY transfer pkey 74331.0 to 2 oscan 0.0
kjiobjscn 1 

*** 2012-09-17 22:04:11.001
ftd (30) received from node 1 (84 0.31/0.0) 
all ftds received 
ftd (33) received from node 1 (84 0.34/0.0) 
ftd (30) received from node 1 (84 0.30/0.0) 
all ftds received 


* kjxftdn: break from kjxftdn, post lmon later 
ftd (35) received from node 1 (84 0.36/0.0) 
all ftds received 
ftd (33) received from node 1 (84 0.33/0.0) 
all ftds received 

* kjxftdn: break from kjxftdn, post lmon later 

*** 2012-09-18 11:07:30.967
ftd (35) received from node 1 (84 0.36/0.0) 
all ftds received 
ftd (37) received from node 1 (84 0.38/0.0) 
all ftds received 
2012-09-18 11:07:30.973676 : 
End DRM(405) for pkey transfer request(s) from 1
ENQUEUE DUMP REQUEST: from 1 spnum 12 on [0xf0008][0x24a0],[TX][ext 0x4,0x0] for reason 3 mtype 0

*** 2012-09-18 17:14:20.114
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0xf0008][0x24a0],[TX][ext 0x4,0x0]
----------resource 0xc2bc3f50----------------------
resname       : [0xf0008][0x24a0],[TX][ext 0x4,0x0]
hash mask     : x3
Local inst    : 2
dir_inst      : 2
master_inst   : 2
hv idx        : 124
hv last r.inc : 84
current inc   : 84
hv status     : 0
hv master     : 1
open options  : dd 
grant_bits    : KJUSERNL KJUSEREX 
grant mode    : KJUSERNL  KJUSERCR  KJUSERCW  KJUSERPR  KJUSERPW  KJUSEREX
count         : 1         0         0         0         0         1
val_state     : KJUSERVS_NOVALUE
valblk        : 0x00000000000000000000000000000000 .
access_inst   : 2
vbreq_state   : 0
state         : x0
resp          : 0xc2bc3f50
On Scan_q?    : N
Total accesses: 2652
Imm.  accesses: 2516
Granted_locks : 1 
Cvting_locks  : 1 
value_block:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
lp 0xd0f7e510 gl KJUSEREX rp 0xc2bc3f50 [0xf0008][0x24a0],[TX][ext 0x4,0x0]
  master 2 gl owner 0xd5df5688 possible pid 19261 xid 53000-0002-00000286 bast 0 rseq 125 mseq 0 history 0x4977d495
  open opt KJUSERDEADLOCK  
CONVERT_Q: 
lp 0xd0f7e6e0 gl KJUSERNL rl KJUSERPR rp 0xc2bc3f50 [0xf0008][0x24a0],[TX][ext 0x4,0x0]
  master 2 owner 1  bast 1 rseq 207 mseq 0x1 history 0x77d497ad
  convert opt KJUSERGETVALUE  
----------enqueue 0xd0f7e510------------------------
lock version     : 89
Owner inst       : 2
grant_level      : KJUSEREX
req_level        : KJUSEREX
bast_level       : KJUSERNL
notify_func      : (nil)
resp             : 0xc2bc3f50
procp            : 0xdb10cc20
pid              : 17454
proc version     : 0
oprocp           : (nil)
opid             : 17454
group lock owner : 0xd5df5688
possible pid     : 19261
xid              : 53000-0002-00000286
dd_time          : 0.0 secs
dd_count         : 0
timeout          : 0.0 secs
On_timer_q?      : N
On_dd_q?         : N
lock_state       : GRANTED
ast_flag         : 0x0
Open Options     : KJUSERDEADLOCK 
Convert options  : KJUSERNOQUEUE KJUSERNODEADLOCKWAIT 
History          : 0x4977d495
Msg_Seq          : 0x0
res_seq          : 125
valblk           : 0x00000000000000000000000000000000 .
user session for deadlock lock 0xd0f7e510
  sid: 290 ser: 713 audsid: 82787243 user: 64/SCOTT    flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
    flags2: (0x40009) -/-/INC
  pid: 83 O/S info: user: grid, term: UNKNOWN, ospid: 19261
    image: oracle@db1
  client details:
    O/S info: user: wasadmin, term: unknown, ospid: 1234
    machine: cdldvjassvap291 program: JDBC Thin Client
    application name: JDBC Thin Client, hash value=2546894660
  current SQL:
  INSERT INTO tab1 SELECT x from tab2;

DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
  possible owner[83.19261] on resource TX-000F0008-000024A0

*** 2012-09-18 17:14:20.115
Submitting asynchronized dump request [28]. summary=[ges process stack dump (kjdglblkrdm1)].
Global blockers dump start:---------------------------------
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0x150019][0x12b0a],[TX][ext 0x2,0x0]
----------resource 0xdcf6de80----------------------
resname       : [0x150019][0x12b0a],[TX][ext 0x2,0x0]
hash mask     : x3
Local inst    : 2
dir_inst      : 1
master_inst   : 1
hv idx        : 119
hv last r.inc : 82
current inc   : 84
hv status     : 0
hv master     : 0
open options  : dd 
Held mode     : KJUSERNL
Cvt mode      : KJUSERPR
Next Cvt mode : KJUSERNL
msg_seq       : 0x1
res_seq       : 32
grant_bits    : KJUSERNL 
grant mode    : KJUSERNL  KJUSERCR  KJUSERCW  KJUSERPR  KJUSERPW  KJUSEREX
count         : 1         0         0         0         0         0
val_state     : KJUSERVS_NOVALUE
valblk        : 0xd0f5415aff7f00000000000000000000 .AZ
access_inst   : 1
vbreq_state   : 0
state         : x8
resp          : 0xdcf6de80
On Scan_q?    : N
Total accesses: 3472
Imm.  accesses: 1369
Granted_locks : 0 
Cvting_locks  : 1 
value_block:  d0 f5 41 5a ff 7f 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
CONVERT_Q: 
lp 0xdb976808 gl KJUSERNL rl KJUSERPR rp 0xdcf6de80 [0x150019][0x12b0a],[TX][ext 0x2,0x0]
  master 1 gl owner 0xdc688bc0 possible pid 19261 xid 53000-0002-00000286 bast 0 rseq 32 mseq 0 history 0x495149da
  convert opt KJUSERGETVALUE  
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0xf0008][0x24a0],[TX][ext 0x4,0x0]
----------resource 0xc2bc3f50----------------------
resname       : [0xf0008][0x24a0],[TX][ext 0x4,0x0]
hash mask     : x3
Local inst    : 2
dir_inst      : 2
master_inst   : 2
hv idx        : 124
hv last r.inc : 84
current inc   : 84
hv status     : 0
hv master     : 1
open options  : dd 
grant_bits    : KJUSERNL KJUSEREX 
grant mode    : KJUSERNL  KJUSERCR  KJUSERCW  KJUSERPR  KJUSERPW  KJUSEREX
count         : 1         0         0         0         0         1
val_state     : KJUSERVS_NOVALUE
valblk        : 0xd0f5415aff7f00000000000000000000 .AZ
access_inst   : 2
vbreq_state   : 0
state         : x0
resp          : 0xc2bc3f50
On Scan_q?    : N
Total accesses: 2654
Imm.  accesses: 2517
Granted_locks : 1 
Cvting_locks  : 1 
value_block:  d0 f5 41 5a ff 7f 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
lp 0xd0f7e510 gl KJUSEREX rp 0xc2bc3f50 [0xf0008][0x24a0],[TX][ext 0x4,0x0]
  master 2 gl owner 0xd5df5688 possible pid 19261 xid 53000-0002-00000286 bast 0 rseq 125 mseq 0 history 0x4977d495
  open opt KJUSERDEADLOCK  
CONVERT_Q: 
lp 0xd0f7e6e0 gl KJUSERNL rl KJUSERPR rp 0xc2bc3f50 [0xf0008][0x24a0],[TX][ext 0x4,0x0]
  master 2 owner 1  bast 1 rseq 207 mseq 0x1 history 0x77d497ad
  convert opt KJUSERGETVALUE  
----------enqueue 0xd0f7e510------------------------
lock version     : 89
Owner inst       : 2
grant_level      : KJUSEREX
req_level        : KJUSEREX
bast_level       : KJUSERNL
notify_func      : (nil)
resp             : 0xc2bc3f50
procp            : 0xdb10cc20
pid              : 17454
proc version     : 0
oprocp           : (nil)
opid             : 17454
group lock owner : 0xd5df5688
possible pid     : 19261
xid              : 53000-0002-00000286
dd_time          : 0.0 secs
dd_count         : 0
timeout          : 0.0 secs
On_timer_q?      : N
On_dd_q?         : N
lock_state       : GRANTED
ast_flag         : 0x0
Open Options     : KJUSERDEADLOCK 
Convert options  : KJUSERNOQUEUE KJUSERNODEADLOCKWAIT 
History          : 0x4977d495
Msg_Seq          : 0x0
res_seq          : 125
valblk           : 0x00000000000000003100050200000000 .1
user session for deadlock lock 0xd0f7e510
  sid: 290 ser: 713 audsid: 82787243 user: 64/SCOTT
    flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
    flags2: (0x40009) -/-/INC
  pid: 83 O/S info: user: grid, term: UNKNOWN, ospid: 19261
    image: oracle@db1
  client details:
    O/S info: user: wasadmin, term: unknown, ospid: 1234
    machine: cdldvjassvap291 program: JDBC Thin Client
    application name: JDBC Thin Client, hash value=2546894660
  current SQL:
  INSERT INTO tab1 SELECT x from tab2; (made up )
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
  possible owner[83.19261] on resource TX-000F0008-000024A0

*** 2012-09-18 17:14:20.116
Submitting asynchronized dump request [28]. summary=[ges process stack dump (kjdglblkrdm1)].
Global blockers dump end:-----------------------------------
Global Wait-For-Graph(WFG) at ddTS[0.1] :
BLOCKED 0xdb976808 3 wq 2 cvtops x1 TX 0x150019.0x12b0a(ext 0x2,0x0)[53000-0002-00000286] inst 2 
BLOCKER 0xcc55d558 3 wq 1 cvtops x28 TX 0x150019.0x12b0a(ext 0x2,0x0)[4C000-0001-0000014C] inst 1 
BLOCKED 0xdb7dcfc8 3 wq 2 cvtops x1 TX 0xf0008.0x24a0(ext 0x4,0x0)[4C000-0001-0000014C] inst 1 
BLOCKER 0xd0f7e510 3 wq 1 cvtops x28 TX 0xf0008.0x24a0(ext 0x4,0x0)[53000-0002-00000286] inst 2 

*** 2012-09-18 17:14:20.687
* Cancel deadlock victim lockp 0xdb976808 

*** 2012-09-18 17:14:25.028
ENQUEUE DUMP REQUEST: from 1 spnum 12 on [0x1a0006][0x2b6e],[TX][ext 0x4,0x0] for reason 3 mtype 0
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
----------resource 0xde49c768----------------------
resname       : [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
hash mask     : x3
Local inst    : 2
dir_inst      : 2
master_inst   : 2
hv idx        : 72
hv last r.inc : 84
current inc   : 84
hv status     : 0
hv master     : 1
open options  : dd 
grant_bits    : KJUSERNL KJUSEREX 
grant mode    : KJUSERNL  KJUSERCR  KJUSERCW  KJUSERPR  KJUSERPW  KJUSEREX
count         : 1         0         0         0         0         1
val_state     : KJUSERVS_NOVALUE
valblk        : 0x00000000000000000000000000000000 .
access_inst   : 2
vbreq_state   : 0
state         : x0
resp          : 0xde49c768
On Scan_q?    : N
Total accesses: 1823
Imm.  accesses: 1789
Granted_locks : 1 
Cvting_locks  : 1 
value_block:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
lp 0xdb40f4a0 gl KJUSEREX rp 0xde49c768 [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
  master 2 gl owner 0xd7f08fa8 possible pid 19228 xid 46000-0002-000004A4 bast 0 rseq 32 mseq 0 history 0x4977d495
  open opt KJUSERDEADLOCK  
CONVERT_Q: 
lp 0xdb414320 gl KJUSERNL rl KJUSERPR rp 0xde49c768 [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
  master 2 owner 1  bast 1 rseq 190 mseq 0x1 history 0x77d497ad
  convert opt KJUSERGETVALUE  
----------enqueue 0xdb40f4a0------------------------
lock version     : 129
Owner inst       : 2
grant_level      : KJUSEREX
req_level        : KJUSEREX
bast_level       : KJUSERNL
notify_func      : (nil)
resp             : 0xde49c768
procp            : 0xdb10cc20
pid              : 17454
proc version     : 0
oprocp           : (nil)
opid             : 17454
group lock owner : 0xd7f08fa8
possible pid     : 19228
xid              : 46000-0002-000004A4
dd_time          : 0.0 secs
dd_count         : 0
timeout          : 0.0 secs
On_timer_q?      : N
On_dd_q?         : N
lock_state       : GRANTED
ast_flag         : 0x0
Open Options     : KJUSERDEADLOCK 
Convert options  : KJUSERNOQUEUE KJUSERNODEADLOCKWAIT 
History          : 0x4977d495
Msg_Seq          : 0x0
res_seq          : 32
valblk           : 0x00000000000000000000000000000000 .
user session for deadlock lock 0xdb40f4a0
  sid: 94 ser: 2065 audsid: 82787238 user: 64/SCOTT    flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
    flags2: (0x40009) -/-/INC
  pid: 70 O/S info: user: grid, term: UNKNOWN, ospid: 19228
    image: oracle@db1
  client details:
    O/S info: user: wasadmin, term: unknown, ospid: 1234
    machine: cdldvjassvap291 program: JDBC Thin Client
    application name: JDBC Thin Client, hash value=2546894660
  current SQL:
  INSERT INTO tab1 SELECT x from tab2; (made up)
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
  possible owner[70.19228] on resource TX-001A0006-00002B6E

*** 2012-09-18 17:14:25.029
Submitting asynchronized dump request [28]. summary=[ges process stack dump (kjdglblkrdm1)].
Global blockers dump start:---------------------------------
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0x160016][0x9249],[TX][ext 0x2,0x0]
----------resource 0xdb2d6758----------------------
resname       : [0x160016][0x9249],[TX][ext 0x2,0x0]
hash mask     : x3
Local inst    : 2
dir_inst      : 1
master_inst   : 1
hv idx        : 51
hv last r.inc : 82
current inc   : 84
hv status     : 0
hv master     : 0
open options  : dd 
Held mode     : KJUSERNL
Cvt mode      : KJUSERPR
Next Cvt mode : KJUSERNL
msg_seq       : 0x1
res_seq       : 49
grant_bits    : KJUSERNL 
grant mode    : KJUSERNL  KJUSERCR  KJUSERCW  KJUSERPR  KJUSERPW  KJUSEREX
count         : 1         0         0         0         0         0
val_state     : KJUSERVS_NOVALUE
valblk        : 0xd0f5415aff7f00000000000000000000 .AZ
access_inst   : 1
vbreq_state   : 0
state         : x8
resp          : 0xdb2d6758
On Scan_q?    : N
Total accesses: 1620
Imm.  accesses: 1442
Granted_locks : 0 
Cvting_locks  : 1 
value_block:  d0 f5 41 5a ff 7f 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
CONVERT_Q: 
lp 0xdb682d78 gl KJUSERNL rl KJUSERPR rp 0xdb2d6758 [0x160016][0x9249],[TX][ext 0x2,0x0]
  master 1 gl owner 0xdc568020 possible pid 19228 xid 46000-0002-000004A4 bast 0 rseq 49 mseq 0 history 0x495149da
  convert opt KJUSERGETVALUE  
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
----------resource 0xde49c768----------------------
resname       : [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
hash mask     : x3
Local inst    : 2
dir_inst      : 2
master_inst   : 2
hv idx        : 72
hv last r.inc : 84
current inc   : 84
hv status     : 0
hv master     : 1
open options  : dd 
grant_bits    : KJUSERNL KJUSEREX 
grant mode    : KJUSERNL  KJUSERCR  KJUSERCW  KJUSERPR  KJUSERPW  KJUSEREX
count         : 1         0         0         0         0         1
val_state     : KJUSERVS_NOVALUE
valblk        : 0xd0f5415aff7f00000000000000000000 .AZ
access_inst   : 2
vbreq_state   : 0
state         : x0
resp          : 0xde49c768
On Scan_q?    : N
Total accesses: 1825
Imm.  accesses: 1790
Granted_locks : 1 
Cvting_locks  : 1 
value_block:  d0 f5 41 5a ff 7f 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
lp 0xdb40f4a0 gl KJUSEREX rp 0xde49c768 [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
  master 2 gl owner 0xd7f08fa8 possible pid 19228 xid 46000-0002-000004A4 bast 0 rseq 32 mseq 0 history 0x4977d495
  open opt KJUSERDEADLOCK  
CONVERT_Q: 
lp 0xdb414320 gl KJUSERNL rl KJUSERPR rp 0xde49c768 [0x1a0006][0x2b6e],[TX][ext 0x4,0x0]
  master 2 owner 1  bast 1 rseq 190 mseq 0x1 history 0x77d497ad
  convert opt KJUSERGETVALUE  
----------enqueue 0xdb40f4a0------------------------
lock version     : 129
Owner inst       : 2
grant_level      : KJUSEREX
req_level        : KJUSEREX
bast_level       : KJUSERNL
notify_func      : (nil)
resp             : 0xde49c768
procp            : 0xdb10cc20
pid              : 17454
proc version     : 0
oprocp           : (nil)
opid             : 17454
group lock owner : 0xd7f08fa8
possible pid     : 19228
xid              : 46000-0002-000004A4
dd_time          : 0.0 secs
dd_count         : 0
timeout          : 0.0 secs
On_timer_q?      : N
On_dd_q?         : N
lock_state       : GRANTED
ast_flag         : 0x0
Open Options     : KJUSERDEADLOCK 
Convert options  : KJUSERNOQUEUE KJUSERNODEADLOCKWAIT 
History          : 0x4977d495
Msg_Seq          : 0x0
res_seq          : 32
valblk           : 0x00000000000000003100050200000000 .1
user session for deadlock lock 0xdb40f4a0
  sid: 94 ser: 2065 audsid: 82787238 user: 64/SCOTT    flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
    flags2: (0x40009) -/-/INC
  pid: 70 O/S info: user: grid, term: UNKNOWN, ospid: 19228
    image: oracle@db1
  client details:
    O/S info: user: wasadmin, term: unknown, ospid: 1234
    machine: cdldvjassvap291 program: JDBC Thin Client
    application name: JDBC Thin Client, hash value=2546894660
  current SQL:
  INSERT INTO tab1 SELECT x from tab2;(made up)
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
  possible owner[70.19228] on resource TX-001A0006-00002B6E

*** 2012-09-18 17:14:25.030
Submitting asynchronized dump request [28]. summary=[ges process stack dump (kjdglblkrdm1)].
Global blockers dump end:-----------------------------------
Global Wait-For-Graph(WFG) at ddTS[0.2] :
BLOCKED 0xdb682d78 3 wq 2 cvtops x1 TX 0x160016.0x9249(ext 0x2,0x0)[46000-0002-000004A4] inst 2 
BLOCKER 0xcefeaf70 3 wq 1 cvtops x28 TX 0x160016.0x9249(ext 0x2,0x0)[54000-0001-000000A9] inst 1 
BLOCKED 0xdb9b6380 3 wq 2 cvtops x1 TX 0x1a0006.0x2b6e(ext 0x4,0x0)[54000-0001-000000A9] inst 1 
BLOCKER 0xdb40f4a0 3 wq 1 cvtops x28 TX 0x1a0006.0x2b6e(ext 0x4,0x0)[46000-0002-000004A4] inst 2 

*** 2012-09-18 17:14:25.667
* Cancel deadlock victim lockp 0xdb682d78 

*** 2012-09-18 18:09:23.508
Begin DRM(406) (swin 0) - AFFINITY transfer pkey 88431.0 to 2 oscan 0.0
kjiobjscn 1 
ftd (30) received from node 1 (84 0.30/0.0) 
all ftds received 

* kjxftdn: break from kjxftdn, post lmon later 
ftd (33) received from node 1 (84 0.34/0.0) 
all ftds received 
ftd (35) received from node 1 (84 0.36/0.0) 
all ftds received 
ftd (37) received from node 1 (84 0.38/0.0) 
all ftds received 
ftd (30) received from node 1 (84 0.31/0.0) 
all ftds received 
ftd (33) received from node 1 (84 0.34/0.0) 
all ftds received 
ftd (35) received from node 1 (84 0.36/0.0) 
all ftds received 
ftd (37) received from node 1 (84 0.38/0.0) 
all ftds received 
ftd (30) received from node 1 (84 0.30/0.0) 
all ftds received

Published by: orausern on October 10, 2012 05:57

Published by: orausern on October 10, 2012 05:58

Let them show you some code. Do not believe anything they said your question don't tell not only

Blocker withdraws the deadlock trace file (self)

Hello

Recently, I had a problem on a 10.2.0.4 database to single instance where blockages are produced. The following test case reproduced the problem (I create three tables parent, a child table with foreign keys indexed to all parents three tables and a procedure that performs an insert in the child table in a standalone transaction):

create table parent_1(id number primary key);

create table parent_2(id number primary key);

create table parent_3(id number primary key);
 
create table child( id_c number primary key,
                   id_p1 number,
                   id_p2 number,
                   id_p3 number,
                   constraint fk_id_p1 foreign key (id_p1) references parent_1(id),
                   constraint fk_id_p2 foreign key (id_p2) references parent_2(id),
                   constraint fk_id_p3 foreign key (id_p3) references parent_3(id)
                   );
 
create index i_id_p1 on child(id_p1);

create index i_id_p2 on child(id_p2);

create index i_id_p3 on child(id_p3);

create or replace procedure insert_into_child as
pragma autonomous_transaction;
begin
  insert into child(id_c, id_p1, id_p2, id_p3) values(1,1,1,1);
  commit;
end;
/
 
insert into parent_1 values(1);

insert into parent_2 values(1);

commit;

And now the action that causes the deadlock:

SQL> insert into parent_3 values(1);

1 row created.

SQL> exec insert_into_child;
BEGIN insert_into_child; END;

*
ERROR at line 1:
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "SCOTT.INSERT_INTO_CHILD", line 4
ORA-06512: at line 1

My question is: How can I determine which integration into the CHILD table waiting for? He could wait on a combination of these, PARENT_3, PARENT_2, PARENT_1, or even on the CHILD if I tried to insert a primary key that is duplicated in the CHILD. Since we have the full test case, we know that he was waiting on PARENT_3 (or better said, he expected to perform a commit / rollback of the transaction 'parent'), but is it possible to determine that only from the deadlock trace file? I ask that because to identify the problem, I had to perform redo log mining, tracing pl/sql with DBMS_TRACE and manual debugging on a clone of the production database that has been restored to a SNA just before blocking is product. So, I had to do a lot of work to get to the trainer table and if this information is already in the deadlock trace file, it would have saved me a lot of time.

Here is the deadlock trace file. In section "DML LOCK", I assumed that the child table (tab = 227042) holds a 3 way locks (SX), all other tables of three parents have a mode 2 locks (SS), but from this excerpt, I see that parent_3 (tab = 227040) blocks the children insert:

Deadlock graph:
                       ---------Blocker(s)--------  ---------Waiter(s)---------
Resource Name          process session holds waits  process session holds waits
TX-00070029-00749150        23     476     X             23     476           S
session 476: DID 0001-0017-00000003     session 476: DID 0001-0017-00000003
Rows waited on:
Session 476: obj - rowid = 000376E2 - AAA3biAAEAAA4BwAAA
  (dictionary objn - 227042, file - 4, block - 229488, slot - 0)
Information on the OTHER waiting sessions:
End of information on OTHER waiting sessions.
Current SQL statement for this session:
INSERT INTO CHILD(ID_C, ID_P1, ID_P2, ID_P3) VALUES(1,1,1,1)
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
3989eef50         4  procedure SCOTT.INSERT_INTO_CHILD
391f3d870         1  anonymous block
.
.
.
.
        SO: 397691978, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
        DML LOCK: tab=227042 flg=11 chi=0
                  his[0]: mod=3 spn=35288
        (enqueue) TM-000376E2-00000000  DID: 0001-0017-00000003
        lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
        res: 0x398341fe8, mode: SX, lock_flag: 0x0
        own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x398341ff8
        ----------------------------------------
        SO: 397691878, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
        DML LOCK: tab=227040 flg=11 chi=0
                  his[0]: mod=2 spn=35288
        (enqueue) TM-000376E0-00000000  DID: 0001-0017-00000003
        lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
        res: 0x3983386e8, mode: SS, lock_flag: 0x0
        own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x3983386f8
        ----------------------------------------
        SO: 397691778, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
        DML LOCK: tab=227038 flg=11 chi=0
                  his[0]: mod=2 spn=35288
        (enqueue) TM-000376DE-00000000  DID: 0001-0017-00000003
        lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
        res: 0x398340f58, mode: SS, lock_flag: 0x0
        own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x398340f68
        ----------------------------------------
        SO: 397691678, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
        DML LOCK: tab=227036 flg=11 chi=0
                  his[0]: mod=2 spn=35288
        (enqueue) TM-000376DC-00000000  DID: 0001-0017-00000003
        lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
        res: 0x39833f358, mode: SS, lock_flag: 0x0
        own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x39833f368
      ----------------------------------------

Thanks in advance for your comments,
Swear

user633661 wrote:

My question is: How can I determine which integration into the CHILD table waiting for? He could wait on a combination of these, PARENT_3, PARENT_2, PARENT_1, or even on the CHILD if I tried to insert a primary key that is duplicated in the CHILD. Since we have the full test case, we know that he was waiting on PARENT_3 (or better said, he expected to perform a commit / rollback of the transaction 'parent'), but is it possible to determine that only from the deadlock trace file?

There is no way to get the answer from the deadlock trace.

At this stage and with your example, the waiting session waits for a lock of the TX (transaction) - this means that he has no idea (and uninteresting) in the involved actual data, that it is simply waiting for a location of transaction undo segment header table clear.

An easy way to demonstrate, it is as follows:-

create the parent and child tables with the activated FK constraint
Session 1 - set a save point, then insert line into parent but do not commit
Session 2 - insert a load line in the child - the session will pass a waiting for TX lock on the parent transaction
Session 1-restoration to the point of backup

Because restoration is a save point, session 1 always held a TX lock in exclusive mode, even if it will take is more all lock TM (table).
Session 2 will still wait for session 1 to commit or rollback - even if the parent required row does not exist, even in a State that is not validated.

Concerning
Jonathan Lewis
http://jonathanlewis.WordPress.com
Author: core Oracle

Performance problem: deadlocks RAC

Hello

Our team is recently making performance tests in our 11 GR 2 RAC 3 knots Lab under Redhat Linux 5.
During the tests, there are some deadlocks detected in the alert log file;

...
Tue Nov 15 11:22:54 2011
Global Enqueue Services Deadlock detected. More info in file
 /opt/app/oracle/diag/rdbms/db/db1/trace/db1_lmd0_12563.trc.
Global Enqueue Services Deadlock detected. More info in file
 /opt/app/oracle/diag/rdbms/db/db1/trace/db1_lmd0_12563.trc.
Tue Nov 15 11:23:10 2011
Global Enqueue Services Deadlock detected. More info in file
 /opt/app/oracle/diag/rdbms/db/db1/trace/db1_lmd0_12563.trc.
Tue Nov 15 11:23:10 2011
Dumping diagnostic data in directory=[cdmp_20111115113104], requested by (instance=3, osid=13645), summary=[abnormal process termination].
Tue Nov 15 11:23:37 2011
Global Enqueue Services Deadlock detected. More info in file
 /opt/app/oracle/diag/rdbms/db/db1/trace/db1_lmd0_12563.trc.
....

About 50% of queries fail with this error; Looking at the trace file that I have.
/opt/app/Oracle/diag/RDBMS/db/db1/trace/db1_lmd0_12563.TRC

....
user session for deadlock lock 0x3d2438198
  sid: 200 ser: 9277 audsid: 1824543 user: 68/SNEADMIN
    flags: (0x45) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
    flags2: (0x40009) -/-/INC
  pid: 65 O/S info: user: grid, term: UNKNOWN, ospid: 5258
    image: oracle@db01
  client details:
    O/S info: user: cceadmin, term: unknown, ospid: 1234
    machine: ca.gency.com program: JDBC Thin Client
    application name: JDBC Thin Client, hash value=2546894660
  current SQL:
  update CCE_ORDER_ITEM_DETAILS set ORDER_ID=:1 , CLUSTER_ID=:2  where ORDER_LINE_ITEM_ID=:3  and CLUSTER_ID=:4 
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
  possible owner[65.5258] on resource TM-0001DF87-00000000

*** 2011-11-15 05:34:48.194
Submitting asynchronized dump request [28]. summary=[ges process stack dump (kjdglblkrdm1)].
Global blockers dump end:-----------------------------------
Global Wait-For-Graph(WFG) at ddTS[0.5] :
BLOCKED 0x3d2438198 4 wq 2 cvtops x1 TM 0x1df87.0x0(ext 0x0,0x0)[41000-0001-000004A5] inst 1 
BLOCKER 0x3d7846108 4 wq 2 cvtops x1 TM 0x1df87.0x0(ext 0x0,0x0)[38000-0002-00002C68] inst 2 
BLOCKED 0x3d7846108 4 wq 2 cvtops x1 TM 0x1df87.0x0(ext 0x0,0x0)[38000-0002-00002C68] inst 2 
BLOCKER 0x3d75a4fd8 4 wq 2 cvtops x1 TM 0x1df87.0x0(ext 0x0,0x0)[43000-0003-000009C1] inst 3 
BLOCKED 0x3d75a4fd8 4 wq 2 cvtops x1 TM 0x1df87.0x0(ext 0x0,0x0)[43000-0003-000009C1] inst 3 
BLOCKER 0x3d2438198 4 wq 2 cvtops x1 TM 0x1df87.0x0(ext 0x0,0x0)[41000-0001-000004A5] inst 1 

.....

No idea please, I can provide more information if necessary

Thank you

Out of curiosity, can indicate you whether it is a new application that runs on 11 GR 2? i.e. has it previously worked flawlessly on an earlier version?

I don't know if it is the same in one of these deadlock LMD trace files but in a blocking single-instance file, there is a big warning that blocks are the result of poor application design. This is not necessarily 100% true but can often be the case. I alluded to this when I commented above on the fact that you update the cluster_id column in these tables, which is then referenced in relationship of fk - is not a drawing that I am convinced of.

What makes the request? What does the cluster_id?

If there are several mode TM 5 occurrences of blocking on several items, it would seem that you have multiple problems (probably the same missing fk type).

As you can see from the info in the last trace of blocking, the declaration of the session involved is different - CCE_FULFILLMENT_ITEM_PROPS.
Is this the same object as 0001DF1C, id of the object 122652 decimal hex?

Can you confirm the structure of this object of the pk/fks and clues?

Crash all running CM own test

a way to solve this problem?
49 lines to date.
-----------------------------------------------------------------------
-Update of the ongoing processes in FND_CONCURRENT_QUEUES
-Implementation running_processes = 0 and max_processes = 0 for all managers
UPDATE fnd_concurrent_queues
*
ERROR on line 1:
ORA-00060: Deadlock detected while you wait resource
Disconnected from the database to Oracle 10 g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
With partitioning, OLAP and Data Mining options
-bash - $3.2

Basically, this means that your simultaneous requests are running.

concerning

Pravin

Competitor Manager - incompatibility of actual values / target after DB update

Legends of dear,
We are facing a problem with real concurrent managers and target values are not equal. ENV: R12.0.6 DB - 10.2.0.3
-We did a Refresh DB sauvegardΘ PROD to the TEST environment
-When running then after cloning
-Check if it holds then PROD IP or the NAME of the NŒUD tables FND_NODES
-Clear FND_NODES by running exec FND_CONC. SETUP_CLEAN proc connecting APPS Schema
-FND_CONC truncated 2 related tables
-Then ran on first level DB and APPS Tier AC.
Now, we couldn't start the concurrent Manager, even if we start it's mismatch with ACTUAL = 0 and TARGET = 1
Internal newspaper of the Manager
================
Check that your system has sufficient resources to start a concurrent Manager process. Contact your system administration: 18 December 2015 21:00:30
Start STANDARD competitor Manager: 18 December 2015 21:00:30
ORACLE 60 error in insert_fcp
Cause: insert_fcp failed due to the ORA-00060: Deadlock detected while you wait resource
ORA-06512: at the 'APPS '. FND_CP_FNDSM', line 127
ORA-06512: at line 1.
The SQL statement being executed at the time of the error was: begin fnd_cp_fndsm.register_fndsm_fcp(:c,:n,:o,:l,:m,:t); end; and was run from the file & ERRFILE.
Could not initialize the FNDSM_ORATEST_TEST services manager. Check that ORATEST has been registered for the simultaneous treatment.
ERROR of the CLIENT CONC-SM (ROUTINE = afpsmcsm) (SM_NAME = FNDSM_ORATEST_TEST) (ERROR = 126)
Systematic AFPEIM has encountered an error when concurrent Manager STANDARD starting with the oracle/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR library.
Check that your system has sufficient resources to start a concurrent Manager process. Contact your system administration: 18 December 2015 21:00:33
Start STANDARD competitor Manager: 18 December 2015 21:00:33
ORACLE 60 error in insert_fcp
Cause: insert_fcp failed due to the ORA-00060: Deadlock detected while you wait resource
ORA-06512: at the 'APPS '. FND_CP_FNDSM', line 127
ORA-06512: at line 1.
The SQL statement being executed at the time of the error was: begin fnd_cp_fndsm.register_fndsm_fcp(:c,:n,:o,:l,:m,:t); end; and was run from the file & ERRFILE.
Could not initialize the FNDSM_ORATEST_TEST services manager. Check that ORATEST has been registered for the simultaneous treatment.
ERROR of the CLIENT CONC-SM (ROUTINE = afpsmcsm) (SM_NAME = FNDSM_ORATEST_TEST) (ERROR = 126)
Systematic AFPEIM has encountered an error when concurrent Manager STANDARD starting with the oracle/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR library.
Check that your system has sufficient resources to start a concurrent Manager process. Contact your system administration: 18 December 2015 21:00:37
Start STANDARD competitor Manager: 18 December 2015 21:00:37
Any kind of help would be very appreciated.
Thank you
Knockaert

Check the trace file in the database alert log file and if the error matches of (simultaneous treatment - ORA-00060: Deadlock detected - UPDATED FND_CONCURRENT_QUEUES (Doc ID 866298.1)), you must apply the hotfix mentioned in the doc.

Thank you

Hussein

Deadlock detected

Similar Questions

Maybe you are looking for