DB2 FOR LUW / DB2FORLUW / 970 - DB2

Problem description: 
Some of the rotating db2diag.xxx.log files for DB2 9.7 are not 
being deleted, which results in the more then 10 db2diag.xxx.log 
file in the db2dump directory. 
 
 
Configuration: 
Linux AMD x86-64 
2 partition system, running on 2 physical hosts. 
DIAGSIZE set to 2 
DB2DUMP directory is shared between nodes. 
DIAGLEVEL is 4 
 
 
Symptom: 
Seven additional db2diag.log files were present under DB2DUMP 
directory. They had various numbers (not sequential) All 
additional files had records from the NODE0001 only. 
 
 
 
Symptom Reproduction: 
 
To reproduce the problem, follow these steps: 
  1. change the DIAGSIZE and DIAGLEVEL 
      db2 update dbm cfg using diagsize 2 
      db2 update dbm cfg using diaglevel 4 
  2. check the changes 
      db2 get dbm cfg | grep -i diagsize 
      db2 get dbm cfg | grep -i diaglevel 
  3. Create the sample database 
      db2sampl 
 
Now you can view all the created .log files under the diag path 
~/sqllib/db2dump 
 
There will be 10 .log files in sequence, and a couple of ones 
that were not deleted.

**************************************************************** 
* USERS AFFECTED:                                              * 
* This problem occurs when user specifies a maximum number of  * 
* logs (total logsize) to be in rotation.                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The cause of the problem is that even when a maximum number  * 
* of log files was specified... extra log files were           * 
* generated.                                                   * 
* This APAR fixes this issue so that now when users specify a  * 
* max number of logs, no additional logs are created.          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP1 or later fix packs.                   * 
* Use the links at the top of this APAR to download the fix    * 
* pack you need.                                               * 
****************************************************************

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
 

First Fixed in DB2 Version 9.7 fix pack 1

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

21.10.2009
18.02.2010
03.02.2011

9.7.FP1