DB2 - Problem description
Problem IC80173 | Status: Closed |
CERTAIN TRANSACTION LOG RECORDS ARE BLOCKING WHEN BEING APPLIED DURING REPLY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Transaction Log Records are replayed on the database in parallel. Some actions however, need to be replayed in a serial mode in order to preserve a particular sequence of events. Such log records or events are called blocking log records. The problem in this APAR is that DB2 is blocking some log records that it does not need to except for an HADR environment with Read ON Standy (ROS) enabled. This has an impact on log replay performance during Rollforward, Crash recovery, or on a non-ROS HADR Standby as parallel processing has to be suspended until these log records are replayed in a serial way. The log records affected are related to Index maintenance and the impact on replay performance is related to the frequency of these log records. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.7 Fixpack 6 or Higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Fixed in v9.7 Fixpack 6 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84471 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.12.2011 17.07.2012 23.07.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |