Transaction Deadlock
TRANSACTION (PROCESS ID) WAS DEADLOCKED ON RESOURCES WITH ANOTHER PROCESS AND HAS BEEN CHOSEN AS THE DEADLOCKED VICTIM.RERUN THE TRANSACTION
Hi Vengat,
It's hard for others to analysis this issue only with the limited information, here are some links about troubleshooting the deadlock in SQL Server, please see:
https://www.simple-talk.com/sql/database-administration/handling-deadlocks-in-sql-server/
http://technet.microsoft.com/en-us/library/ms178104(v=sql.105).aspx
https://www.simple-talk.com/sql/learn-sql-server/how-to-track-down-deadlocks-using-sql-server-2005-profiler/
If the issue persists, please post the detail error message when running the script, so that we can make further investigation.
Regards,
Charlie Liao
TechNet Community Support
Similar Messages
-
Hi,
I am trying to execute a transaction in WorkBench and it gives me an Error
"com.sap.xmii.illuminator.logging.LHException:com.microsoft.sqlserver.jdbc.SQLServerException:Transaction (Process ID 62) was deadlocked on lock resources with another process and has been choosen as the deadlock victim. Rerun the transaction"
This error is coming while executing a SQL action inside the transaction. This Sql action will call a stored procedure on External System to write some data.
These are the server Parameter of this data server.
PoolMax: 100
PollSize: 1
There are already 2 open connections to the same database which are also writing some data using the same Stored Procedure.
Thanks,
Gowtham K.That error is from your database. There may be ways to mitigate this, just search for the error on google. If using mssql check
[http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/194f18b0-03b2-4e8f-8c67-5c92373c3efd]
Regards,
Jamie -
I've got a BMP transaction defined through UserTransaction. Within the limits of the transaction, there are CMP Entity calls (CMT) and simple JDBC actions.
When I deploy my app to OC4J, the transaction gets deadlocked. The exact point it happens is when a JDBC action tries to insert a value referencing to another value already inserted (but not committed) by an Entity call within the same transaction.
Surprisingly, when I restart OC4J and my app autodeploys, there is no deadlock performing exactly the same transaction!!
Anybody has an idea about that? Is it an OC4J bug?Maybe this is best understood:
I've got a Bean managed transaction defined in a Session Bean through javax.transaction.UserTransaction. Within the limits of the transaction, there are create CMP Entity calls (CMT) and simple insert JDBC actions.
When I deploy my app to OC4J and run the mentioned transaction, the transaction gets deadlocked. The exact point it happens is when a JDBC action tries to insert a value referencing to another value already inserted (but not committed) by an Entity call within the same transaction.
Which is surprising is that when I restart OC4J and my app autodeploys, there is no deadlock performing exactly the same transaction!!
Can anybody help on this?
PS: Sorry about posting this four times. The forum seemed not to be working properly when this happenned. -
Getting deadlock detected while waiting for resource error for select Query.....
Hi all,
i am getting a below error whenever executing the below select query....
some times it will show dead lock detected while waiting for resource and terminated...
some times it executes and gives result..
but all the time it writes an alert to alert log
Plesae suggest how to resolve the issue..........
Thanks in advance
Env: Linux / Oracle 11.2.0.3.3
Error from alert log:
Errors in file /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc:
ORA-00060: deadlock detected while waiting for resource
ORA-10387: parallel query server interrupt (normal)
Trace file info... 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 the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/oracle/oracle/product/11.2.0/dbhome_1
System name: Linux
Node name: bdrdb.cteplindia.com
Release: 2.6.18-308.el5PAE
Version: #1 SMP Fri 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
*** CLIENT ID:() 2013-11-04 23:18:57.915
*** SERVICE NAME:(bdrdb) 2013-11-04 23:18:57.915
*** MODULE NAME:() 2013-11-04 23:18:57.915
*** ACTION NAME:() 2013-11-04 23:18:57.915
*** 2013-11-04 23:18:57.915
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
PS-00000001-00000011 92 423 S 33 128 S X
BF-2ed08c01-00000000 33 128 S 92 423 S X
session 423: DID 0001-005C-00081126 session 128: DID 0001-0021-00067D23
session 128: DID 0001-0021-00067D23 session 423: DID 0001-005C-00081126
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
PS-00000001-00000011 92 423 S 33 128 S X
BF-2ed08c01-00000000 33 128 S 92 423 S X
session 423: DID 0001-005C-00081126 session 128: DID 0001-0021-00067D23
session 128: DID 0001-0021-00067D23 session 423: DID 0001-005C-00081126
Rows waited on:
Session 423: no row
Session 128: obj - rowid = 00021DC1 - AAAh3BAAVAAAQL/AAA
(dictionary objn - 138689, file - 21, block - 66303, slot - 0)
----- Information for the OTHER waiting sessions -----
Session 128:
sid: 128 ser: 46176 audsid: 1836857 user: 102/DBLOCAL
flags: (0x8000041) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
flags2: (0x40009) -/-/INC
pid: 33 O/S info: user: oracle, term: UNKNOWN, ospid: 31611
image: [email protected]
client details:
O/S info: user: masked, term: masked, ospid: 5924:568
machine: masked program: Toad.exe
application name: TOAD background query session, hash value=526966934
current SQL:
application name: TOAD background query session, hash value=526966934
current SQL:
SELECT DISTINCT B_FP_TEST.TEST_ID
FROM 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.STATUS_ID = L_TEST_STATUS.STATUS_ID
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 IN (:"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 the OTHER waiting sessions -----
*** 2013-11-04 23:18:57.916
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3, mask=0x0)
----- Error Stack Dump -----
ORA-00060: deadlock detected while waiting for resource
ORA-10387: parallel query server interrupt (normal)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
More......
Query:
SELECT DISTINCT B_FP_TEST.TEST_ID
FROM 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.STATUS_ID = L_TEST_STATUS.STATUS_ID
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 IN ('Scheduled', 'In-Progress', 'Completed')
AND j_op_test_anml.test_id = B_FP_TEST.TEST_ID
AND ( (j_op_test_anml.end_date BETWEEN TO_DATE ('28-Oct-2013') - 1
AND TO_DATE ('04-Nov-2013') + 1)
OR (j_op_test_anml.start_date BETWEEN TO_DATE ('28-Oct-2013') - 1
AND TO_DATE ('04-Nov-2013') + 1)
OR (TO_DATE ('28-Oct-2013') BETWEEN j_op_test_anml.start_date
AND j_op_test_anml.end_date)
OR (TO_DATE ('04-Nov-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
Query Exp plan:
Plan hash value: 3398228788
| Id | Operation | Name | Rows | 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 | PX COORDINATOR | | | | | | | | | | |
| 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 | PCWP | |
| 6 | PX RECEIVE | | 246 | 15990 | 797 (1)| 00:00:10 | | | Q3,05 | PCWP | |
| 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 | PCWP | |
| 9 | PX RECEIVE | | 573 | 29223 | 793 (1)| 00:00:10 | | | Q3,04 | PCWP | |
| 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 | PCWP | |
| 12 | BUFFER SORT | | | | | | | | Q3,03 | PCWC | |
| 13 | PX RECEIVE | | | | | | | | Q3,03 | PCWP | |
| 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 GLOBAL 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 GLOBAL INDEX ROWID | B_FP_TEST | 1 | 22 | 1 (0)| 00:00:01 | ROWID | ROWID | | | |
| 21 | PX BLOCK ITERATOR | | 70382 | 549K| 11 (0)| 00:00:01 | | | Q3,03 | PCWC | |
|* 22 | TABLE ACCESS FULL | J_FP_INVESTIGATOR | 70382 | 549K| 11 (0)| 00:00:01 | | | Q3,03 | PCWP | |
| 23 | BUFFER SORT | | | | | | | | Q3,04 | PCWC | |
| 24 | PX RECEIVE | | 3 | 42 | 3 (0)| 00:00:01 | | | Q3,04 | PCWP | |
| 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 | BUFFER SORT | | | | | | | | Q3,05 | PCWC | |
| 28 | PX RECEIVE | | 30 | 150 | 3 (0)| 00:00:01 | | | Q3,05 | PCWP | |
| 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 | PARTITION RANGE SINGLE | | 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 GLOBAL 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 | PX COORDINATOR | | | | | | | | | | |
| 47 | PX SEND QC (RANDOM) | :TQ20003 | | | | | | | Q2,03 | P->S | QC (RAND) |
| 48 | NESTED LOOPS | | | | | | | | Q2,03 | PCWP | |
| 49 | NESTED LOOPS | | 33 | 2310 | 399 (2)| 00:00:05 | | | Q2,03 | PCWP | |
|* 50 | HASH JOIN | | 33 | 2145 | 397 (2)| 00:00:05 | | | Q2,03 | PCWP | |
| 51 | PX RECEIVE | | 78 | 3978 | 393 (1)| 00:00:05 | | | Q2,03 | PCWP | |
| 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 | PCWP | |
| 54 | BUFFER SORT | | | | | | | | Q2,02 | PCWC | |
| 55 | PX RECEIVE | | | | | | | | Q2,02 | PCWP | |
| 56 | PX SEND BROADCAST | :TQ20000 | | | | | | | | S->P | BROADCAST |
| 57 | NESTED LOOPS | | | | | | | | | | |
| 58 | NESTED LOOPS | | 66 | 2838 | 382 (1)| 00:00:05 | | | | | |
| 59 | PARTITION RANGE SINGLE | | 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 GLOBAL INDEX ROWID | B_FP_TEST | 1 | 22 | 1 (0)| 00:00:01 | ROWID | ROWID | | | |
| 63 | PX BLOCK ITERATOR | | 70382 | 549K| 11 (0)| 00:00:01 | | | Q2,02 | PCWC | |
|* 64 | TABLE ACCESS FULL | J_FP_INVESTIGATOR | 70382 | 549K| 11 (0)| 00:00:01 | | | Q2,02 | PCWP | |
| 65 | BUFFER SORT | | | | | | | | Q2,03 | PCWC | |
| 66 | PX RECEIVE | | 3 | 42 | 3 (0)| 00:00:01 | | | Q2,03 | PCWP | |
| 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 | PCWP | |
|* 70 | TABLE ACCESS BY INDEX ROWID | L_ATMS_TEST_TYPE | 1 | 5 | 1 (0)| 00:00:01 | | | Q2,03 | PCWP | |
| 71 | PX COORDINATOR | | | | | | | | | | |
| 72 | PX SEND QC (RANDOM) | :TQ10003 | | | | | | | Q1,03 | P->S | QC (RAND) |
| 73 | NESTED LOOPS | | | | | | | | Q1,03 | PCWP | |
| 74 | NESTED LOOPS | | 33 | 2310 | 399 (2)| 00:00:05 | | | Q1,03 | PCWP | |
|* 75 | HASH JOIN | | 34 | 2210 | 397 (2)| 00:00:05 | | | Q1,03 | PCWP | |
| 76 | PX RECEIVE | | 78 | 3978 | 393 (1)| 00:00:05 | | | Q1,03 | PCWP | |
| 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 | PCWP | |
| 79 | BUFFER SORT | | | | | | | | Q1,02 | PCWC | |
| 80 | PX RECEIVE | | | | | | | | Q1,02 | PCWP | |
| 81 | PX SEND BROADCAST | :TQ10000 | | | | | | | | S->P | BROADCAST |
| 82 | NESTED LOOPS | | | | | | | | | | |
| 83 | NESTED LOOPS | | 66 | 2838 | 382 (1)| 00:00:05 | | | | | |
| 84 | PARTITION RANGE SINGLE | | 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 GLOBAL INDEX ROWID | B_FP_TEST | 1 | 22 | 1 (0)| 00:00:01 | ROWID | ROWID | | | |
| 88 | PX BLOCK ITERATOR | | 70382 | 549K| 11 (0)| 00:00:01 | | | Q1,02 | PCWC | |
|* 89 | TABLE ACCESS FULL | J_FP_INVESTIGATOR | 70382 | 549K| 11 (0)| 00:00:01 | | | Q1,02 | PCWP | |
| 90 | BUFFER SORT | | | | | | | | Q1,03 | PCWC | |
| 91 | PX RECEIVE | | 3 | 42 | 3 (0)| 00:00:01 | | | Q1,03 | PCWP | |
| 92 | PX SEND HASH | :TQ10001 | 3 | 42 | 3 (0)| 00:00:01 | | | | S->P | HASH |
|* 93 | TABLE ACCESS FULL | L_TEST_STATUS | 3 | 42 | 3 (0)| 00:00:01 | | | | | |
|* 94 | INDEX UNIQUE SCAN | L_ATMS_TEST_TYPE_PK | 1 | | 0 (0)| 00:00:01 | | | Q1,03 | PCWP | |
|* 95 | TABLE ACCESS BY INDEX ROWID | L_ATMS_TEST_TYPE | 1 | 5 | 1 (0)| 00:00:01 | | | Q1,03 | PCWP | |
Predicate Information (identified by operation id):
5 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
8 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
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"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
30 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
34 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
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"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
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"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
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"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
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"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
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"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
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)Excellent piece of follow-up on my first suggestion.
I nearly made a comment about how the plan doesn't show Bloom filter pruning either - and then I realised why not. The plan you've shown us comes from Explain Plan with literal values present; the trace file shows bind variables with names that are generated when cursor_sharing is set to force or similar - so the run-time plan and the plan from explain plan are almost guaranteed to be different.
Oracle support will need you to supply the plan you get from trying to run the query and then making a call to dbms_xplan.display_cursor() - dbms_xplan in 10g | Oracle Scratchpad If you do this I think you'll find that the pstart/pstop columns contain entries like :BF0000, and you may even find operations link PX JOIN FILTER CREATE / PX JOIN FILTER USE
A couple of generic notes:
if a query does sufficient work to merit parallel execution, then it's usually better to supply the best possible information to the optimizer, which means using literals rather than bind variables - you could try executing the query with the hint /*+ cursor_sharing_exact */ to stop Oracle from turning your literals into binds; it might be the presence of bind variables that's making the optimizer choose a path that has to include bloom filter pruning in your case.
Where you have the to_date() call you've used a four-digit year - which is a very good thing and helps the optimizer - but it's also a good idea to include an explicit format string as well: with a four-digit year this probably won't make any difference, but it avoids any risk of ambiguity for the optimizer.
I made a comment about the P->S stage and bottlenecks - I spent a couple more minutes looking at the plan, and I see the optimizer has used concatentation: in effect it has run three query blocks one after the other and fed the results to the query co-ordinator - in this case the P->S would make no difference to the end-user response time there's always a final P->S to the coordinator, you just happen to have three of them.
Regards
Jonathan Lewis -
DEADLOCK DETECTED ( ORA-00060 )
Hi,
We are getting deadlocks when the System (Exteranl-Portal-
Production) Cache Upload process runs. It's Looks like
application problem.
We have been getting this deadlock problem whenever the CACHE job gets
executed.
Basically its a portal SRM Business package system.
We have scheduled the CACHE job on portal at 1 AM MSTAZ time , so it
will use Jco to connect R3 and SRM system to bring the data.
We have been observing this deadlock problem only at the time of cache
job.
But cache job is executing succesfully , but we could see the deadlock
in the logs.
In the beginning of trace file (Location:-
/oracle/RPE/saptrace/usertrace/) we found the information as follows
more rpe_ora_1835342.trc
Dump file /oracle/RPE/saptrace/usertrace/rpe_ora_1835342.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
ORACLE_HOME = /oracle/RPE/102_64
System name: AIX
Node name: fsp55a08
Release: 3
Version: 5
Machine: 000788ABD600
Instance name: RPE
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 1835342, image: oracle@fsp55a08
2009-05-31 01:00:49.485
ACTION NAME:() 2009-05-31 01:00:49.485
MODULE NAME:(JDBC Thin Client) 2009-05-31 01:00:49.485
SERVICE NAME:(SYS$USERS) 2009-05-31 01:00:49.485
SESSION ID:(275.1229) 2009-05-31 01:00:49.485
DEADLOCK DETECTED ( 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 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-00050010-00003981 17 275 X 18 284 X
TX-00010000-000038a3 18 284 X 17 275 X
session 275: DID 0001-0011-00000139 session 284: DID 0001-0012-0000004F
session 284: DID 0001-0012-0000004F session 275: DID 0001-0011-00000139
Rows waited on:
Session 284: obj - rowid = 0000561D - AAAFYdAAJAAAHUlAAU
(dictionary objn - 22045, file - 9, block - 29989, slot - 20)
Session 275: obj - rowid = 00005617 - AAAFYXAAJAAAG1aAAc
(dictionary objn - 22039, file - 9, block - 27994, slot - 28)
Information on the OTHER waiting sessions:
Session 284:
pid=18 serial=1236 audsid=672749 user: 21/SAPRPEDB
O/S info: user: rpeadm, term: unknown, ospid: 1234, machine: fsp65003
program: JDBC Thin Client
Please help me on this issue.
Please let me know if you need any more information on the same.
Thank you in advance.
Regards,
A.Naresh
SAP-BASISHi,
Check SAP Note 84348 - Oracle deadlocks, ORA-00060
Thanks
Sunny -
Deadlock detected ora-00060 WWV_FLOW_PREFERENCES$
Hi,
Since the last 3 days, my production database running only APEX applications has been having some lagging issues.
I checked the CPU, Memory etc and everything seems fine except that I get some contention on FLOWS objects.
I checked the alert.log and I can see deadlocks on WWV_FLOW_PREFERENCES$.
I was wondering what could cause this ? :
*** CLIENT ID:(nobody:1682016905757562) 2009-01-16 14:34:46.343
*** SESSION ID:(255.13691) 2009-01-16 14:34:46.342
DEADLOCK DETECTED
[Transaction Deadlock]
Current SQL statement for this session:
DELETE FROM WWV_FLOW_PREFERENCES$ WHERE SECURITY_GROUP_ID = :B2 AND PREFERENCE_NAME LIKE 'FSP%' AND USER_ID = :B1
at the same time I had Row Lock Contention on : UPDATE WWV_FLOW_PREFERENCES$ SET ATTRIBUTE_VALUE = :B5 WHERE USER_ID = NVL(:B4 ,NVL(:B3 ,USER)) AND PREFERENCE_NAME = :B2 AND SECURITY_GROUP_ID = :B1
Any ideas ?
Thanks
Francis.Hi ,
I think I found what was causing locks and deadlocks.
we added rewrites to Apache to access some pages directly. Multiple rewrites were pointing to the exact same page.
For example :
RewriteRule ^/car$ /pls/htmldb/f?p=199:90::RESET:::P90_ID_CAR:99 [R,L]
RewriteRule ^/cars$ /pls/htmldb/f?p=199:90::RESET:::P90_ID_CAR:99 [R,L]
RewriteRule ^/car/$ /pls/htmldb/f?p=199:90::RESET:::P90_ID_CAR:99:2 [R,L]
RewriteRule ^/cars/$ /pls/htmldb/f?p=199:90::RESET:::P90_ID_CAR:99:2 [R,L]
So what happened , is that when a BOT from MSN or Yahoo was scanning our site, it accessed this page with nobody and the same session # at the same time.
I suppose that using same session # and same app_user causes lock problems in wwv_flow since it is the updating and selecting the same records.
So I changed the rewrite rules to use session 0 and removed the RESET in the url (used to reset collections).
I'll see if this will stop the deadlocks.
You can reproduce the locks on wwv_flow if you hit the refresh button on your browser multiple times. You will see in the session monitor that the same session # is used by multiple oracle processes.
maybe there should be a fix to avoid having the same session and same user (nobody) running on separate session simultaneously ?
Francis. -
ORA-00060 DEADLOCK DETECTED - Need Help
Hi Gurus,
I have a question on how to determine the trace log. Where the deadlock happen.
Please help. I have no other hint on how to resolve the error.
*** ACTION NAME:() 2008-08-06 03:34:21.740
*** MODULE NAME:(OEM.SystemPool) 2008-08-06 03:34:21.740
*** SERVICE NAME:(celcomdb) 2008-08-06 03:34:21.740
*** CLIENT ID:() 2008-08-06 03:34:21.740
*** SESSION ID:(113.3188) 2008-08-06 03:34:21.740
DEADLOCK DETECTED ( 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 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-0000c45a-00000000 119 113 X 27 60 SX
TX-0004002c-000269bc 27 60 X 119 113 X
session 113: DID 0001-0077-00000028 session 60: DID 0001-001B-00000278
session 60: DID 0001-001B-00000278 session 113: DID 0001-0077-00000028
Rows waited on:
Session 60: no row
Session 113: obj - rowid = 0000C384 - AAAMOEAADAAAF99AAA
(dictionary objn - 50052, file - 3, block - 24445, slot - 0)
Information on the OTHER waiting sessions:
Session 60:
pid=27 serial=1313 audsid=0 user: 51/SYSMAN
O/S info: user: oracle10, term: UNKNOWN, ospid: 14610456, machine: S63KLJ01
program: oracle@S63KLJ01 (J000)
application name: EM_PING, hash value=2147830874
action name: AGENT_STATUS_MARKER, hash value=2850782869
Current SQL information unavailable
End of information on OTHER waiting sessions.
Current SQL statement for this session:
UPDATE MGMT_OMS_PARAMETERS SET VALUE=TO_CHAR(SYSDATE, 'DD-Mon-YYYY HH24:MI:SS') WHERE HOST_URL=:B1 AND NAME='TIMESTAMP'
----- PL/SQL Call Stack -----
object line object
handle number name
70000006e5ab778 39 package body SYSMAN.MGMT_FAILOVER
70000002e8aaf98 1 anonymous block
===================================================
PROCESS STATE
Process global information:
process: 70000006f4b1598, call: 70000006a9c9320, xact: 70000006dedcf98, curses: 70000006f5a5a50, usrses: 70000006f5a5a50
SO: 70000006f4b1598, type: 2, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=119, calls cur/top: 70000006a9c9320/70000006abfcaf8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 9
last post received-location: ksqrcl
last process to post me: 70000006f484118 141 0
last post sent: 0 0 0
last post sent-location: No post
last process posted by me: none
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 70000006f50bcd0
O/S info: user: oracle10, term: UNKNOWN, ospid: 11538508
OSD pid info: Unix process pid: 11538508, image: oraclecelcomdb@S63KLJ01
Dump of memory from 0x070000006F45FCD0 to 0x070000006F45FED8
70000006F45FCD0 00000004 00000000 07000000 6A9ABD00 [............j...]
70000006F45FCE0 00000010 0003139D 07000000 6ABFCAF8 [............j...]
70000006F45FCF0 00000003 0003139D 07000000 6F8FD600 [............o...]
70000006F45FD00 0000000B 0003139D 07000000 6F5A5A50 [............oZZP]
70000006F45FD10 00000004 00031291 00000000 00000000 [................]
70000006F45FD20 00000000 00000000 00000000 00000000 [................]
Repeat 26 times
70000006F45FED0 00000000 00000000 [........]
SO: 70000006f5a5a50, type: 4, owner: 70000006f4b1598, flag: INIT/-/-/0x00
(session) sid: 113 trans: 70000006dedcf98, creator: 70000006f4b1598, flag: (41) USR/- BSY/-/-/-/-/-
DID: 0001-0077-00000028, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 6, prv: 0, sql: 70000006e5a9140, psql: 70000006e5a9410, user: 51/SYSMAN
O/S info: user: oracle10, term: unknown, ospid: 1234, machine: S63KLJ01
program: OMS
client info: S63KLJ01_Management_Service
application name: OEM.SystemPool, hash value=2960518376
last wait for 'enq: TX - row lock contention' blocking sess=0x70000006f5611e0 seq=322 wait_time=2929700 seconds since wait started=4
name|mode=54580006, usn<<16 | slot=4002c, sequence=269bc
Dumping Session Wait History
for 'enq: TX - row lock contention' count=1 wait_time=2929700
name|mode=54580006, usn<<16 | slot=4002c, sequence=269bc
for 'enq: TM - contention' count=1 wait_time=224489
name|mode=544d0006, object #=c45a, table/partition=0
for 'enq: TM - contention' count=1 wait_time=2929708
name|mode=544d0006, object #=c45a, table/partition=0
for 'SQL*Net message from client' count=1 wait_time=35033
driver id=28444553, #bytes=1, =0
for 'SQL*Net message to client' count=1 wait_time=1
driver id=28444553, #bytes=1, =0
for 'SQL*Net message from client' count=1 wait_time=227
driver id=28444553, #bytes=1, =0
for 'SQL*Net message to client' count=1 wait_time=1
driver id=28444553, #bytes=1, =0
for 'latch: library cache' count=1 wait_time=96826
address=70000006cf2f298, number=d6, tries=0
for 'latch: library cache' count=1 wait_time=36929
address=70000006cf2f0b8, number=d6, tries=0
for 'SQL*Net message from client' count=1 wait_time=131974
driver id=28444553, #bytes=1, =0
temporary object counter: 0
Virtual Thread:
kgskvt: 70000006e82cd98, sess: 70000006f5a5a50, vc: 0, proc: 70000006f4b1598
consumer group cur: OTHER_GROUPS (upd? 0), mapped: DEFAULT_CONSUMER_GROUP, orig:
vt_state: 0x200, vt_flags: 0x30, blkrun: 0
is_assigned: 1, in_sched: 0 (0)
vt_active: 0 (pending: 1)
used quanta: 0 (cg: 0)
cpu start time: 0, quantum status: 0x0
quantum checks to skip: 0, check thresh: 0
idle time: 0, active time: 0 (cg: 0)
cpu yields: 0 (cg: 0), waits: 0 (cg: 0), wait time: 0 (cg: 0)
queued time outs: 0, time: 0 (cur 0, cg 0)
calls aborted: 0, num est exec limit hit: 0
undo current: 0k max: 0k
UOL used : 0 locks(used=2, free=0)
KGX Atomic Operation Log 70000002eb54978
Mutex 0(0, 0) idn 0 oper NONE
Cursor Parent uid 113 efd 15 whr 22 slp 0
oper=NONE pt1=0 pt2=0 pt3=0
pt4=0 u41=0 stt=0
KGX Atomic Operation Log 70000002eb549c0
Mutex 0(0, 0) idn 0 oper NONE
Library Cache uid 113 efd 0 whr 0 slp 0
KGX Atomic Operation Log 70000002eb54a08
Mutex 0(0, 0) idn 0 oper NONE
Library Cache uid 113 efd 0 whr 0 slp 0
SO: 70000006ae53108, type: 53, owner: 70000006f5a5a50, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=70000006ae53108 handle=70000002e8e8150 mode=N
call pin=0 session pin=0 hpc=0000 hlc=0000
htl=70000006ae53188[70000006a753478,70000006abaf090] htb=70000006abaf090 ssga=70000006abae018
user=70000006f5a5a50 session=70000006f5a5a50 count=1 flags=CBK[0020] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=70000002e8e8150 mtx=70000002e8e8280(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=S latch#=4 hpc=0000 hlc=0000
lwt=70000002e8e81f8[70000002e8e81f8,70000002e8e81f8] ltm=70000002e8e8208[70000002e8e8208,70000002e8e8208]
pwt=70000002e8e81c0[70000002e8e81c0,70000002e8e81c0] ptm=70000002e8e81d0[70000002e8e81d0,70000002e8e81d0]
ref=70000002e8e8228[70000004ad30028,70000004ad30028] lnd=70000002e8e8240[70000002e8e8240,70000002e8e8240]
LIBRARY OBJECT: object=70000004ad2f990
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=16
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 70000006eada130 70000004ad2faa8 I/P/A/-/- 0 NONE 00
6 70000004ad2fec8 700000040f57a78 I/P/A/-/E 0 NONE 00
----------------------------------------Oracle handles dead lock by its own. but to resolve the issue u can try following things.
1. take explain for UPDATE MGMT_OMS_PARAMETERS SET VALUE=TO_CHAR(SYSDATE, 'DD-Mon-YYYY HH24:MI:SS') WHERE HOST_URL=:B1 AND NAME='TIMESTAMP';
2. analyze above explain plan and try to tune it.
i think, its because of missing indexes. -
ORA-00060: deadlock detected while waiting for resource with Tbs Read-only
Hi all,
We're using Oracle 10.2.0.1 and 9.2.0.4.
I'm testing the performing of a procedure that inserts, like this:
CREATE OR REPLACE PROCEDURE P$TAD_TEST
IS
TYPE T_T1_C1 IS TABLE OF T1.C1%TYPE INDEX BY PLS_INTEGER;
TYPE T_T1_DT IS TABLE OF T1.DT%TYPE INDEX BY PLS_INTEGER;
P_C1 T_T1_C1;
P_DT T_T1_DT;
P_RESULT NUMBER;
BEGIN
FOR j IN 1..4032 LOOP
P_C1(j) := j;
P_DT(j) := SYSDATE + (j/24/60);
END LOOP;
FORALL i IN P_C1.FIRST..P_C1.LAST SAVE EXCEPTIONS
INSERT INTO T1 VALUES (P_C1(i), P_DT(i));
EXCEPTION
WHEN OTHERS THEN
P_RESULT := SQLCODE;
END;
The table T1 is partitioned across 10 tablespaces. The test consist to take
these tablespace read-only and perform the procedure, and analyze the results,
like erros.
but when I perform the procedure, The alert.log indicates the error
ORA-00060: deadlock detected while waiting for resource.
Why this occurs only the tablespaces are read-only?
thank you!!!!Hi,
yesterday we got this error again(in fact twice) and we were able to get the trace file. It says this is NOT oracle error. i was wrong in suspecting Oracle. This is the trace file details. i dont know how to debug this. Any help appreciated.
*** 2010-06-15 16:24:29.243
*** ACTION NAME:() 2010-06-15 16:24:29.231
*** MODULE NAME:(JDBC Thin Client) 2010-06-15 16:24:29.231
*** SERVICE NAME: 2010-06-15 16:24:29.231
*** SESSION ID:(482.4266) 2010-06-15 16:24:29.231
DEADLOCK DETECTED ( 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 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-00300021-0000b52d 209 482 X 247 474 S
TX-002a0009-00011b24 247 474 X 209 482 S
session 482: DID 0001-00D1-0000000A session 474: DID 0001-00F7-00000008
session 474: DID 0001-00F7-00000008 session 482: DID 0001-00D1-0000000A
Rows waited on:
Session 474: obj - rowid = 0000CED4 - AAAM7UAAxAAAVgSAAA
(dictionary objn - 52948, file - 49, block - 88082, slot - 0)
Session 482: obj - rowid = 0000D8BF - AAANi/AAuAAB+z/AAA
(dictionary objn - 55487, file - 46, block - 519423, slot - 0)
Information on the OTHER waiting sessions:
Session 474:
pid=247 serial=31796 audsid=25502259 user: 62/USER
O/S info: ....
program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
Current SQL Statement:
INSERT QUERY1
End of information on OTHER waiting sessions.
Current SQL statement for this session:
INSERT QUERY2
Thanks,
AK -
DEADLOCK DETECTED == wwv_flow_data
I was hoping (praying) someone could shed further light on why we are experiencing deadlocks in our APEX business applications. We have a number of large organisations using our business suite of apex applications (all LIVE - searches, inserts, updates, deletes) and we are currently struggling to find out what's causing deadlocks that are being generated (these are severely affecting the server performance etc). I know it's difficult to summarise what's causing without a reproducible example but unfortunately we also cannot reproduce it at our developement centre. It is currently only occuring at customer sites on a consistent basis.
Does anyone have any idea how we can go about tracing the cause of these Deadlocks ?
Why are they occurring - there is no specific dml against apex dictionary tables (api's are alwasy used to do things like set session state, clear cache etc)
All we currently have is the generated trace file and some Deadlock examples are below. Why is it always the 'wwv_flow_data' table ?
Also, the majority of them seem to be updating an item to an apex URL (bind vars separated by colons) ie :B6 || ':' || :B5 || ':' || :B4 || ':' || :B3
An example is:
*** 2009-09-29 10:50:24.760
*** ACTION NAME:(PAGE 169) 2009-09-29 10:50:24.759
*** MODULE NAME:(APEX:APPLICATION 147) 2009-09-29 10:50:24.759
*** SERVICE NAME:(SYS$USERS) 2009-09-29 10:50:24.759
*** CLIENT ID:(GHANZANFARJ:2261912940872031) 2009-09-29 10:50:24.759
*** SESSION ID:(4947.3819) 2009-09-29 10:50:24.759
DEADLOCK DETECTED ( 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 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-0089002a-00032b7e 1008 4947 X 710 3585 X
TX-01240010-00023f5f 710 3585 X 1008 4947 X
session 4947: DID 0001-03F0-00000028 session 3585: DID 0001-02C6-00000087
session 3585: DID 0001-02C6-00000087 session 4947: DID 0001-03F0-00000028
Rows waited on:
Session 3585: obj - rowid = 0004AC08 - AABKwIAAaAAAEX1ABZ
(dictionary objn - 306184, file - 26, block - 17909, slot - 89)
Session 4947: obj - rowid = 0004AC08 - AABKwIAAaAAAEX1ABX
(dictionary objn - 306184, file - 26, block - 17909, slot - 87)
Information on the OTHER waiting sessions:
Session 3585:
pid=710 serial=6190 audsid=169143612 user: 6970/<none>
O/S info: user: oracle, term: , ospid: 2113768, machine: rbisprodapp
program: httpd@rbisprodapp (TNS V1-V3)
client info: GHANZANFARJ
application name: APEX:APPLICATION 147, hash value=3432819319
action name: PAGE 169, hash value=1337406124
Current SQL Statement:
UPDATE WWV_FLOW_DATA SET ITEM_VALUE = :B6 || ':' || :B5 || ':' || :B4 || ':' || :B3 WHERE FLOW_INSTANCE = :B2 AND ITEM_ID = :B1
End of information on OTHER waiting sessions.
Current SQL statement for this session:
DELETE FROM WWV_FLOW_DATA WHERE FLOW_INSTANCE = :B1 AND ITEM_ID IN (SELECT ID FROM WWV_FLOW_PAGE_PLUGS WHERE FLOW_ID = :B3 AND PAGE_ID = :B2 AND PLUG_SOURCE_TYPE IN ( 'SIMPLE_CHART', 'UPDATABLE_SQL_QUERY', 'DBMSSQL_CURSOR', 'FUNCTION_RETURNING_DBMSSQL_CURSOR', 'FUNCTION_RETURNING_SQL_QUERY_CACHED', 'FUNCTION_RETURNING_SQL_QUERY', 'STRUCTURED_QUERY', 'SQL_QUERY', 'DYNAMIC_QUERY'))
----- PL/SQL Call Stack -----
object line object
handle number name
7000003679ac978 227 package body FLOWS_030100.WWV_FLOW_DISP_PAGE_PLUGS
70000050e85efb8 10283 package body FLOWS_030100.WWV_FLOW
7000004340cf8c0 255 procedure FLOWS_030100.F
70000039feafba8 31 anonymous blockThis sounds like you are missing some commits in your DML.
Deadlocks normally only occur in Oracle when two sessions try to lock the same rows for update.
Session1: locks row A;
Session2: locks row B;
Session1: tries to lock row B;-- Waiting because of lock by session2
Session2: tries to lock row A; -- Waiting because of lock by session1 / Deadlock
This situation is highly unuasual for an Oracle application and is (almost) always a flaw in application design.
You should try to figure out which DML is being triggered by the two locking sessions. This maybe on an APEX page, but could also be in a database trigger or procedure.
To rule other things out: check which SESSION_ID's are being used by the application at the time of the deadlock. Maybe your users are using some bookmarks that point to the same SESSION_ID... -
Deadlock error on logical standby
Hi All,
I am get an issue where every thing is working fine on Db server but when it is getting replicated to Logical standby i am getting a deadlock error. Please find error logs below
Fri May 20 21:00:56 2011
ORA-00060: Deadlock detected. More info in file /u01/logicalstdby_home/product/admin/XXXXX/bdump/xxlog_p004_15175.trc.
Fri May 20 21:00:56 2011
8
Errors in file /u01/logicalstdby_home/product/admin/XXXXX/bdump/xxlog_lsp0_2207.trc:
ORA-12801: error signaled in parallel query server P004
ORA-00060: deadlock detected while waiting for resource
9
ORA-12801: error signaled in parallel query server P004
ORA-00060: deadlock detected while waiting for resource
LOGSTDBY Analyzer process P003 pid=42 OS id=15173 stopped
Please can anyone help in investigation.
Thanks and Regrads,
AmolHi ,
I have the logs from deadlock file.
There are two queries in this dump. Does this mean that the two queries in the logs (which are actually same) are runing in parellel. Because this actually ran fine on the primary database.
DEADLOCK DETECTED ( 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 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-01350024-00098ad3 44 804 X 46 797 S
TX-012f0006-0008ac28 46 797 X 60 874 S
TX-01340000-000a175c 60 874 X 44 804 S
session 804: DID 0001-002C-0003E40C session 797: DID 0001-002E-00002364
session 797: DID 0001-002E-00002364 session 874: DID 0001-003C-0000019C
session 874: DID 0001-003C-0000019C session 804: DID 0001-002C-0003E40C
Rows waited on:
Session 797: obj - rowid = 00000000 - D/////AAaAAHqeAAAA
(dictionary objn - 0, file - 26, block - 2008960, slot - 0)
Session 874: obj - rowid = 00089976 - AAC5PjAAFAAAmj+AAA
(dictionary objn - 563574, file - 5, block - 157950, slot - 0)
Session 804: obj - rowid = 00089976 - AAC5PjAAFAAAmi3AAA
(dictionary objn - 563574, file - 5, block - 157879, slot - 0)
Information on the OTHER waiting sessions:
Session 797:
pid=46 serial=418 audsid=0 user: 0/SYS
O/S info: user: oracle, term: UNKNOWN, ospid: 15180, machine: db5p
program: oracle@db5p (P006)
Current SQL Statement:
update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
Session 874:
pid=60 serial=20958 audsid=0 user: 0/SYS
O/S info: user: oracle, term: UNKNOWN, ospid: 15182, machine: db5p
program: oracle@db5p (P007)
Current SQL Statement:
update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
End of information on OTHER waiting sessions.
Current SQL statement for this session:
update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
===================================================
PROCESS STATE
Process global information:
process: 0x29c53bcc8, call: 0x29567f358, xact: 0x299db2d90, curses: 0x29c811dd8, usrses: 0x29c811dd8
SO: 0x29c53bcc8, type: 2, owner: (nil), flag: INIT/-/-/0x00
(process) Oracle pid=44, calls cur/top: 0x29567f358/0x29567eb18, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 117
last post received-location: kcbzww
last process to post me: 29c53fc08 42 0
last post sent: 0 0 117
last post sent-location: kcbzww
last process posted by me: 29c53c4b0 188 0
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 0x29f601e88
O/S info: user: oracle, term: UNKNOWN, ospid: 15175
OSD pid info: Unix process pid: 15175, image: oracle@db5p (P004)
Dump of memory from 0x000000029C500F08 to 0x000000029C501110
29C500F00 00000002 00000000 [........]
29C500F10 9C811DD8 00000002 00000004 0003129B [................]
29C500F20 8F34B7A0 00000002 0000001E 0003115B [..4.........[...]
29C500F30 9CA03A98 00000002 0000000B 000313A7 [.:..............]
29C500F40 9EBD0510 00000002 0000003D 0003115B [........=...[...]
29C500F50 9C803260 00000002 00000004 0003129B [`2..............]
29C500F60 75E66848 00000001 0000001E 0003115B [Hh.u........[...]
29C500F70 99507DB0 00000002 00000007 000313A7 [.}P.............]
29C500F80 99507F70 00000002 00000007 000313A7 [p.P.............]
29C500F90 995083D0 00000002 00000007 000313A7 [..P.............]
29C500FA0 99508CA8 00000002 00000007 000313A7 [..P.............]
29C500FB0 995093C0 00000002 00000007 000313A7 [..P.............]
29C500FC0 99509AC0 00000002 00000007 000313A7 [..P.............]
29C500FD0 9950AC58 00000002 00000007 000313A7 [X.P.............]
29C500FE0 9950B290 00000002 00000007 000313A7 [..P.............]
29C500FF0 9950D6A0 00000002 00000007 000313A7 [..P.............]
29C501000 994FDAB0 00000002 00000007 000313A7 [..O.............]
29C501010 99510640 00000002 00000007 000313A7 [@.Q.............]
29C501020 99510B80 00000002 00000007 000313A7 [..Q.............]
29C501030 99510FE0 00000002 00000007 000313A7 [..Q.............]
29C501040 99511298 00000002 00000007 000313A7 [..Q.............]
29C501050 99511998 00000002 00000007 000313A7 [..Q.............]
29C501060 99511A78 00000002 00000007 000313A7 [x.Q.............]
29C501070 99511B58 00000002 00000007 000313A7 [X.Q.............]
29C501080 99512350 00000002 00000007 000313A7 [P#Q.............]
29C501090 99513248 00000002 00000007 000313A7 [H2Q.............]
29C5010A0 99513408 00000002 00000007 000313A7 [.4Q.............]
29C5010B0 99513788 00000002 00000007 000313A7 [.7Q.............]
29C5010C0 9CA04DE8 00000002 0000000B 000313A7 [.M..............]
29C5010D0 995144C0 00000002 00000007 000313A7 [.DQ.............]
29C5010E0 99515038 00000002 00000007 000313A7 [8PQ.............]
29C5010F0 995152D8 00000002 00000007 000313A7 [.RQ.............]
29C501100 995159F0 00000002 00000007 000313A7 [.YQ.............]
Thanks,
Amol -
Hi: I am on 10.2.0.3.
Can someone help me with identifying conflicting sqls in deadlock? Is the first (update) sql waiting while the insert one is locking? If so, why they refer to different tables?
Dump file /db/dbdump/XXPRD/udump/fsprd_ora_27440.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /oracle/app/oracle/product/10.2.0
System name: HP-UX
Node name: indxxx17
Release: B.11.23
Version: U
Machine: ia64
Instance name: XXPRD
Redo thread mounted by this instance: 1
Oracle process number: 123
Unix process pid: 27440, image: oracleXXPRD@indxxx17
*** SERVICE NAME:(FSPRD) 2009-02-26 10:28:32.262
*** SESSION ID:(446.2263) 2009-02-26 10:28:32.262
DEADLOCK DETECTED ( 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 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-000a0000-0002a5d5 123 446 X 122 404 X
TX-000b002a-0001b1ea 122 404 X 123 446 S
session 446: DID 0001-007B-0000034A session 404: DID 0001-007A-00000278
session 404: DID 0001-007A-00000278 session 446: DID 0001-007B-0000034A
Rows waited on:
Session 404: obj - rowid = 0000D536 - AAANU2AAXAAAAMeAAA
(dictionary objn - 54582, file - 23, block - 798, slot - 0)
Session 446: obj - rowid = 00000000 - D/////ADAAAAB0eAAA
(dictionary objn - 0, file - 192, block - 7454, slot - 0)
Information on the OTHER waiting sessions:
Session 404:
pid=122 serial=59321 audsid=1173413 user: 59/SYSADM
O/S info: user: SYSTEM, term: INDXXX80, ospid: 2424:4888, machine: ENT\INDXXX80
program: sqrw.exe
client info: BGILBERT,2424
application name: sqrw.exe, hash value=0
Current SQL Statement:
UPDATE PS_BI_LOADGL_PROC SET BI_LOAD_GL_STAT = :1 where OPRID = :2 and RUN_CNTL_ID = :3 and SEQ_NUM = :4
End of information on OTHER waiting sessions.
Current SQL statement for this session:
INSERT INTO PS_BI_ACCT_ENTRY (BUSINESS_UNIT,INVOICE,LINE_SEQ_NUM,ACCOUNTING_DT,ACCT_ENTRY_TYPE,DISC_SUR_LVL,DISC_SUR_ID,LINE_DST_SEQ_NUM,TAX_AUTHORITY_CD,D
ISC_SUR_INDICATOR,BUSINESS_UNIT_GL,LEDGER_GROUP,LEDGER,ACCOUNTING_PERIOD,FISCAL_YEAR,ACCOUNT,ALTACCT,DEPTID,OPERATING_UNIT,PRODUCT,FUND_CODE,CLASS_FLD,PROGRA
M_CODE,BUDGET_REF,AFFILIATE,AFFILIATE_INTRA1,AFFILIATE_INTRA2,CHARTFIELD1,CHARTFIELD2,CHARTFIELD3,PROJECT_ID,STATISTICS_CODE,MONETARY_AMOUNT,STATISTIC_AMOUNT
,OPEN_ITEM_KEY,JRNL_LN_REF,LINE_DESCR,USER1,USER2,USER3,USER4,USER5,JOURNAL_ID,JOURNAL_LINE,BUDGET_HDR_STATUS,BUDGET_LINE_STATUS,KK_TRAN_OVER_FLAG,KK_TRAN_OV
ER_OPRID,GL_DISTRIB_STATUS,PROCESS_INSTANCE,APPL_JRNL_ID,CURRENCY_CD,FOREIGN_CURRENCY,FOREIGN_AMOUNT,RT_TYPE,RATE_MULT,RATE_DIV,DOC_TYPE,DOC_SEQ_NBR,DOC_SEQ_
DATE,FROM_ACCRUAL,BUSINESS_UNIT_PC,ACTIVITY_ID,RESOURCE_TYPE,RESOURCE_CATEGORY,RESOURCE_SUB_CAT,ANALYSIS_TYPE,ENTRY_EVENT) select B2.BUSINESS_UNIT, B2.INVOIC
E, B2.LINE_SEQ_NUM, B2.ACCOUNTING_DT, B2.ACCT_ENTRY_TYPE, B2.DISC_SUR_LVL, B2.DISC_SUR_ID, B2.LINE_DST_SEQ_NUM, B2.TAX_AUTHORITY_CD, B2.DISC_SUR_INDICATOR, B
2.BUSINESS_UNIT_GL, B2.LEDGER_GROUP, B2.LEDGER, B2.ACCOUNTING_PERIOD, B2.FISCAL_YEAR, B2.ACCOUNT,B2.ALTACCT,B2.DEPTID,B2.OPERATING_UNIT,B2.PRODUCT,B2.FUND_CO
DE,B2.CLASS_FLD,B2.PROGRAM_CODE,B2.BUDGET_REF,B2.AFFILIATE,B2.AFFILIATE_INTRA1,B2.AFFILIATE_INTRA2,B2.CHARTFIELD1,B2.CHARTFIELD2,B2.CHARTFIELD3,B2.PROJECT_ID
,B2.STATISTICS_CODE, B2.MONETARY_AMOUNT, B2.STATISTIC_AMOUNT, B2.OPEN_ITEM_KEY, B2.JRNL_LN_REF, B2.LINE_DESCR, B2.USER1, B2.USER2, B2.USER3, B2.USER4,
B2.USER5, B2.JOURNAL_ID, B2.JOURNAL_LINE, 'V', 'V', ' ', ' ', 'N', 319204, B2.APPL_JRNL_ID, B2.CURRENCY_CD, B2.FOREIGN_CURRENCY, B2.FOREIGN_AMOUN
T, B2.RT_TYPE, B2.RATE_MULT, B2.RATE_DIV, B2.DOC_TYPE, B2.DOC_SEQ_NBR, B2.DOC_SEQ_DATE, B2.FROM_ACCRUAL, B2.BUSINESS_UNIT_PC, B2.ACTIVITY_ID, B2.RESOU
RCE_TYPE, B2.RESOURCE_CATEGORY, B2.RESOURCE_SUB_CAT, B2.ANALYSIS_TYPE, B2.ENTRY_EVENT from PS_BI_ACCT_LN_STG B2, PS_BI_LDGL_TMP D2 where B2.BUSINESS_UN
IT = D2.BUSINESS_UNIT and B2.INVOICE = D2.INVOICE and B2.BUSINESS_UNIT = :1 and B2.ACCT_ENTRY_TYPE = 'AR' and
D2.PROCESS_INSTANCE = :2
===================================================
PROCESS STATE
Process global information:
process: c00000012b3c9698, call: c0000000ad6da080, xact: c000000129b02ab0, curses: c00000012e53f6f8, usrses: c00000012e53f6f8
SO: c00000012b3c9698, type: 2, owner: 0000000000000000, flag: INIT/-/-/0x00
(process) Oracle pid=123, calls cur/top: c0000000ad6da080/c0000000ad6da080, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 115 0 4
last post received-location: kslpsr
last process to post me: c00000012e3a3c20 1 6
last post sent: 0 0 24
last post sent-location: ksasnd
last process posted by me: c00000012e3a3c20 1 6
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: c00000012b428278
O/S info: user: oracle, term: UNKNOWN, ospid: 27440
OSD pid info: Unix process pid: 27440Taking a somewhat wild guess:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-000a0000-0002a5d5 123 446 X 122 404 X
TX-000b002a-0001b1ea 122 404 X 123 446 S
session 446: DID 0001-007B-0000034A session 404: DID 0001-007A-00000278
session 404: DID 0001-007A-00000278 session 446: DID 0001-007B-0000034A
Rows waited on:
Session 404: obj - rowid = 0000D536 - AAANU2AAXAAAAMeAAA
(dictionary objn - 54582, file - 23, block - 798, slot - 0)
Session 446: obj - rowid = 00000000 - D/////ADAAAAB0eAAA
(dictionary objn - 0, file - 192, block - 7454, slot - 0)If I were to take a guess from the above, session 123 inserted into the child table (or modified a row) and is attemping to insert into the parent table, but was blocked by session 122. Session 122 modified another row in the parent table, but the child table has a missing foreign key index, so the modification of the parent table tried to generate a mode 4 share lock on the child table, but is blocked due to the mode 6 exclusive row lock on the child table acquired by session 123. The mode 4 share lock may be caused by other problems including potential duplicate values in a primary/unique column (should the other session commit), a problem with initrans, bitmap indexes, a session trying to modify a row already modified by another session, or a handful of other problems.
If you search the forum, I have previously posted a couple different deadlock graphs and the SQL code that I used to generate those deadlock graphs. You might find an exact match for the above pattern.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating Inc.
Edited by: Charles Hooper on Mar 3, 2009 7:46 PM
See (/* Test 4 - Transaction table that does not use a sequence contributes to the problem */):
Re: Deadlock ( holds: S, waits: SSX ) -
Deadlocks and very high wait times
We are seeing a very high number of deadlocks in the system. The deadlocks trace all show a 'enq: TX - row lock contention' with wait times of around 2929700+ seconds ex:
last wait for 'enq: TX - row lock contention' blocking sess=0x70000006d85e1b8 seq=55793 wait_time=2929704 seconds since wait started=4
name|mode=54580006, usn<<16 | slot=1d0010, sequence=705f
Dumping Session Wait History
for 'enq: TX - row lock contention' count=1 wait_time=2929704
name|mode=54580006, usn<<16 | slot=1d0010, sequence=705f
for 'latch: enqueue hash chains' count=1 wait_time=1649
address=70000006dbb4a20, number=13, tries=0
for 'enq: TX - row lock contention' count=1 wait_time=2929708
name|mode=54580006, usn<<16 | slot=1d0010, sequence=705f
for 'SQL*Net message from client' count=1 wait_time=101740
driver id=54435000, #bytes=1, =0
for 'SQL*Net message to client' count=1 wait_time=1
driver id=54435000, #bytes=1, =0
for 'direct path write temp' count=1 wait_time=921
file number=fb, first dba=6521b, block cnt=2
for 'SQL*Net more data from client' count=1 wait_time=3
driver id=54435000, #bytes=10, =0
for 'SQL*Net more data from client' count=1 wait_time=5
driver id=54435000, #bytes=1e, =0
for 'SQL*Net more data from client' count=1 wait_time=10
driver id=54435000, #bytes=2c, =0
for 'SQL*Net more data from client' count=1 wait_time=5
driver id=54435000, #bytes=3a, =0
Any ideas on how to resolve this ?
Thanks
SuryaSorry for the typo, that Ora-0060 error we are seeing. Here is the deadlock graph:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining Scoring Engine
and Real Application Testing options
ORACLE_HOME = /orasw/product/10.2.0.4.0
System name: AIX
Node name: spda5001
Release: 3
Version: 5
Machine: 00074D5AD400
Instance name: IAMS01P1
Redo thread mounted by this instance: 1
Oracle process number: 21
Unix process pid: 2306444, image: oracle@spda5001
*** 2011-12-24 05:05:39.885
*** SERVICE NAME:(IAMS01P) 2011-12-24 05:05:39.884
*** SESSION ID:(443.2130) 2011-12-24 05:05:39.884
DEADLOCK DETECTED ( 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 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-00080020-000c3957 21 443 X 58 391 X
TX-001d0010-0000705f 58 391 X 21 443 X
session 443: DID 0001-0015-0000002E session 391: DID 0001-003A-00000081
session 391: DID 0001-003A-00000081 session 443: DID 0001-0015-0000002E
Rows waited on:
Session 391: obj - rowid = 0001098B - AAATtpAAGAAADROAAD
(dictionary objn - 67979, file - 6, block - 13390, slot - 3)
Session 443: obj - rowid = 00010B25 - AAARRwAAGAAAAdgAAN
(dictionary objn - 68389, file - 6, block - 1888, slot - 13)
Information on the OTHER waiting sessions:
Session 391:
pid=58 serial=16572 audsid=52790041 user: 93/IAMS_USR
O/S info: user: , term: , ospid: 1234, machine: mac3023
program:
Current SQL Statement:
update spt_identity set created=:1, modified=:2, owner=:3, assigned_scope=:4, assigned_scope_path=:5, extended1=:6, extended2=:7, extended3=:8, extended4=:9, extended5=:10, extended6=:11, extended7=:12, extended8=:13, extended9=:14, extended10=:15, extended11=:16, extended12=:17, extended13=:18, extended14=:19, extended15=:20, extended16=:21, extended17=:22, extended18=:23, extended19=:24, extended20=:25, name=:26, description=:27, protected=:28, iiqlock=:29, attributes=:30, manager=:31, display_name=:32, firstname=:33, lastname=:34, email=:35, manager_status=:36, inactive=:37, last_login=:38, last_refresh=:39, password=:40, password_expiration=:41, password_history=:42, bundle_summary=:43, assigned_role_summary=:44, correlated=:45, auth_question_lock_start=:46, failed_auth_question_attempts=:47, controls_assigned_scope=:48, certifications=:49, activity_config=:50, preferences=:51, history=:52, scorecard=:53, uipreferences=:54, attribute_meta_data=:55, workgroup=:56 where id=:57
End of information on OTHER waiting sessions.
Current SQL statement for this session:
update spt_workflow_case set created=:1, modified=:2, owner=:3, assigned_scope=:4, assigned_scope_path=:5, stack=:6, attributes=:7, launcher=:8, host=:9, launched=:10, completed=:11, progress=:12, percent_complete=:13, type=:14, messages=:15, name=:16, description=:17, complete=:18, target_class=:19, target_id=:20, target_name=:21, workflow=:22 where id=:23 -
Deadlock with CREATE GLOBAL TEMPORARY TABLE
I got this error
ORA-00604: error occurred at recursive SQL level 1
ORA-00060: deadlock detected while waiting for resource
while trying to create global temporary table.
Table creation command:
CREATE GLOBAL TEMPORARY TABLE ITUSER.T_0091FBDG ("GOD" char(4) DEFAULT (' ') NOT NULL,"UNKUM" number(10,0) DEFAULT (0) NOT NULL,[a lot of other fields]) ON COMMIT PRESERVE ROWS
There is no outer references in command. So does somebody know where does deadlock come from?
I'm using Oracle 10g.
Edited by: LeopoldStoch on Apr 13, 2010 7:04 AMI have grabbed log files. But it make me even more curious. Here it is:
alert_itdb.log
Thread 1 advanced to log sequence 253 (LGWR switch)
Current log# 1 seq# 253 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO01.LOG
Tue Apr 13 10:53:09 2010
Thread 1 advanced to log sequence 254 (LGWR switch)
Current log# 2 seq# 254 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO02.LOG
Tue Apr 13 10:55:32 2010
Thread 1 advanced to log sequence 255 (LGWR switch)
Current log# 3 seq# 255 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO03.LOG
Tue Apr 13 10:55:49 2010
ORA-00060: Deadlock detected. More info in file c:\oracle\product\10.2.0\admin\itdb\udump\itdb_ora_3868.trc.
Tue Apr 13 11:01:58 2010
Thread 1 advanced to log sequence 256 (LGWR switch)
Current log# 1 seq# 256 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO01.LOG
Tue Apr 13 11:03:29 2010
Thread 1 advanced to log sequence 257 (LGWR switch)
Current log# 2 seq# 257 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO02.LOG
Tue Apr 13 11:14:16 2010
itdb_ora_3868.trc
Dump file c:\oracle\product\10.2.0\admin\itdb\udump\itdb_ora_3868.trc
Tue Apr 13 10:55:48 2010
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Release 10.2.0.4.0 - Production
Windows NT Version V5.2 Service Pack 2
CPU : 2 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:3568M/8188M, Ph+PgF:7889M/12090M, VA:579M/2799M
Instance name: itdb
Redo thread mounted by this instance: 1
Oracle process number: 18
Windows thread id: 3868, image: ORACLE.EXE (SHAD)
*** 2010-04-13 10:55:48.874
*** ACTION NAME:() 2010-04-13 10:55:48.811
*** MODULE NAME:(5436,20100413105316,82100) 2010-04-13 10:55:48.811
*** SERVICE NAME:(ITDB) 2010-04-13 10:55:48.811
*** SESSION ID:(145.52602) 2010-04-13 10:55:48.811
DEADLOCK DETECTED ( 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 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-00080011-0000198d 18 145 X 17 158 S
TX-0006001c-0000192d 17 158 X 18 145 S
session 145: DID 0001-0012-00000164 session 158: DID 0001-0011-000005F5
session 158: DID 0001-0011-000005F5 session 145: DID 0001-0012-00000164
Rows waited on:
Session 158: obj - rowid = 00000000 - D/////AACAAAKy6AAA
(dictionary objn - 0, file - 2, block - 44218, slot - 0)
Session 145: obj - rowid = 00000000 - D/////AACAAAABJAAA
(dictionary objn - 0, file - 2, block - 73, slot - 0)
Information on the OTHER waiting sessions:
Session 158:
pid=17 serial=2727 audsid=241067 user: 60/ITUSER
O/S info: user: VSC03\it_appsrv, term: VSC03, ospid: 2328:2640, machine: WORKGROUP\VSC03
program: AppServer.exe
client info: ELIZ-041.R#046IKSANOV.RIKSANOV.VSC03:8223.2328.5-1-2600.IT_APPSR
application name: 5436,20100413105322,82000, hash value=3107059750
Current SQL Statement:
CREATE GLOBAL TEMPORARY TABLE ITUSER.T_009EFBDN ("GOD" char(4) DEFAULT (' ') NOT NULL,"UNKUM" number(10,0) DEFAULT (0) NOT NULL,"CENA" number(15,5) DEFAULT (0) NOT NULL,"EDI" number(3,0) NULL,"EDI2" number(3,0) NULL,"KOL" number(14,5) DEFAULT (0) NOT NULL,"KOL2" number(14,5) DEFAULT (0) NOT NULL,"SUMMA" number(16,2) DEFAULT (0) NOT NULL,"KOL_N1" number(14,5) DEFAULT (0) NOT NULL,"KOL_N2" number(14,5) DEFAULT (0) NOT NULL,"KOL_N3" number(14,5) DEFAULT (0) NOT NULL,"KOL_N4" number(14,5) DEFAULT (0) NOT NULL,"KOL_N5" number(14,5) DEFAULT (0) NOT NULL,"KOL_N6" number(14,5) DEFAULT (0) NOT NULL,"KOL_N7" number(14,5) DEFAULT (0) NOT NULL,"KOL_N8" number(14,5) DEFAULT (0) NOT NULL,"KOL_N9" number(14,5) DEFAULT (0) NOT NULL,"KOL_N10" number(14,5) DEFAULT (0) NOT NULL,"KOL_N11" number(14,5) DEFAULT (0) NOT NULL,"KOL_N12" number(14,5) DEFAULT (0) NOT NULL,"KOL_N13" number(14,5) DEFAULT (0) NOT NULL,"KOL2N1" number(14,5) DEFAULT (0) NOT NULL,"KOL2N2" number(14,5) DEFAULT (0) NOT NULL,"KOL2N3" number(14,5) DEFAULT (0) NOT NULL,"KOL2N4" number(14,5) DEFAULT (0) NOT NULL,"KOL2N5" number(14,5) DEFAULT (0) NOT NULL,"KOL2N6" number(14,5) DEFAULT (0) NOT NULL,"KOL2N7" number(14,5) DEFAULT (0) NOT NULL,"KOL2N8" number(14,5) DEFAULT (0) NOT NULL,"KOL2N9" number(14,5) DEFAULT (0) NOT NULL,"KOL2N10" number(14,5) DEFAULT (0) NOT NULL,"KOL2N11" number(14,5) DEFAULT (0) NOT NULL,"KOL2N12" number(14,5) DEFAULT (0) NOT NULL,"KOL2N13" number(14,5) DEFAULT (0) NOT NULL,"SUM_N1" number(16,2) DEFAULT (0) NOT NULL,"SUM_N2" number(16,2) DEFAULT (0) NOT NULL,"SUM_N3" number(16,2) DEFAULT (0) NOT NULL,"SUM_N4" number(16,2) DEFAULT (0) NOT NULL,"SUM_N5" number(16,2) DEFAULT (0) NOT NULL,"SUM_N6" number(16,2) DEFAULT (0) NOT NULL,"SUM_N7" number(16,2) DEFAULT (0) NOT NULL,"SUM_N8" number(16,2) DEFAULT (0) NOT NULL,"SUM_N9" number(16,2) DEFAULT (0) NOT NULL,"SUM_N10" number(16,2) DEFAULT (0) NOT NULL,"SUM_N11" number(16,2) DEFAULT (0) NOT NULL,"SUM_N12" number(16,2) DEFAULT (0) NOT NULL,"SUM_N13" number(16,2) DEFAULT (0) NOT NULL,"DATE_REST" date NULL,"KOL_PRI" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRI" number(14,5) DEFAULT (0) NOT NULL,"SUM_PRI" number(16,2) DEFAULT (0) NOT NULL,"DATE_FPRI" date NULL,"NDOC_FPRI" char(20) DEFAULT (' ') NOT NULL,"KOL_PRIG" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRIG" number(14,5) DEFAULT (0) NOT NULL,"SUM_PRIG" number(16,2) DEFAULT (0) NOT NULL,"KOL_PRIT" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRIT" number(14,5) DEFAULT (0) NOT NULL,"KOL_RAS" number(14,5) DEFAULT (0) NOT NULL,"KOL2RAS" number(14,5) DEFAULT (0) NOT NULL,"SUM_RAS" number(16,2) DEFAULT (0) NOT NULL,"DATE_LRAS" date NULL,"NDOC_LRAS" char(20) DEFAULT (' ') NOT NULL,"KOL_RASG" number(14,5) DEFAULT (0) NOT NULL,"KOL2RASG" number(14,5) DEFAULT (0) NOT NULL,"SUM_RASG" number(16,2) DEFAULT (0) NOT NULL,"KOL_RAST" number(14,5) DEFAULT (0) NOT NULL,"KOL2RAST" number(14,5) DEFAULT (0) NOT NULL,"KOL_PRIREZ" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRIREZ" number(14,5) DEFAULT (0) NOT NULL,"SUM_PRIREZ" number(16,2) DEFAULT (0) NOT NULL,"KOL_RASREZ" number(14,5) DEFAULT (0) NOT NULL,"KOL2RASREZ" number(14,5) DEFAULT (0) NOT NULL,"SUM_RASREZ" number(16,2) DEFAULT (0) NOT NULL,"PRC_RAS" number(3,0) DEFAULT (0) NOT NULL,"KSSM" char(5) NULL,"COMM" char(40) DEFAULT (' ') NOT NULL,"KDM3" char(1) DEFAULT (' ') NOT NULL,"KDM4" char(1) DEFAULT (' ') NOT NULL,"KOL_INV" number(14,5) DEFAULT (0) NOT NULL,"KOL2INV" number(14,5) DEFAULT (0) NOT NULL,"CENA_INV" number(15,5) DEFAULT (0) NOT NULL,"SUM_INV" number(16,2) DEFAULT (0) NOT NULL,"DATE_INV" date NULL,"KSBG" char(3) DEFAULT (' ') NOT NULL,"KOL_C" number(14,5) DEFAULT (0) NOT NULL,"KOL2C" number(14,5) DEFAULT (0) NOT NULL,"SUM_C" number(16,2) DEFAULT (0) NOT NULL,"KBLS" char(5) DEFAULT (' ') NOT NULL,"BS_ZATR" char(10) NULL,"KAU_ZATR" char(12) DEFAULT (' ') NOT NULL,"MECEXPL" number(3,0) DEFAULT (0) NOT NULL,"SUM_IZNOS" number(14,2) DEFAULT (0) NOT NULL,"SUM_IMEC" number(14,2) DEFAULT (0) NOT NULL,"NINKAS" number(10,0) DEFAULT (0) NOT NULL,"DATE_D" date NULL,"FIO_D" char(10) DEFAULT (' ') NOT NULL,"DATE_K" date NULL,"FIO_O" char(10) DEFAULT (' ') NOT NULL,"STDCURR" char(1) DEFAULT (' ') NOT NULL) ON COMMIT PRESERVE ROWS
End of information on OTHER waiting sessions.
Current SQL statement for this session:
insert into col$(obj#,name,intcol#,segcol#,type#,length,precision#,scale,null$,offset,fixedstorage,segcollength,deflength,default$,col#,property,charsetid,charsetform,spare1,spare2,spare3)values(:1,:2,:3,:4,:5,:6,decode(:5,182/*DTYIYM*/,:7,183/*DTYIDS*/,:7,decode(:7,0,null,:7)),decode(:5,2,decode(:8,-127/*MAXSB1MINAL*/,null,:8),178,:8,179,:8,180,:8,181,:8,182,:8,183,:8,231,:8,null),:9,0,:10,:11,decode(:12,0,null,:12),:13,:14,:15,:16,:17,:18,:19,:20)
===================================================
PROCESS STATE
Process global information:
process: 5F28A1F8, call: 5F3A8E98, xact: 5DFF8B40, curses: 5F37D6A8, usrses: 5F375F38
SO: 5F28A1F8, type: 2, owner: 00000000, flag: INIT/-/-/0x00
(process) Oracle pid=18, calls cur/top: 5F3A8E98/5F3A75B8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 117
last post received-location: kcbzww
last process to post me: 5f289c00 93 0
last post sent: 0 0 117
last post sent-location: kcbzww
last process posted by me: 5f289c00 93 0
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 5F2BC4EC
O/S info: user: SYSTEM, term: VSC03, ospid: 3868
OSD pid info: Windows thread id: 3868, image: ORACLE.EXE (SHAD)
Dump of memory from 0x5F276E78 to 0x5F276FFC
5F276E70 0000000B 5E1231B8 [.....1.^]
5F276E80 00000010 000313A9 5F3A75B8 00000003 [.........u:_....]
5F276E90 000313A9 5F4B92D4 0000000B 000313A9 [......K_........]
5F276EA0 5F375F38 00000004 0003129D 5DE1FFA4 [8_7_...........]]
5F276EB0 00000007 000313A9 5DE20028 00000007 [........(..]....]
5F276EC0 000313A9 5DE200BC 00000007 000313A9 [.......]........]
5F276ED0 5DE20140 00000007 000313A9 5DE201C4 [@..]...........]]
5F276EE0 00000007 000313A9 5DE20248 00000007 [........H..]....]
5F276EF0 000313A9 5DE202CC 00000007 000313A9 [.......]........]
5F276F00 00000000 00000000 00000000 00000000 [................]
Repeat 14 times
5F276FF0 00000000 00000000 00000000 [............]
(FOB) flags=2 fib=5DEEEC98 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\UNDOTBS01.DBF
fno=2 lblksz=8192 fsiz=311040
(FOB) flags=2 fib=5DEEE608 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\CONTROL03.CTL
fno=2 lblksz=16384 fsiz=430
(FOB) flags=2 fib=5DEEE2C8 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\CONTROL02.CTL
fno=1 lblksz=16384 fsiz=430
(FOB) flags=2 fib=5DEEDF88 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\CONTROL01.CTL
fno=0 lblksz=16384 fsiz=430
(FOB) flags=2 fib=5DEEF658 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\ITDATA01.DBF
fno=5 lblksz=8192 fsiz=2109440
(FOB) flags=2 fib=5DEEE948 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\SYSTEM01.DBF
fno=1 lblksz=8192 fsiz=79360
(FOB) flags=2 fib=5DEEFCE8 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\TEMP01.DBF
fno=201 lblksz=8192 fsiz=43776
SO: 5F375F38, type: 4, owner: 5F28A1F8, flag: INIT/-/-/0x00
(session) sid: 145 trans: 5D06D4B0, creator: 5F28A1F8, flag: (8100041) USR/- BSY/-/-/-/-/-
DID: 0001-0012-00000164, short-term DID: 0000-0000-00000000
txn branch: 00000000
oct: 1, prv: 0, sql: 50B2BAC0, psql: 57554078, user: 60/ITUSER
service name: ITDB
O/S info: user: VSC03\it_appsrv, term: VSC03, ospid: 3668:3616, machine: WORKGROUP\VSC03
program: AppServer.exe
client info: ELIZ-041.R#046IKSANOV.RIKSANOV.VSC03:8223.3668.5-1-2600.IT_APPSR
application name: 5436,20100413105316,82100, hash value=3093400541
last wait for 'enq: TX - allocate ITL entry' blocking sess=0x5F386200 seq=4256 wait_time=2999487 seconds since wait started=2
name|mode=54580004, usn<<16 | slot=6001c, sequence=192d
Dumping Session Wait History
for 'enq: TX - allocate ITL entry' count=1 wait_time=2999487
name|mode=54580004, usn<<16 | slot=6001c, sequence=192d
for 'buffer busy waits' count=1 wait_time=10
file#=1, block#=f923, class#=1
for 'buffer busy waits' count=1 wait_time=53
file#=1, block#=d1ff, class#=1
for 'buffer busy waits' count=1 wait_time=36
file#=1, block#=19, class#=4
for 'buffer busy waits' count=1 wait_time=28
file#=1, block#=19, class#=4
for 'buffer busy waits' count=1 wait_time=27
file#=1, block#=f923, class#=1
for 'buffer busy waits' count=1 wait_time=13
file#=1, block#=ec86, class#=1
for 'buffer busy waits' count=1 wait_time=29
file#=1, block#=f923, class#=1
for 'buffer busy waits' count=1 wait_time=15
file#=1, block#=f95d, class#=1
for 'buffer busy waits' count=1 wait_time=215
file#=1, block#=d1ff, class#=1
temporary object counter: 1
UOL used : 0 locks(used=2, free=10)
KGX Atomic Operation Log 69405330
Mutex 00000000(0, 0) idn 0 oper NONE
Cursor Parent uid 145 efd 5 whr 11 slp 0
oper=NONE pt1=A4744BC4 pt2=6842B2F4 pt3=A4744B94
pt4=00000000 u41=0 stt=0
KGX Atomic Operation Log 69405358
Mutex 50B2BB74(0, 1) idn 0 oper NONE
Cursor Stat uid 145 efd 8 whr 1 slp 0
oper=NONE pt1=50B2BAC0 pt2=00000000 pt3=00000000
pt4=00000000 u41=0 stt=8
KGX Atomic Operation Log 69405380
Mutex 00000000(0, 0) idn 0 oper NONE
Library Cache uid 145 efd 0 whr 0 slp 0
SO: 5C5A6334, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c5a6334 handle=5e9a6868 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C5A6384[5C76A228,5C59D1D0] htb=5C59D1D0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=CBK[0020] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=5e9a6868 mtx=5E9A691C(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=S latch#=1 hpc=c742 hlc=c742
lwt=5E9A68C4[5E9A68C4,5E9A68C4] ltm=5E9A68CC[5E9A68CC,5E9A68CC]
pwt=5E9A68A8[5E9A68A8,5E9A68A8] ptm=5E9A68B0[5E9A68B0,5E9A68B0]
ref=5E9A68E4[662DCE3C,662DCE3C] lnd=5E9A68F0[5E9A68F0,5E9A68F0]
LIBRARY OBJECT: object=51e6451c
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=18
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 a1f966d4 51e645b4 I/P/A/-/- 0 NONE 00
6 662dcce4 a24e2534 I/P/A/-/E 0 NONE 00
KGX Atomic Operation Log 50C2014C
Mutex 662DCC54(0, 2) idn d64ee82 oper SHRD
Cursor Pin uid 145 efd 0 whr 3 slp 0
opr=4 pso=5C5A6334 flg=0
pcs=662DCC54 nxt=5B9C77F4 flg=18 cld=0 hd=5E9A6868 par=54763C50
ct=2 hsh=0 unp=00000000 unn=0 hvl=662dcff0 nhv=0 ses=00000000
hep=662DCCA0 flg=80 ld=1 ob=51E6451C ptr=A24E2534 fex=A24E16F8
SO: 5C76A1D8, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c76a1d8 handle=5a67b168 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C76A228[5C59D1D0,5C5A6384] htb=5C59D1D0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=5a67b168 mtx=5A67B21C(2) cdp=2
name=
insert into col$(obj#,name,intcol#,segcol#,type#,length,precision#,scale,null$,offset,fixedstorage,segcollength,deflength,default$,col#,property,charsetid,charsetform,spare1,spare2,spare3)values(:1,:2,:3,:4,:5,:6,decode(:5,182/*DTYIYM*/,:7,183/*DTYIDS*/,:7,decode(:7,0,null,:7)),decode(:5,2,decode(:8,-127/*MAXSB1MINAL*/,null,:8),178,:8,179,:8,180,:8,181,:8,182,:8,183,:8,231,:8,null),:9,0,:10,:11,decode(:12,0,null,:12),:13,:14,:15,:16,:17,:18,:19,:20)
hash=012a6293ef607cee606b82dc0d64ee82 timestamp=04-08-2010 17:06:19
namespace=CRSR flags=RON/KGHP/TIM/PN0/LRG/KST/DBN/MTX/[100100d1]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=c298 hlc=c298
lwt=5A67B1C4[5A67B1C4,5A67B1C4] ltm=5A67B1CC[5A67B1CC,5A67B1CC]
pwt=5A67B1A8[5A67B1A8,5A67B1A8] ptm=5A67B1B0[5A67B1B0,5A67B1B0]
ref=5A67B1E4[5A67B1E4,5A67B1E4] lnd=5A67B1F0[5A67B1F0,5A67B1F0]
LIBRARY OBJECT: object=54763bb8
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 662dd020 662dce3c 5e9a6868
1 662dd020 5b9c7940 5eb1fdbc
DATA BLOCKS:
data# heap pointer status pins change whr
0 54c98590 54763c50 I/P/A/-/- 0 NONE 00
SO: 5C5AFBCC, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c5afbcc handle=6ad6312c mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C5AFC1C[5C61B52C,5C59D0B0] htb=5C59D0B0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=6ad6312c mtx=6AD631E0(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=2 hpc=b9a0 hlc=b9a0
lwt=6AD63188[6AD63188,6AD63188] ltm=6AD63190[6AD63190,6AD63190]
pwt=6AD6316C[6AD6316C,6AD6316C] ptm=6AD63174[6AD63174,6AD63174
SO: 5C5A5C34, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c5a5c34 handle=69731e20 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C5A5C84[5C59D4D0,5C6074B0] htb=5C59D4D0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=69731e20 mtx=69731ED4(2) cdp=2
name=update con$ set con#=:3 where owner#=:1 and name=:2
hash=cb0043a665029adc35682cfd8f583ce2 timestamp=04-08-2010 17:10:17
namespace=CRSR flags=RON/KGHP/TIM/PN0/SML/KST/DBN/MTX/[120100d0]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=2 hpc=ac50 hlc=ac50
lwt=69731E7C[69731E7C,69731E7C] ltm=69731E84[69731E84,69731E84]
pwt=69731E60[69731E60,69731E60] ptm=69731E68[69731E68,69731E68]
ref=69731E9C[69731E9C,69731E9C] lnd=69731EA8[69731EA8,69731EA8]
LIBRARY OBJECT: object=66177404
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 5887c454 5887c270 69641ffc
1 5887c454 5887c400 693d29b4
DATA BLOCKS:
data# heap pointer status pins change whr
0 57178070 6617749c I/P/A/-/- 0 NONE 00
SO: 5C62D288, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c62d288 handle=5734d800 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C62D2D8[5C59D590,5C59D590] htb=5C59D590 ssga=5C59CD04
user=5f375f38 session=5f375f38 count=0 flags=LRU/[4000] savepoint=0x17ee5af
LIBRARY OBJECT HANDLE: handle=5734d800 mtx=5734D8B4(0) cdp=0
name=SYS._default_auditing_options_
hash=fab1a450ca8625c88d7aa501cb042efa timestamp=03-14-2008 18:46:51
namespace=TABL flags=KGHP/TIM/SML/[02000000]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=3e1e hlc=3e1e
lwt=5734D85C[5734D85C,5734D85C] ltm=5734D864[5734D864,5734D864]
pwt=5734D840[5734D840,5734D840] ptm=5734D848[5734D848,5734D848]
ref=5734D87C[5734D87C,5734D87C] lnd=5734D888[5734D888,5734D888]
LIBRARY OBJECT: object=69e8d9e4
type=TABL flags=EXS/LOC[0005] pflags=[0000] status=VALD load=0
DATA BLOCKS:
data# heap pointer status pins change whr
0 572f55b0 69e8da7c I/-/A/-/- 0 NONE 00
SO: 5C62CA38, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c62ca38 handle=54e2b2d0 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C62CA88[5C7875E0,5C59D458] htb=5C59D458 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=54e2b2d0 mtx=54E2B384(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=cb1c hlc=cb1c
lwt=54E2B32C[54E2B32C,54E2B32C] ltm=54E2B334[54E2B334,54E2B334]
pwt=54E2B310[54E2B310,54E2B310] ptm=54E2B318[54E2B318,54E2B318]
ref=54E2B34C[66147E34,66147E34] lnd=54E2B358[54E2B358,54E2B358]
LIBRARY OBJECT: object=51e651ac
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=18
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 6a86de6c 51e65244 I/P/A/-/- 0 NONE 00
6 66147cdc 9dabe588 I/-/A/-/E 0 NONE 00
SO: 5C787590, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c787590 handle=57422b64 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C7875E0[5C59D458,5C62CA88] htb=5C59D458 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=57422b64 mtx=57422C18(2) cdp=2
name=insert into obj$(owner#,name,namespace,obj#,type#,ctime,mtime,stime,status,remoteowner,linkname,subname,dataobj#,flags,oid$,spare1,spare2)values(:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13,:14,:15,:16, :17)
hash=8876f3fed7222711572e6a76e623c9d3 timestamp=04-08-2010 17:06:19
namespace=CRSR flags=RON/KGHP/TIM/PN0/MED/KST/DBN/MTX/[500100d0]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=60c0 hlc=60c0
lwt=57422BC0[57422BC0,57422BC0] ltm=57422BC8[57422BC8,57422BC8]
pwt=57422BA4[57422BA4,57422BA4] ptm=57422BAC[57422BAC,57422BAC]
ref=57422BE0[57422BE0,57422BE0] lnd=57422BEC[57422BEC,57422BEC]
LIBRARY OBJECT: object=6a7276e4
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 66148018 66147e34 54e2b2d0
1 66148018 5896c0ec 6af7d37c
DATA BLOCKS:
data# heap pointer status pins change whr
0 696b76e0 6a72777c I/P/A/-/- 0 NONE 00
SO: 5C78B970, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c78b970 handle=54fbd288 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C78B9C0[5C787B90,5C59D1B0] htb=5C59D1B0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=54fbd288 mtx=54FBD33C(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=3 hpc=f79a hlc=f79a
lwt=54FBD2E4[54FBD2E4,54FBD2E4] ltm=54FBD2EC[54FBD2EC,54FBD2EC]
pwt=54FBD2C8[54FBD2C8,54FBD2C8] ptm=54FBD2D0[54FBD2D0,54FBD2D0]
ref=54FBD304[5BF92EF0,5BF92EF0] lnd=54FBD310[54FBD310,54FBD310]
LIBRARY OBJECT: object=541e8b98
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=16
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 693cb454 541e8c30 I/P/A/-/- 0 NONE 00
6 5bf92e34 a021d62c I/-/A/-/E 0 NONE 00
SO: 5C787B40, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c787b40 handle=5eb09aec mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C787B90[5C59D1B0,5C78B9C0] htb=5C59D1B0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=5eb09aec mtx=5EB09BA0(2) cdp=2
name=select o.owner#,o.name,o.namespace,o.remoteowner,o.linkname,o.subname,o.dataobj#,o.flags from obj$ o where o.obj#=:1
hash=ae93e4a5100360375a3ff87632f4667e timestamp=04-02-2010 10:17:58
namespace=CRSR flags=RON/KGHP/TIM/PN0/MED/KST/DBN/MTX/[500100d0]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=3 hpc=d23e hlc=d23e
lwt=5EB09B48[5EB09B48,5EB09B48] ltm=5EB09B50[5EB09B50,5EB09B50]
pwt=5EB09B2C[5EB09B2C,5EB09B2C] ptm=5EB09B34[5EB09B34,5EB09B34]
ref=5EB09B68[5EB09B68,5EB09B68] lnd=5EB09B74[5EB09B74,5EB09B74]
LIBRARY OBJECT: object=5bf92fd4
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 5bf92f60 5bf92d7c 5eb099a8
1 5bf92f60 5bf92ef0 54fbd288
2 5bf92f60 5b9aa120 576a80c8
3 5bf92f60 5b9aa284 54f7a6d0
DATA BLOCKS:
data# heap pointer status pins change whr
0 5eb09a7c 5bf9306c I/P/A/-/- 0 NONE 00 -
Hi , iam geeting a dead log error from an autonomous trigger.
But in log file it show the same session nos'
DEADLOCK DETECTED ( 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 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-00010003-00000459 16 188 X 16 188 X
session 188: DID 0001-0010-000021B4 session 188: DID 0001-0010-000021B4
Rows waited on:
Session 188: obj - rowid = 00002F8A - AAAC+KAAEAAACzcAAA
(dictionary objn - 12170, file - 4, block - 11484, slot - 0)
Information on the OTHER waiting sessions:
End of information on OTHER waiting sessions.
Current SQL statement for this session:
UPDATE SUMMARY SET NAME = :B1 WHERE Mint_NAME = TO_CHAR(:B2 )
----- PL/SQL Call Stack -----
object line object
handle number name
1B5C1E9C 109 BF_AU_IP_TEST
1F957020 8352 package body MINT
1B719024 19 package body ALOADER
1B7615E0 1 anonymous block
===================================================THIS IS MY AUTONOMOUS TRIGGER -BF_AU_IP_TEST
this trigger has the following update staetment
UPDATE SUMMARY SET NAME = :B1 WHERE Mint_NAME = TO_CHAR(:B2 )
Edited by: user8792751 on Aug 19, 2010 2:59 AMDeadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00010003-00000459 16 188 X 16 188 Xyou have a TX (transaction) enqueue with exclusive mode (X) being held and exclusive mode(X) being waited on
Which means that two sessions are doing concurrent DML on the same target.
you have the sql statement involved in the deadlock and you have the row waited on
Rows waited on:
Session 188: obj - rowid = 00002F8A - AAAC+KAAEAAACzcAAAremember that an autonomous transaction when called represents a new session and then don't be surprised to observe deadlock in this situation.
But, please, let me know why you are
(a) using an autonomous transaction
(b) and using an autonomous transaction in trigger
I may help you to find another way to do your requirement
Regards
Mohamed Houri -
DEADLOCK과 INITRANS (같은 TABLE내의 다른 범위의 DATA처리시 ORA-60)
제품 : ORACLE SERVER
작성날짜 : 2000-09-06
DEADLOCK과 INITRANS (같은 TABLE내의 다른 범위의 DATA처리시 ORA-60)
================================================================
deadlock에 관한 일반적인 사항은 <Bul:11742>에 정리되어 있다. 같은 data를
동시에 변경하는 transaction의 경우 deadlock이 발생하는 것은 application
logic을 수정하여 해결해야 하는 경우가 대부분이다.
그런데 같은 table에 대해서 동시에 수행되는 transaction이 각자 서로 다른
data를 처리하는 경우에도 ora-60(deadlock detected while waiting for
resource)이 발생할 수 있다.
예를 들어 한 transaction은 A table의 1월 data를 처리하고, 동시에 다른
transaction은 같은 A table의 2월 data를 처리하는 것과 같은 경우이다.
이러한 경우에도 initrans가 작게 설정되어 있으면, ora-60이 발생할 수 있는데,
이 자료에서는 이와 같이 다른 data를 처리하는 transaction들 사이에서의
ora-60이 발생하는 경우와 조치사항을 확인한다.
1. transaction entry에 대해서
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
table이나 index에 포함된 모든 block에 update/delete/insert와 같은 dml을
수행하기 위해서는 일단 그 block에 transaction정보를 저장시킬 transaction
entry를 확보한 후에 원하는 작업이 수행가능하다.
이 transaction entry의 크기는 os dependent하기는 하나 대부분 23 bytes이며,
table이나 index의 initrans option에 의해, 미리 확보되는 block당 transaction
entry의 갯수가 결정된다. default는 table이 1, index가 2이다.
이 transaction entry가 특정 transaction에 할당되면 그 transaction이 commit
이나 rollback되기 전까지는 다른 transaction에서 사용할 수 없다. 같은
block에 다른 transaction이 dml을 수행하려면, 남은 공간중에서 23 bytes의
transaction entry를 새로 할당하거나, 공간이 없으면 앞에서 먼저 사용중인
transaction이 commit/rollback되기를 기다려야 한다.
2. ORA-60이 발생하는 경우
~~~~~~~~~~~~~~~~~~~~~~~~~
deadlock을 유발시키는 transaction이 서로간에 완전히 다른 data(같은 table)를
처리하더라도 그 data가 같은 block에 함께 들어가 있는 경우라면 ORA-60이
발생할 수 있다. 즉, transaction entry를 잡는 과정에서 block내에 남은
space가 부족한 경우, 서로 상대방의 transaction이 종료되기를 기다리는
deadlock이 발생가능하다는 것이다.
아래에 실제 예를 들어 자세한 발생 시나리오를 정리하였다.
1. ORDER table은 날짜별로 data가 추가, 변경, 삭제되는 100만건 이상의 data를
가진 table이다. 이 table에 대해서 월별로 통계작업을 수행하는데, 6개월씩
처리하기 위해 6개 transaction을 동시에 수행하였다.
즉, T1은 1월 data, T2는 2월 data, T6는 6월 data를 처리하는 식이다.
2. ORDER table은 initrans값이 1로 지정되어 있고 현재 1000개의 block이 이
table에 할당되어 있다.
3. 100번지 block에 2월, 3월, 5월 data가 함께 저장되어 있다.
200번지 block에는 2월, 3월 data가 저장되어 있다.
4. T2 transaction이 100번지 block에 이미 확보되어 있는 1개의 transaction
entry를 사용하여 transaction정보를 저장하였다.
그리고, 2월달 data에 대한 작업을 수행하였다.
5. T3 transaction이 200번지 block에 initrans 1에 의해 확보되어 있는 23 bytes
의 transaction entry를 이용하여 transaction정보를 저장한 후 3월달 data에
대한 처리를 수행하였다.
6. T2 transaction이 2월달 data중 나머지 부분을 처리하기 위해 200번지를
access하여 23 bytes의 T2 를 위한 transaction entry를 확보하려고 하였으나,
block에 남은 공간이 없어서, T3 transaction이 commit할때까지 기다린다.
5번 단계에서, initrans에 의해 미리 확보되어 있는 공간을 사용하는 T3
transaction이 종료되면, 그 부분을 T2가 사용할 수 있게 되는 것이다.
7. T3 transaction도 100번지에 있는 3월 data를 처리하기 위해 100번지내에
transaction entry를 추가적으로 확보하려 하였으나, 공간이 없어서,
마찬가지로 미리 100번지 block을 사용하고 있는 T2 transaction이 종료되기
를 기다리게 된다.
8. 6과 7상황에 의해 T2와 T3 transaction은 서로 상대방이 종료되기를 기다리는,
deadlock이 발생하게 되므로 deadlock상황을 유발시킨 T3 transaction이
ORA-60을 발생시키면서 종료되고, T3 transaction은 rollback된다.
200번지에 확보한 transaction entry부분도 반환하여 다른 transaction이
사용가능한 상태가 된다.
9. 8번에서 release된 200번지 block내의 transaction entry 23 bytes를
6번 단계에서 기다리고 있던 T2 transaction이 확보하고 작업을 진행한다.
3. deadlock을 피하기 위한 방법
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
결론적으로, 같은 table에 대해서 다른 data를 처리하는 transaction이라
하더라도 동시에 수행하는 transaction이 많은 경우라면 initrans 값이 작은
경우 ora-60이 발생할 수 있게 된다.
하나의 table에 대해서 performance 등의 이유로 동시에 다른 data를 처리하는
transaction을 수행하고자 한다면, table의 initrans 값을 크게하여,
하나의 block에 여러 개의 transaction이 dml 처리를 수행하더라도 space가
부족하여 기다리는 상황은 없도록 하여야 한다.
initrans를 n으로 지정한다면 23*n bytes가 항상 transaction entry로 미리
확보되어 있는 것이다. 이렇게 transaction entry로 초기에 확보된 공간은
data를 저장할 수 없는 공간이 되므로, 너무 크게 하는 것은 space 낭비가
초래된다. 하나의 block에 대해서 동시에 여러 transaction이 처리되지 않는
경우라면 미리 확보된 transaction entry는 사용도 되지 않고 낭비되어, full
table scan 등의 작업에 성능 악화만 초래하게 된다.
initrans 값은 하나의 table에 대해서 동시에 처리하는 transaction의 갯수
이하로 지정하도록 한다. 해당 table에 대한 동시 transaction의 갯수 만큼
initrans를 지정하면 앞에서 설명한 상황의 deadlock은 발생하지 않는 것이
보장되나 space를 고려할 때 그 보다는 약간 작게 하는 것이 일반적인다.
initrans는 table이나 index에 대해서 create나 alter 문장 시 지정, 변경이
가능하나, alter의 경우 이미 확보된 block에는 영향을 미치지 못하므로
export/import를 이용하여 새로 지정하는 것이 필요하다.
다음에 scott.dept table에 대해서 예를 들었다.
column정의 storage등은 임의의 값을 예로 사용한 것이며, initrans도
예로 3을 지정하였다.
os>exp scott/tiger file=test.dmp tables=dept
os>sqlplus scott/tiger
SQL>drop table dept;
SQL>create table dept (deptno number(2), dname varchar2(10))
initrans 3
storage(initial 10m next 2m pctincrease 0);
os>imp scott/tiger file=test.dmp tables=dept ignore=y
Maybe you are looking for
-
Smartview 11.1.2.1.102 Refresh problems
I have multiple users experiencing severe refresh problems after upgrading to smartview version 11.1.2.1.102. Users state Refresh is taking 10-15mins+ when in old version 9x it only takes 1-2mins. In addition users have rebuilt the excel files (copy
-
Efficient way for Continous Creation of XML Content?
Hi I have a requirement of creating xml content from the data extraced from a udp packet. As the packet arrives, i have to generate appropriate xml content from them and keep in the same single xml file. Problem: Since the xml file is not a flat file
-
Hello, I try to send data from BW system to XI. In RWB when I try to start the RFC sender the control data changed to "manually". When I changed the control data to automatically the channel changed to "stopped". I want to configure the RFC sender to
-
Partner role determination PI in purchase orders
Dear All, Does anyone knows if with the release of ECC 6.0 something has been changed about the partner role determination? If we set up a vendor in the previous release with transaction MK01, the partner role PI was determined automatically in the
-
New Powerbook's sound is muted in some apps
I have a new powerbook that I got about a month ago, and to my great unhappiness it's having sound problems. When I am using iTunes sound will be produced as normal, and will most other applications (Myst IV, Reason, Garageband). However, Windows Med