DB2 - Problem description
Problem IC88176 | Status: Closed |
ALTER TABLESPACE REDUCE COMMAND MAY STOP REDUCING THE TABLESPACE'S SIZE AT SOME POINT IN TIME WHILE HWM STILL KEEPS DECREASING | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When you issue an "alter tablespace <TS name> reduce <fixed value>" command, the tablespace's size (TotalPgs) is reduced in line with the falling HWM. However, at a point in time, the HWM may keep decreasing while the TotalPgs variable does not. In the worst case scenario, this may persist until the HWM cannot be decreased any more, at which point the tablespace will be reduced to its target size. For example, you can issue the command from above, on a tablespace called USERSPACE with a 4k page size: "alter tablespace USERSPACE reduce 50 M" and then monitor the tablespace using db2pd: "db2pd -db SAMPLE -tablespaces -repeat 2 100" From the db2pd output below, it is clear that both TotalPgs and the HWM are initially decreasing. However, TotalPgs stops decreasing at a value of 80058, while the HWM continues to decrease. This continues until the HWM hits 52634 (no more free extents below the HWM), at which point TotalPgs is decreased to 72192 (for a total reduction of 12,800 pages, or 50M). Address TotalPgs UsablePgs UsedPgs PndFreePgs FreePgs HWM Max HWM State MinRecTime NQuiescers PathsDropped 0x07000000416DA6E0 84992 84990 52636 0 32354 83056 83056 0x00000000 1351990976 0 No 0x07000000416DA6E0 82258 82256 52638 0 29618 82170 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80458 80456 52638 0 27818 80382 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52638 0 27418 78354 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52636 0 27420 76350 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52638 0 27418 74316 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52636 0 27420 72350 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52636 0 27420 70414 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52638 0 27418 68450 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52636 0 27420 66706 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52636 0 27420 64894 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52634 0 27422 63326 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52634 0 27422 61368 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52636 0 27420 59380 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52634 0 27422 57448 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52634 0 27422 55312 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 80058 80056 52634 0 27422 53390 83056 0x00080000 1351990976 0 No 0x07000000416DA6E0 72192 72190 52634 0 19556 52634 83056 0x00000000 1351990976 0 No 0x07000000416DA6E0 72192 72190 52634 0 19556 52634 83056 0x00000000 1351990976 0 No | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 fix pack 8 * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in version 9.7 fix pack 8 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.11.2012 15.04.2013 15.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |