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 IC95388 Status: Closed

EXCESSIVE MEMORY USAGE IN DATABASE HEAP WHEN FAILING ALTER TABLE SPACE
COMMANDS ARE ISSUED ACROSS A LARGE NUMBER OF TABLESPACES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
A 256K database heap allocation required for certain alter 
tablespace commands is unintentionally cached when no internal 
action is required.  The memory is cached per tablespace and 
will be reused for any subsequent alter tablespace command on 
the same tablespace (and may be freed as part of that 
operation). 
 
Commands known to miss freeing the buffer: 
 
1. ALTER TABLESPACE ... REDUCE  where the reduce operation 
cannot proceed.  This will be accompanied by a db2diag.log 
message: 
FUNCTION: DB2 UDB, buffer pool services, sqlbAlterPool, probe:15 
MESSAGE : ADM1534W  Table space "USERSPACE1" could not be 
reduced in size 
          because there are used pages at the end of the table 
space. 
 
2. ALTER TABLESPACE ... REBALANCE where the rebalance operation 
is not required. 
 
The additional cached memory is rarely significant, reused per 
tablespace, and freed at database deactivation.  Systems with a 
very large number of tablespaces where the above commands are 
regularly issued may experience symptoms associated with 
abnormally high memory usage.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All systems                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3                       * 
****************************************************************
Local Fix:
avoid invalid ALTER TABLESPACE commands where possible
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.5 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList