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

SMALL DBHEAP CONFIGURATIONS CAN TRIGGER SLOW CRASH RECOVERY PERFORMANCE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
An indication for a too small DBHEAP configuration and thus a 
slow performing crash recovery is the following db2diag.log 
message: 
 
2015-02-18-09.35.24.993348+120 I9084E522             LEVEL: 
Warning 
PID     : 4132                 TID : 140735793850112 PROC : 
db2sysc 0 
INSTANCE: xxxxxx               NODE : 000            DB   : zzz 
APPHDL  : 0-2233               APPID: *LOCAL.xxxxxx.150218072957 
AUTHID  : xxxxxx               HOSTNAME: yyyyyy 
EDUID   : 8093                 EDUNAME: db2redom (zzz) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpParallelRecovery, 
probe:880 
DATA #1 : <preformatted> 
Resetting max shredder memory to 1833728 from 9523200 
 
This APAR will change the allocation algorithm to allow for 
better crash recovery performance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See SYSROUTE APARs to see where this APAR is addressed       * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.03.2015
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList