DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP4 for a permanent fix or apply the    * 
* suggested workarounds.                                       * 
****************************************************************

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

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Fixed in DB2 v10.1 FP4

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

08.10.2013
02.06.2014
02.06.2014