home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC74160 Status: Closed

ROLLFORWARD OF ALTER TABLESPACE REDUCE CAN FAIL WITH TABLESPACE TOO SMALL

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An ALTER TABLESPACE REDUCE will work as expected during normal 
database operation. During a ROLLFORWARD on a HADR STANDBY or 
after a RESTORE, the same ALTER TABLESPACE REDUCE can fail with 
SQLB_TBSPACE_TOO_SMALL. The database will be marked bad due to 
this error. After a restart of the database, the ROLLFORWARD 
will finish the ALTER TABLESPACE REDUCE successfully and 
continue as expected. 
 
This can only happen: 
* when an action right before the ALTER TABLESPACE reduces the 
high water mark of the tablespace, for example a   DROP TABLE 
statement. 
* and the REDUCE shrinks the tablespace below the previous high 
water mark (before the DROP TABLE). 
 
The following message can be found in the db2diag.log file: 
 
2011-01-25-17.29.04.069318-300 I542180A638        LEVEL: Error 
PID     : 1663102              TID  : 5182        PROC : db2sysc 
INSTANCE: xxxx               NODE : 000         DB   : SAMPLE 
APPHDL  : 0-10                 APPID: *LOCAL.xxxxx.110125222809 
AUTHID  : xxxxx 
EDUID   : 5182                 EDUNAME: db2redom (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbValidateContOpsMain, probe:150 
MESSAGE : ZRC=0x8002013A=-2147352262=SQLB_TBSPACE_TOO_SMALL 
          "Cannot reduce tablespace size as requested" 
DATA #1 : <preformatted> 
useablePages is less than the High Water Mark 
useablePages = 9998 
HighWaterMark = 19472
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description above.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
First fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.01.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList