DB2 - Problem description
Problem IC84607 | Status: Closed |
TABLE PARTITION REMAINS LOGICALLY DETACHED AFTER DETACH FAILURE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
During partition detach against a range partitioned table, if an APD task is abnormally terminated (e.g. deadlock), its changes will be rolled back internally. The task will be picked up and retried later by the ABP agent, and it will rely on entries in SYSIBM.SYSJOBS and SYSIBM.SYSTASKS to restart and complete the detach. However, it is possible for these entries in SYSIBM.SYSJOBS and SYSIBM.SYSTASKS to be missing, in which case the detach tasks will never complete, and the partition will be stuck as "logically detached" (with STATUS='L' in SYSCAT.DATAPARTITIONS). The fix for this APAR will prevent such condition, but it does not (retroactively) fix the existing issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to DB2 v10.1 Fix Pack 1 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v10.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 02.11.2012 02.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |