DB2 FOR LUW / DB2FORLUW / B10 - DB2

Database rollforward or HADR replay of REDUCE MAX operation will
progress with a lower rate than it is required to ensure data
consistency.
Whilst a record of this type is replayed, in the backtrace of
all engine threads one  will see all redo
workers (db2redow EDUs) but one waiting in:

sqlprWaitDuringPRec
sqlprFindQueue
sqlpPRecProcLog
sqlpParallelRecovery
sqleSubCoordProcessRequest

and a single EDU with sqlbMoveOneExtent or sqlbRedoFreeExtents
function on the stack, e.g.:

sqlbMoveOneExtent
sqlbRedoUpdateEMP
sqlbRedo
sqldmrdo
sqlpRecDbRedo
sqlpPRecProcLog
sqlpParallelRecovery

This is caused by a too high level of synchronization for log
records of this type. This APAR will relax the restriction and
allow for a faster processing of log records, that affect other
tablespaces, whilst "REDUCE MAX" is running.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************

not known / see Local fix

forerunner  : IT27769 
follow-up : 

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

15.01.2019
16.01.2020
16.01.2020