DB2 FOR LUW / DB2FORLUW / A50 - DB2

When two or more db2readlog API callers try to retrieve the same
log file, the following messages may occur in db2diag.log:

2017-10-05-13.53.10.456450-300 I292450665E1644 LEVEL: Warning
PID : 12535 TID : 140735663826688 PROC : db2sysc 0
INSTANCE: INST1          NODE : 000 DB : SAMPLE
HOSTNAME: HOST
EDUID : 442 EDUNAME: db2lfr.0 (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveStartUse, probe:190
MESSAGE : ZRC=0x00000003=3
          SQL0003N The database name is not valid.
          DIA8003C The interrupt has been received.
DATA #1 : 
WARNING: No room for retrieved log number 10908948 in
retrieveArray.
        index: 18446744073709551615
   entryCount: 264
retrieveCount: 264
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00007FFFECC67B0F pdLogPrintf + 0x8F
  [1] 0x00007FFFF1E0D8CC
_Z21sqlpgRetrieveStartUseP14sqlpMasterDbcbjtPmmPKcmm + 0x26C
  [2] 0x00007FFFF1E75B4B
_Z25sqlplfrAddToRetrieveArrayP14sqlpMasterDbcbP12SQLPLFR_DBCBjPK
cP21SQLPLFR_REQ_SCAN_NEXTmPmb + 0xEB
  [3] 0x00007FFFF1E795B4
_Z16sqlplfrFMOpenLogP12SQLPLFR_DBCBjP21SQLPLFR_REQ_SCAN_NEXTmPmP
P9SQLP_LECB + 0x2584
  [4] 0x00007FFFF1E6C9FA
_Z16sqlplfrFMReadLogP12SQLPLFR_DBCBP21SQLPLFR_REQ_SCAN_NEXTP17SQ
LPLFR_SCAN_DATA + 0x28A
  [5] 0x00007FFFF1E7124C
_Z17sqlplfrDoScanNextP12SQLPLFR_DBCBP11SQLPLFR_REQ + 0x2BC
  [6] 0x00007FFFEFE1148C _Z10sqlplfrEduP9sqpLfrEdu + 0x47C
  [7] 0x00007FFFEFE60668 _ZN9sqpLfrEdu6RunEDUEv + 0x28
  [8] 0x00007FFFF05B9007 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
  [9] 0x00007FFFEFD4EB43 sqloEDUEntry + 0x303
  [10] 0x00007FFFF7BC6AA1 /lib64/libpthread.so.0 + 0x7AA1


This is a regression to APAR IT20001, which was not completely
fixed when delivered within Db2 version 10.5 FixPack 9.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 Version 10.5 Fix Pack 10.                     *
****************************************************************

To avoid the problem from happening, set overflow log path
directly to the archive log path (including the chain folder),
example:
db2 update db cfg for sample using overflowlogpath
/data1/jamesji/logs3/jamesji/SAMPV11/NODE0000/LOGSTREAM0000/C000
0000

and ensure that log archive compression (logarchcompr1) is
disabled.

Once the problem occurs, database needs to be reactivated to
resolve the issue.

not known / see Local fix

forerunner  : 
follow-up : IT23817 

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

07.12.2017
12.07.2018
04.06.2020