|
Problem IT08278
|
Status: Closed |
SMALL DBHEAP CONFIGURATIONS CAN TRIGGER SLOW CRASH RECOVERY PERFORMANCE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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: *
* Upgrade to DB2 Version 10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.04.2015
17.07.2015
17.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
