|
Problem IC79332
|
Status: Closed |
TABLE PARTITION REMAINS LOGICALLY DETACHED AFTER DETACH FAILURE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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 Version 9.7 Fix Pack 6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84318 IC84607
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.10.2011
02.08.2012
02.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
