DB2 - Problembeschreibung
Problem IT10270 | Status: Geschlossen |
An inplace table reorg may deadlock with a concurrent update operation | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
A space-reclaiming inplace table reorg may deadlock with a concurrent update operating on the same table. This deadlock may not occur if the reorg is reclustering; that is, there is a clustering index on the table, or the reorg specified an index. This problem exists on DB2 V9.7 GA to Fix Pack 10, V10.1 GA to Fix Pack 5 and V10.5 GA. It does not exist on DB2 V10.5 Fix Pack 1 or later. db2pd -eve shows a deadlock as below. ----- Database Partition 0 -- Database SAMPLE -- Active -- xxx Locks being waited on : AppHandl [nod-index] TranHdl Lockname Type Mode Conv Sts CoorEDU AppName AuthID AppID 43815 [000-43815] 222 000100D200000001000000006A Onl Reorg .IN .IX C 6000 db2reorg DB2INST1 xxxxx 21003 [000-21003] 232 000100D200000001000000006A Onl Reorg ..S G 891 db2jcc_a DB2INST1 xxxxx 43815 [000-43815] 222 000100D200000003DDAC002152 Row .NS G 6000 db2reorg DB2INST1 xxxxx 21003 [000-21003] 232 000100D200000003DDAC002152 Row ..X W 891 db2jcc_a DB2INST1 xxxxx ----- In above example, db2jcc_a runs UPDATE command while REORG is executing as db2reorg. The deadlock is between the inplace reorg lock and a row lock. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 11. * **************************************************************** | |
Local-Fix: | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 11. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.07.2015 07.10.2015 07.10.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP11 | |
Problem behoben lt. FixList in der Version | |
9.7.0.11 |