DB2 FOR LUW / DB2FORLUW / A10 - DB2

Transaction Log Records are replayed on the database in 
parallel. Some actions however, need to be replayed in a serial 
mode in order to preserve a particular sequence of events. Such 
log records or events are called blocking log records. 
 
The problem in this APAR is that DB2 is blocking some log 
records that it does not need to except for an HADR environment 
with Read ON Standy (ROS) enabled. This has an impact on log 
replay performance during Rollforward, Crash recovery, or on a 
non-ROS HADR Standby as parallel processing has to be suspended 
until these log records are replayed in a serial way. The log 
records affected are related to Index maintenance and the impact 
on replay performance is related to the frequency of these log 
records.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 Fixpack 1 or Higher                         * 
****************************************************************

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First Fixed in v10.1 Fixpack 1

not known / see Local fix

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

14.06.2012
05.11.2012
05.11.2012