DB2 FOR LUW / DB2FORLUW / A50 - DB2

In a DB2 pureScale environment, each member maintains its own 
set of transaction log files (that is, a log stream) on the 
shared disk, and some transactions sometimes require the log 
stream merges for the db2 examining the records from all log 
streams and ordering the records.  The db2ReadLog API is an 
example. 
 
  And SQL1273N error is returned from db2ReadLog API if the 
target log file does not exist in all of log streams, then the 
db2ReadLog API call may be retried and on the subsequent retry, 
earlier LFS (Log Flash Sequence) number may be specified in LRI 
(Log Record Identifier). 
 
  In such a situation, the log record data with the next LRI may 
be successfully returned from the retry with earlier LFS and the 
subsequent db2ReadLog API calls with the next LRI on the 
previous calls may be succeeded.  But the log records in the 
lost log file will be skipped.

**************************************************************** 
* USERS AFFECTED:                                              * 
* pureScale user                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.0.6                                           * 
****************************************************************

Problem Fixed In 10.5.0.6

not known / see Local fix

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

28.02.2015
16.11.2015
14.12.2015