DB2 FOR LUW / DB2FORLUW / A10 - DB2

In the newer releases of DB2 ( v9.8, v10.1, v10.5 ) if a older 
log file is requested to be read DB2 has to read all the files 
sequentially back up to the old file to verify the correct file 
is chosen. Depending on the number of log files that need to be 
retrieved, and the time required to retrieve each log file, this 
can be a lengthy process where, although the application is 
making progress, it may appear that the application is hung and 
not doing anything.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL who are using db2ReadLog API directly or use tools such  * 
* as QREP which use the API                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP4                                     * 
****************************************************************

To imrove performamce, download or copy all archived log files 
to 
LOGSTREAM<node>/LOGSTREAM<node> directory before running the 
application that uses the db2ReadLog API interface.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Fixed in DB2 v10.1 FP4

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC98804 
follow-up : 

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

11.12.2013
26.06.2014
26.06.2014