DB2 - Problem description
Problem IC75177 | Status: Closed |
REDISTRIBUTE ON RANGE PARTITIONED TABLES MIGHT DEADLOCK | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
A redistribute operation on a data partition group containing range partitioned tables might deadlock. This is due to a timing issue between the redistribute progress monitor and redistribute trying to update the tablespace state. The redistribute progress monitor will attempt to lock all tables to get the table size. When the redistribute agent starts working on a tablespace it will attempt to lock all tables in order to update the tablespace state to REDIST IN PROGRESS. Since the two agents lock the tables in different order it is possible with the right timing to hit a deadlock. The workaround is to interrupt the redistribute and issue a REDISTRIBUTE CONTINUE. The fix will be to serialize the redistribute progress monitor with the other agent so that they don't try to lock the tables at the same time. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Redistribute * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.5 FP8 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 V9.5 FP8 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.03.2011 27.06.2011 27.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.8 |