DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 v10.1 Fix Pack 1                               * 
****************************************************************

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 v10.1 Fix Pack 1

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.06.2012
02.11.2012
02.11.2012