DB2 - Problem description
Problem IC88046 | Status: Closed |
TRANSACTION START TIMESTAMP IS NOT UPDATED WHEN APPLINFO LOG RECORD IS WRITTEN USING CURRENT VALUE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The IBM DB2 Recovery Expert for Linux, UNIX, and Windows product utilizes the APPLINFO log record when reporting on transactions in the Log Analysis feature. The APPLINFO log record is used to obtain the transaction start timestamp. It has been determined that the transaction start timestamp is not updated when the APPLINFO log record is written and the current value is used. This causes inaccuracies in the reporting of the transaction start timestamp and Quiet Time reporting. For example, if a connection commits a transaction and then after a period of time passes a new transaction is started the start timestamp recorded in the APPLINFO log record will be the timestamp of the last commit and not the current timestamp when the new transaction started. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 8 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 8 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.11.2012 28.08.2013 28.08.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |