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

UPGRADE DATABASE MAY TAKE LONG IN DPF ENVIRONMENT DUE TO DYNAMIC STATEMENT
CACHE INVALIDATION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
You may encounter long running database upgrade in DPF 
environment. 
 
During database upgrade a call to 
SYSIBMINTERNAL.ADMIN_REFRESH_TBSP_ATTRIBS is made. This changes 
the prefetch size for tablespaces. 
As part of this operation DB2 invalidates the dynamic statement 
cache on all DPF partitions. This may take very long. 
 
A db2trc (perfcount) will show a lot of time spent in function 
sqlrlInvalAPMCacheForTable.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 FixPack 4                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 FixPack 4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC97084 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.08.2013
03.06.2014
03.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList