Online backup include logs might fail with ADM8010E with the
reason "Log could not be retrieved".
This problem only exists in version 11.5.6 and 11.5.7.
The problem is more likely to occur with high BACKUP
parallelism.
The db2diag.log messages can be found leading to the failure:
2022-03-29-06.18.59.415880+000 I46943A522 LEVEL: Error
PID : 11797134 TID : 20320 PROC :
db2sysc 0
INSTANCE: myinst NODE : 000 DB : MYDB
HOSTNAME: myhost11
EDUID : 20320 EDUNAME: db2lfr.0 (MYDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrOpenExtentRetrieve,
probe:205
MESSAGE : ZRC=0x82100016=-2112880618=SQLP_RC_RETRIEVE_FAILED
"Log could not be retrieved"
DATA #1 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
1666758
2022-03-29-06.19.00.722001+000 I49387A501 LEVEL:
Warning
PID : 11797134 TID : 20320 PROC :
db2sysc 0
INSTANCE: myinst NODE : 000 DB : MYDB
HOSTNAME: myhost11
EDUID : 20320 EDUNAME: db2lfr.0 (MYDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog,
probe:5120
DATA #1 :
LFR Scan Num = 42296321
LFR Scan Caller's EDUID = 102762
Return code for LFR opening file S1666758.LOG was -2112880618
2022-03-29-06.19.00.724154+000 E51251A604 LEVEL:
Severe
PID : 11797134 TID : 102762 PROC :
db2sysc 0
INSTANCE: myinst NODE : 000 DB : MYDB
APPHDL : 0-27191 APPID: *LOCAL.myauth.220329020054
AUTHID : MYAUTH HOSTNAME: myhost11
EDUID : 102762 EDUNAME: db2bm.121045.3 (MYDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent,
probe:2620
MESSAGE : ADM8010E Backup was unable to copy requested log file
"S1666758.LOG"
for inclusion in the backup image. The backup has been
aborted.
This problem can also affect HADR primary database, when it
needs to retrieve a log file from archive during remote catchup.
It can result in the HADR primary closing the connection with
the HADR standby due to not able to find the log file it needs
from archive. The following is an example of the messages from
db2diag.log:
2022-09-10-09.31.46.799431-300 I1191754849A674 LEVEL: Error
PID : 57606564 TID : 48886 PROC :
db2sysc 0
INSTANCE: myinst1 NODE : 000 DB : MYDB
HOSTNAME: myhost1
EDUID : 48886 EDUNAME: db2lfr.0 (CMSDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrDoScanNext,
probe:1001
MESSAGE : ZRC=0x8010019D=-2146434659=SQLP_LOG_NOT_IN_ARCHIVE
"Log extent not found in archive."
DATA #1 : String, 21 bytes
Hit EOL for LFR scan.
DATA #2 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes
LFR Scan Num = 453
LFR Scan Caller's EDUID = 77671
DATA #3 : Hex integer, 8 bytes
0x0000000205040020
2022-09-10-09.31.46.800090-300 I1191755524A625 LEVEL: Error
PID : 57606564 TID : 77671 PROC :
db2sysc 0
INSTANCE: myinst1 NODE : 000 DB : MYDB
HOSTNAME: myhost1
EDUID : 77671 EDUNAME: db2hadrp.0.3 (CMSDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrEdu::hdrEduP, probe:20591
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
DATA #1 :
HADR primary database failed to read log pages for remote
catchup. sqlplfrScanNext scanPages = 0, scanFlagsOut = 0x2
2022-09-10-09.31.46.800659-300 E1191756150A458 LEVEL: Event
PID : 57606564 TID : 77671 PROC :
db2sysc 0
INSTANCE: myinst1 NODE : 000 DB : MYDB
HOSTNAME: myhost1
EDUID : 77671 EDUNAME: db2hadrp.0.3 (CMSDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSetHdrState, probe:10000
CHANGE : HADR state set to HDR_P_REM_CATCHUP_PENDING (was
HDR_P_REM_CATCHUP), connId=151 |
