DB2 - Problem description
Problem IT33596 | Status: Closed |
ROLLFORWARD WITH NORETRIEVE OPTION STILL TRIGGERED LOG RETRIEVALFROM ARCHIVE AND CAUSED SQL1273N ERROR | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
This problem only occurs on database using infinite active log configuration, i.e. the LOGSECOND database configuration parameter is set to -1. When ROLLFORWARD DATABASE command with NORETRIEVE option is used, the following error is returned: SQL1273N An operation reading the logs on database "TEST" cannot continue because of a missing log file "S00XXXXX.LOG" on database partition "X" and log stream "X". From db2diag.log, we can see this ROLLFORWARD still retrieved some log file from archive, not respecting the NORETRIEVE option on the ROLLFORWARD. This incorrect retrieve is also leading to additional complications that eventually caused the SQL1273 error. 2020-06-26-06.36.02.132832+480 E139552E712 LEVEL: Info PID : 40073 TID : 140727300384512 PROC : db2sysc 0 INSTANCE: Instance1 NODE : 000 DB : TEST HOSTNAME: HOST1 EDUID : 4363 EDUNAME: db2logmgr (TEST) 0 FUNCTION: DB2 UDB, data protection services, sqpLogMgrEdu::sqlpgRetrieveLogFile, probe:4149 MESSAGE : ADM1845I Completed retrieve for log file "S0012345.LOG" on chain "X" from ".../Instance1/TEST/NODE0000/LOGSTREAM0000/C0000738/" to ".../overflowLogs/NODE0000/LOGSTREAM0000/LOGSTREAM0000/". 2020-06-26-06.36.12.743455+480 I3235016E555 LEVEL: Info PID : 40073 TID : 47016289756928 PROC : db2sysc 0 INSTANCE: Instance1 NODE : 000 DB : TEST HOSTNAME: HOST1 EDUID : 3893 EDUNAME: db2loggr (TEST) 0 FUNCTION: DB2 UDB, data protection services, sqlpgOpenLogExtent, probe:10000 MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." DIA8411C A file "" could not be found. DATA #1 : Error opening database log extent 3116503282. 2020-06-26-06.36.12.743737+480 I3235572E460 LEVEL: Warning PID : 40073 TID : 47016289756928 PROC : db2sysc 0 INSTANCE: Instance1 NODE : 000 DB : TEST HOSTNAME: HOST1 EDUID : 3893 EDUNAME: db2loggr (TEST) 0 FUNCTION: DB2 UDB, data protection services, sqlpgSwitchProcessAllLogStreams, probe:1840 DATA #1 : Retrieving log extent 3116503282 for log stream 0 2020-06-26-06.36.12.941161+480 I3236033E724 LEVEL: Info PID : 40073 TID : 46932005218048 PROC : db2sysc 0 INSTANCE: Instance1 NODE : 000 DB : TEST HOSTNAME: HOST1 EDUID : 3892 EDUNAME: db2logmgr (TEST) 0 FUNCTION: DB2 UDB, data protection services, sqpLogMgrEdu::sqlpgRetrieveLogFile, probe:4599 MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." DIA8411C A file "" could not be found. DATA #1 : String, 51 bytes INFINITE LOGGING: rfwdHeadChainId < rfwdLogChainId. DATA #2 : String, 39 bytes Attempt to search from the lower chain. DATA #3 : unsigned integer, 4 bytes 3 DATA #4 : unsigned integer, 4 bytes 755 2020-06-26-06.36.13.997050+480 E3239703E587 LEVEL: Error PID : 40073 TID : 47016289756928 PROC : db2sysc 0 INSTANCE: Instance1 NODE : 000 DB : TEST HOSTNAME: HOST1 EDUID : 3893 EDUNAME: db2loggr (TEST) 0 FUNCTION: DB2 UDB, data protection services, sqlpgSwitchProcessAllLogStreams, probe:1861 MESSAGE : ADM1601E A recovery or rollforward operation on database "TEST" cannot continue because of a missing log file "S6503282.LOG" on database partition "0" and log stream "0". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 for LUW V11.1 Mod4 Fixpack6 or later. * **************************************************************** | |
Local Fix: | |
Do not use infinite active log configuration, i.e. change the LOGSECOND database configuration parameter to a value that is not -1. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.07.2020 21.03.2021 21.03.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |