|
Problem IC71022
|
Status: Closed |
HISTORY FILE OPENED IN INCORRECT MODE MAY RESULT IN HISTORY FILE CORRUPTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - 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: *
* The history file is opened with the incorrect mode, causing *
* the data to be cached in the file system cache. If the *
* server crashes the changes in the file system cache will be *
* gone. *
****************************************************************
* RECOMMENDATION: *
* If the history file is corrupted after a server crash, *
* simply remove the history file and a new one will be *
* generated automatically, but the data in the original *
* history file will be lost. *
**************************************************************** |
| 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.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Fixed in v91 fp 10. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72470 IC73660
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.09.2010
10.06.2011
10.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
