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

OFFLINE ADD NODE AND NORMAL DB2START FAIL DUE TO DEADLATCH DURING INSTANCE
STARTUP

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During instance startup on a partition, a deadlatch may occur 
while initiializing the DBMS memory set. In rare circumstances, 
additional memory may need to be allocated while trying to set 
up the memory set which leads to a deadlatch situation. This is 
due to an internal accounting error when estimating the initial 
size of a memory heap. If the deadlatch occurs then db2start 
will timeout or hang. 
 
A db2trc taken during db2start would look like this if the issue 
occurs: 
 
11541          0.986140292   DB2StartMain data [probe 375] 
11542          0.986141042   | SqloMemController::initialize 
entry 
11543          0.986141941   | SqloMemController::initialize 
exit 
11544          0.986143324   | sqloRegisterMemorySetWithPMC 
entry 
11545          0.986145712   | | 
SqloMemController::registerConsumer entry 
11546          0.986147470   | | | sqlogmblkEx entry 
11547          0.986150005   | | | | 
SMemBasePool::getNewChunkSubgroup entry 
11548          0.986153271   | | | | | sqlo_xlatch::getConflict 
entry 
11549          0.986206322   | | | | | sqlo_xlatch::getConflict 
mbt [Marker:PD_LATCH_TRACE_WAIT_STARTING ] 
13835        306.975846427   | | | | | | sqleKillNode entry
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See above.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 9.7 FP5 or later                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Deadlatch situation is resolved by properly estimating size of 
internal memory heap. The problem is first fixed in DB2 9.7 FP5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.06.2011
16.12.2011
16.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList