DB2 FOR LUW / DB2FORLUW / A50 - DB2

Even when rollforward command is successful with no errors, dump 
files named BPS*.events.bin are generated in DIAGPATH. Users can 
delete these files if the rollforward runs successfully. 
 
Here is sample output: 
 
$ touch dummy 
$ ls -lFrt | tail -6 
-rw-r-----    1 db2inst1  db2users    6291316 Apr 03 17:48 
db2eventlog.000 
drwxrwxrwx    2 db2inst1  db2users        256 May 07 16:58 
events/ 
drwxrwxr-t    2 db2inst1  db2users        256 May 08 05:42 
stmmlog/ 
-rw-rw-rw-    1 db2inst1  db2users      23020 May 21 01:20 
db2inst1.nfy 
-rw-rw-rw-    1 db2inst1  db2users     434858 May 25 23:16 
db2diag.log 
-rw-r--r--    1 db2inst1  db2users          0 May 25 23:16 dummy 
 
$ db2 rollforward db sample to end of logs 
   ... 
DB20000I  The ROLLFORWARD command completed successfully. 
 
$ ls -lFrt | tail -6 
-rw-r--r--    1 db2inst1  db2users          0 May 25 23:16 dummy 
-rw-rw-rw-    1 db2inst1  db2users      23541 May 25 23:17 
db2inst1.nfy 
-rw-rw-rw-    1 db2inst1  db2users     470979 May 25 23:17 
db2diag.log 
-rw-r-----    1 db2inst1  db2users    1048696 May 25 23:17 
SAMPLE.20150525231704.000.SQLB.BPSMed.events.bin 
-rw-r-----    1 db2inst1  db2users    1048696 May 25 23:17 
SAMPLE.20150525231704.000.SQLB.BPSLow.events.bin 
-rw-r-----    1 db2inst1  db2users    8388728 May 25 23:17 
SAMPLE.20150525231704.000.SQLB.BPSHi.events.bin

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using rollforward                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************

First fixed in DB2 Version 10.5 Fix Pack 7.

keiner bekannt / siehe Local-Fix

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

26.05.2015
01.02.2016
01.02.2016