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

DB2LOGMGR MAY GET INTO A SELF DEADLATCH SITUATION CAUSING A HANG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 is pruning backups and log files at the end of a backup and 
a simultaneous request to archive or retrieve a log file comes 
in. 
If for example something went wrong inside TSM and a signal 
gets raised, it causes DB2 to not free the sessionCount latch 
and hanging the instance. 
 
You will see the following for db2logmgr: 
 
<LatchInformation> 
Waiting on latch type: (SQLO_LT_sqluvend_C__sessionCountLatch) - 
Address: (000000001347B008), Line: 277, File: sqluvend.C 
 
Holding latch type: (SQLO_LT_sqluvend_C__sessionCountLatch) - 
Address: (000000001347B008), Line: 277, File: sqluvend.C 
HoldCount: 1 
</LatchInformation>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 and Fix Pack 11                   * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 Version 9.7 and Fix Pack 11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.01.2015
09.10.2015
09.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList