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

A LOCK ON THE NOTIFY LOG OR DB2DIAG.LOG CAN MAKE THE ENGINE SO SLOW THAT IT
WOULD LOOK LIKE A HANG

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
A lock by another application or anything else on the notify log 
or db2diag.log file can potentially make the engine work very 
slow if there are lot of messages being asked to be written to 
the log files due to some condition in the engine ( such as lock 
escalation ). The engine can become so slow that it would look 
like a "hang". The situation is exasperated on a DPF system 
where all the nodes are writing to the same db2diag.log or 
notify.log file.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP4 or apply the suggested workaround.   * 
****************************************************************
Local Fix:
Viable workarounds include: 
 
1) Find out who or what is locking the file(s) and kill that 
process OR 
2) db2diag -A ( to change the log file ) -- ( but this will help 
only if the lock is on db2diag.log file ) OR 
3) For DPF systems, have the logs split on Node numbers using 
the new functionality of DIAGPATH ( refer Infocenter ) OR 
4) For DPF systems, have one local DIAGPATH for each physical 
servers OR
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fixed in release DB2 V10.5 FP4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
25.08.2014
25.08.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList