DB2 - Problem description
Problem IC66506 | Status: Closed |
RARE CONDITION MAY LEAD TO ROLLFORWARD / CRASH RECOVERY PARALLEL FAILURE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
During parallel recovery, a rare timing condition may cause some internal data to be cleaned up before the other process tries to read it. This could cause a logical assertion to fail during recovery and the instance to be abend. The internal data being prematurely cleaned up is called the object descriptor. In a customer build the problem will fail in function sqlbfix, probe 5 with the following message in the db2diag.log: "fixCB::pageKey and fixCB::obj do not match" Note again this issue only occurs during recovery. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * A timing condition exists in parallel recovery when * * processing the GET_ONE_EXT, FMT_EMP and OBJ_ADD_EXT. The * * problem is one recovery agent could be processing one of * * these log records and initialize an internal memory * * structure that is required by other agents. The result is * * failure in parallel recovery with a error message in the * * db2diag.log: * * * * fixCB::pageKey and fixCB::obj do not match * **************************************************************** * RECOMMENDATION: * * Upgrade to v97 fp3 * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
This will be fixed in v97 fp 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.02.2010 16.09.2010 16.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |