DB2 - Problem description
Problem IC72470 | Status: Closed |
HISTORY FILE OPENED IN INCORRECT MODE MAY RESULT IN HISTORY FILE CORRUPTION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Due to the misuse of a confusing flag, when we open the history file we will be opening it incorrectly with NO_FLUSH_ON_CLOSE, which means do not flush the data to disk when closing the file handle. This can be a problem if the database server then crashed, causing the data in the file system cache to disappear and never make disk. The symptoms of the issue include history file corruption after a server crash. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * Potential history file corruption as data is not immediately * * flushed to disk. If database was abnormally shut down, * * history file data residing in the file system cache might be * * lost, resulting in history file missing information or * * corruption. * **************************************************************** * RECOMMENDATION: * * upgrade or remove the history file manually if it is * * corrupted * **************************************************************** | |
Local Fix: | |
In most cases the history file can repair itself from the secondary backup, if that is not possible, simply remove the history file in the database directory and a new one will be created automatically. However the data in the original history file will be lost. The result of loosing this history file information will include not being able to use the recovery command for lost backup entries, however recovery and rollforward would still be an option if applicable to the database. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
problem fixed in v97 fp4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.11.2010 29.04.2011 29.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |