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

ALTER TABLESPACE PREFETCH SIZE ON TABLEPSAPCES WITH MANY OBJECTS FLOODS
CATALOG CACHE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
ALTER TABLEPSACE PREFETCH SIZE on tablespaces with many objects 
will flood the CATALOG CACHE with all the objects from the 
modified tablespace. Symptoms are running out of CATALOG CACHE 
memory and massive performance problems for all applications, 
bringing the database to a hang state. The ALTER TABLESPACE 
command will run for a very long time.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************
Local Fix:
Set CATALOGCACHE_SZ to a much higher value temporarily.
available fix packs:
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
First fixed in DB2 Version 10.5 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.02.2014
06.11.2014
06.11.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList