DB2 - Problem description
Problem IT41626 | Status: Closed |
CRASH RECOVERY AFTER A DATABASE ROLLFORWARD TO POINT IN TIME THAT INCLUDES AN INDOUBT TRANSACTION FAILS WITH SQL1265 (ADM1532E) | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
This problem may be encountered after a rollforward to point in time, where an indoubt transaction exists at the end of the rollforward. After the rollforward, since the database contains an unresolved indoubt, a crash recovery is required. This crash recovery may fail with SQL1265 (ADM1532E). You may also see a similar message in the db2diag.log: 2022-07-09-06.28.43.881191-240 I21516074A664 LEVEL: Error PID : 39977320 TID : 69882 PROC : db2sysc 0 INSTANCE: instance NODE : 000 DB : DBNAME APPHDL : 0-6214 APPID: *N0.aaaa.220710041638 AUTHID : AAAAA HOSTNAME: hostname EDUID : 69882 EDUNAME: db2agent (DBNAME) 0 FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:640 MESSAGE : ZRC=0x86100017=-2045771753=SQLPR_BAD_VER_LOG_EXT "Log extent file is the incorrect version" DIA8424C An incorrect version of a log file was encountered. DATA #1 : Codepath, 8 bytes 1:2:3:11:28:29:37:38:39 FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::RecoverDatabase, probe:20300 MESSAGE : ADM1532E Crash recovery has failed with SQLCODE "-1265". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest modification/fix pack. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest modification/fix pack. * **************************************************************** | |
Comment | |
Problem was first fixed in Db2 11.5.8.0. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.07.2022 19.08.2022 09.09.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |