|
Problem IT20001
|
Status: Closed |
WITH MULTIPLE DB2READLOG API CALLERS RETRIEVING THE SAME LOG FILE, DB2READLOG API CALLERS MAY TIME OUT OR FAIL WITH SQL2038N |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When two or more db2readlog API callers try to retrieve the same
log file, the
following messages may occur in db2diag.log:
2015-12-14-23.01.48.290843+480 I10452773E1476 LEVEL:
Warning
PID : 29521 TID : 140728323794688 PROC :
db2sysc 0
INSTANCE: lkinst1 NODE : 000 DB :
LKEBBS
HOSTNAME: PG1248
EDUID : 25550 EDUNAME: db2lfr.0 (LKEBBS) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveStartUse, probe:190
DATA #1 : <preformatted>
WARNING: No room for retrieved log number 13365 in
retrieveArray. Index
18446744073709551615 entryCount 264
CALLSTCK: (Static functions may not be resolved correctly, as
they are
resolved to the nearest symbol)
[0] 0x00007FFFEDF0ACCF pdLogPrintf + 0x8F
[1] 0x00007FFFF2E9F68D
_Z21sqlpgRetrieveStartUseP14sqlpMasterDbcbjtPmmPKcmm
+ 0x76D
[2] 0x00007FFFF2EFF7AB
_Z25sqlplfrAddToRetrieveArrayP14sqlpMasterDbcbP12SQLPLFR
_DBCBjPKcP21SQLPLFR_REQ_SCAN_NEXTmPmb + 0xEB
[3] 0x00007FFFF2F03E30
_Z16sqlplfrFMOpenLogP12SQLPLFR_DBCBjP21SQLPLFR_REQ_SCAN_
NEXTmPmPP9SQLP_LECB + 0x31B0
[4] 0x00007FFFF2EF6616
_Z16sqlplfrFMReadLogP12SQLPLFR_DBCBP21SQLPLFR_REQ_SCAN_N
EXTP17SQLPLFR_SCAN_DATA + 0x1C6
[5] 0x00007FFFF2EFA638
_Z17sqlplfrDoScanNextP12SQLPLFR_DBCBP11SQLPLFR_REQ + 0x2
B8
[6] 0x00007FFFF0F7CE8A _Z10sqlplfrEduP9sqpLfrEdu + 0x4CA
[7] 0x00007FFFF0FC7948 _ZN9sqpLfrEdu6RunEDUEv + 0x28
[8] 0x00007FFFF16E0C17 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
[9] 0x00007FFFF0EC98B1 sqloEDUEntry + 0x301
[10] 0x0000003B3A0077F1 /lib64/libpthread.so.0 + 0x77F1
[11] 0x0000003B39CE5CCD clone + 0x6D
or
2017-03-15-08.55.01.297715+600 I2413802A537 LEVEL: Error
PID : 33095832 TID : 91182 PROC :
db2sysc 0
INSTANCE: ap5db2a NODE : 000 DB :
SOREWP01
HOSTNAME: db2ap5
EDUID : 91182 EDUNAME: db2lfr.0 (SOREWP01) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrOpenExtentRetrieve,
probe:210
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
DATA #1 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
89020
Once these messages occurs, db2readlog API callers may time out
or receive
SQL2038N error or are not able to continue retrieving log files
until database
reactivation. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
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
Once the problem occurs, database need to be reactivated to
resolve the issue. |
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.04.2017
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
