DB2死锁问题。看不懂这是这些log是怎么回事。有没有明白人啊？
20114) Deadlock Event ...
Deadlock ID: 12709
Number of applications deadlocked: 2
Deadlock detection time: 04/12/2011 12:00:09.363976
Rolled back Appl participant no: 2
Rolled back Appl Id: 182.180.17.72.63204.11022307373
Rolled back Appl seq number: : 0832
20115) Deadlock Event ...
Deadlock ID: 12710
Number of applications deadlocked: 2
Deadlock detection time: 04/12/2011 12:10:05.369436
Rolled back Appl participant no: 2
Rolled back Appl Id: 182.180.17.72.63204.11022307373
Rolled back Appl seq number: : 08ba
20116) Deadlocked Connection ...
Deadlock ID: 12710
Participant no.: 1
Participant no. holding the lock: 2
Appl Id: 182.180.17.73.46417.11022307374
Appl Seq number: 00008
Tpmon Client Workstation: JS12_UCS_SVR02
Appl Id of connection holding the lock: 182.180.17.72.63204.11022307373
Seq. no. of connection holding the lock: 00001
Lock wait start time: 04/12/2011 12:10:00.019267
Lock Name : 0x00030015000000000000000752
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Current Mode : none
Deadlock detection time: 04/12/2011 12:10:05.369699
Table of lock waited on : QRTZ_TRIGGERS
Schema of lock waited on : UCS
Data partition id for table : 0
Tablespace of lock waited on : UCS_TBS1
Type of lock: Row
Mode of lock: X - Exclusive
Mode application requested on lock: U - Update
Node lock occured on: 0
Lock object name: 7
Application Handle: 55547
Deadlocked Statement:
Type : Dynamic
Operation: Execute
Section : 1
Creator : NULLID
Package : SYSSH200
Cursor : SQL_CURSH200C1
Cursor was blocking: FALSE
Text : UPDATE qrtz_TRIGGERS SET TRIGGER_STATE = ? WHERE JOB_NAME = ? AND JOB_GROUP = ? AND TRIGGER_STATE = ?
List of Locks:
Lock Name : 0x00030015000000000000000652
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 6
Object Type : Row
Tablespace Name : UCS_TBS1
Table Schema : UCS
Table Name : QRTZ_TRIGGERS
Data partition id : 0
Mode : X - Exclusive
Lock Name : 0x000002430000000100014F8056
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 0
Object Type : Internal - Variation
Data partition id : -1
Mode : S - Share
Lock Name : 0x5359534C564C303128EFECDC41
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 0
Object Type : Internal - Plan
Data partition id : -1
Mode : S - Share
Lock Name : 0x00030015000000000000000054
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 21
Object Type : Table
Tablespace Name : UCS_TBS1
Table Schema : UCS
Table Name : QRTZ_TRIGGERS
Data partition id : 0
Mode : IX - Intent Exclusive
Locks Held: 4
Locks in List: 4
Locks Displayed: 4
20117) Deadlock Event ...
Deadlock ID: 12711
Number of applications deadlocked: 2
Deadlock detection time: 04/12/2011 12:24:06.391814
Rolled back Appl participant no: 2
Rolled back Appl Id: 182.180.17.73.46418.11022307374
Rolled back Appl seq number: : 0aee
20118) Deadlock Event ...
Deadlock ID: 12712
Number of applications deadlocked: 2
Deadlock detection time: 04/12/2011 12:26:07.393723
Rolled back Appl participant no: 2
Rolled back Appl Id: 182.180.17.73.46418.11022307374
Rolled back Appl seq number: : 0b1d
20119) Deadlocked Connection ...
Deadlock ID: 12712
Participant no.: 1
Participant no. holding the lock: 2
Appl Id: 182.180.17.72.63205.11022307374
Appl Seq number: 05050
Tpmon Client Workstation: JS12_UCS_SVR01
Appl Id of connection holding the lock: 182.180.17.73.46418.11022307374
Seq. no. of connection holding the lock: 00001
Lock wait start time: 04/12/2011 12:26:00.022243
Lock Name : 0x00030015000000000000000952
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Current Mode : none
Deadlock detection time: 04/12/2011 12:26:07.394004
Table of lock waited on : QRTZ_TRIGGERS
Schema of lock waited on : UCS
Data partition id for table : 0
Tablespace of lock waited on : UCS_TBS1
Type of lock: Row
Mode of lock: X - Exclusive
Mode application requested on lock: U - Update
Node lock occured on: 0
Lock object name: 9
Application Handle: 55549
Deadlocked Statement:
Type : Dynamic
Operation: Execute
Section : 1
Creator : NULLID
Package : SYSSH200
Cursor : SQL_CURSH200C1
Cursor was blocking: FALSE
Text : UPDATE qrtz_TRIGGERS SET TRIGGER_STATE = ? WHERE JOB_NAME = ? AND JOB_GROUP = ? AND TRIGGER_STATE = ?
List of Locks:
Lock Name : 0x00030015000000000000000752
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 7
Object Type : Row
Tablespace Name : UCS_TBS1
Table Schema : UCS
Table Name : QRTZ_TRIGGERS
Data partition id : 0
Mode : X - Exclusive
Lock Name : 0x000002430000000100014F8056
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 0
Object Type : Internal - Variation
Data partition id : -1
Mode : S - Share
Lock Name : 0x5359534C564C303128EFECDC41
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 0
Object Type : Internal - Plan
Data partition id : -1
Mode : S - Share
Lock Name : 0x00030015000000000000000054
Lock Attributes : 0x00000000
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 21
Object Type : Table
Tablespace Name : UCS_TBS1
Table Schema : UCS
Table Name : QRTZ_TRIGGERS
Data partition id : 0
Mode : IX - Intent Exclusive
Locks Held: 4
Locks in List: 4
Locks Displayed: 4
我用的websphere集群2台web服务器，一台DB服务器。还有quartz任务调度。但是现在一直报死锁错误
[解决办法]
qrtz_TRIGGERS表主键是什么，是否 因为频繁UPDATE造成死锁
[解决办法]
数据库堆 等一些配置参数似乎过小 比如，上千万条记录的更新 用2400个4K，恩~~~~
机器配置如何的？
