DB2 FOR LUW / DB2FORLUW / A10 - DB2

There can be instances during database rollforward or HADR 
standby replay where an open transaction or slow internal 
bufferpool flushing may adversely affect the performance of 
recovery.  One will notice that they are in such a situation 
when the DB2 diagnostics log shows frequent entries such as the 
following: 
 
2014-09-26-11.03.02.395365-240 I1815E1419            LEVEL: Info 
PID     : 28919                TID : 140735458305792 PROC : 
db2sysc 0 
INSTANCE: db2inst             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-13                 APPID: *LOCAL.DB2.140920141323 
HOSTNAME: host1 
EDUID   : 94                   EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlprProcessMaxLogFilesOpenInRecoveryThreshold, probe:6876 
DATA #1 : <preformatted> 
Some log stream(s) have reached the maximum number of log files 
that can be opened during recovery threshold. 
Recovery status for log stream 0 
                   lowtranlsn: 00000A3AA349D30C 
                   minbufflsn: 00000A3AC6F1CC3B 
                      headlsn: 00000A3AA349D30C 
       recoveryStartingLFSLSN: 0/0000000000000000 
initialRecoveryStartingLFSLSN: 0/0000000000000000 
                 groupHeadLsn: 00000A3AA349D30C 
              groupMinBuffLSN: 00000A3AC6F1CC3B 
                 HeadExtentID: 140350 
            GroupHeadExtentID: 140350 
               rfwdLogChainId: 22 
              rfwdHeadChainId: 22 
        numLogFilesInRecovery: 256 
                      nextLso: 21120392226938 
                      nextLsn: 00000A3AC6F1CC3C 
                 minPseudoLsn: FFFFFFFFFFFFFFFF 
         LastFullRecLfsLsnLso: 
2975515101/00000A3AC6F1CC3B/21120392226937 
          LastRecLfsLsnLsoLFH: 
2975515101/00000A3AC6F1CC3A/21120392226840 
 
that seems to fill up the DB2 diagnostics log at a high rate. 
 
Additionally, in HADR standby replay scenarios one may notice 
the standby falling behind the primary in terms to replay 
position.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************

If this problem is noticed deactivating the standby and then 
re-activating should correct the problem.  If the problem leads 
to the standby being shutdown unexpectedly, re-activating will 
also work in this case.

First fixed in DB2 Version 10.1 Fix Pack 5.

keiner bekannt / siehe Local-Fix

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

21.10.2014
26.10.2015
26.10.2015