suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT38506 Status: Closed

DB2READLOG API FAILS TO RETRIEVE LOG FILE WITH SQL2657N

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
This problem only affects version 11.5.6.0.

The db2ReadLog() API might fail with SQL2657N error saying
Db2 cannot find a log file from the archive location, when in
fact the log file found and successfully retrieved by Db2.
The db2ReadLog() operation is timing out too quickly not
waiting long enough for the log file to be retrieved.

You may see the following db2diag.log messages:

>

2021-09-13-15.02.24.293514-240                       LEVEL: Info
PID     : 1111                 TID : 111111111111111 PROC :
db2sysc 0
INSTANCE: myinst1              NODE : 000            DB   : MYDB
HOSTNAME: myhost1
EDUID   : 60                   EDUNAME: db2logmgr (MYDB) 0
FUNCTION: DB2 UDB, data protection services,
sqpLogMgrEdu::sqlpgRetrieveLogFile, probe:4131
MESSAGE : ADM1843I  Started retrieve for log file
"S0012345.LOG".

>

2021-09-13-15.02.24.393514-240                       LEVEL:
Warning
PID     : 1111                 TID : 111111111111112 PROC :
db2sysc 0
INSTANCE: myinst1              NODE : 000            DB   : MYDB
HOSTNAME: myhost1
EDUID   : 61                   EDUNAME: db2lfr.0 (MYDB) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLookup, probe:500
DATA #1 : 
Log 12345 on log stream 0 is in the array but is still being
retrieved.
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x000072C24BAE8699 pdLogPrintf + 0x79
  [1] 0x000072C253E902B5
_Z19sqlpgRetrieveLookupP14sqlpMasterDbcbjmtPm + 0x3A5
  [2] 0x000072C25401F356
_Z16sqlplfrFMOpenLogP12SQLPLFR_DBCBjP21SQLPLFR_REQ_SCAN_NEXTPmPP
9SQLP_LECB + 0x3DF6
  [3] 0x000072C2540051D6
_Z16sqlplfrFMReadLogP12SQLPLFR_DBCBP21SQLPLFR_REQ_SCAN_NEXTP17SQ
LPLFR_SCAN_DATA + 0x3E6
  [4] 0x000072C25400A896
_Z17sqlplfrDoScanNextP12SQLPLFR_DBCBP11SQLPLFR_REQ + 0x426
  [5] 0x000072C25400F2D8 _Z10sqlplfrEduP9sqpLfrEdu + 0x848
  [6] 0x000072C2541A1B57 _ZN9sqpLfrEdu6RunEDUEv + 0x27
  [7] 0x000072C255ABE734 _ZN9sqzEDUObj9EDUDriverEv + 0x1A4
  [8] 0x000072C253D60599 sqloEDUEntry + 0x2A9
  [9] 0x000072C25A8C3EA5 /lib64/libpthread.so.0 + 0x7EA5
  [10] 0x000072C2481F29FD clone + 0x6D

>

2021-09-13-15.02.26.123456-240                       LEVEL:
Warning
PID     : 1111                 TID : 111111111111112 PROC :
db2sysc 0
INSTANCE: myinst1              NODE : 000            DB   : MYDB
HOSTNAME: myhost1
EDUID   : 61                   EDUNAME: db2lfr.0 (MYDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog,
probe:5120
DATA #1 : 
LFR Scan Num            = 16592118
LFR Scan Caller's EDUID = 583
Return code for LFR opening file S0012345.LOG was -2112880618

>

2021-09-13-15.02.28.123456-240                       LEVEL: Info
PID     : 1111                 TID : 111111111111111 PROC :
db2sysc 0
INSTANCE: myinst1              NODE : 000            DB   : MYDB
HOSTNAME: myhost1
EDUID   : 60                   EDUNAME: db2logmgr (MYDB) 0
FUNCTION: DB2 UDB, data protection services,
sqpLogMgrEdu::sqlpgRetrieveLogFile, probe:4148
DATA #1 : 
Completed retrieve for log file S0012345.LOG on chain 9 to
/myarchive/NODE0000/LOGSTREAM0000/LOGSTREAM0000/.  The newly
retrieved log will be verified.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply Db2 Version 11.5.7.0                                   *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply Db2 Version 11.5.7.0                                   *
****************************************************************
Comment
Apply Db2 Version 11.5.7.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.09.2021
30.11.2021
22.04.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)