|
Problem IC80429
|
Status: Closed |
HISTORY FILE CORRUPTION MAY OCCUR WHEN THE FILESYSTEM THAT THE HISTORY FILE RESIDES ON BECOMES 100% FULL |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
History file corruption may occur when filesystem where the
history file resides becomes full
Will see errors similar to the following
2011-06-09-02.50.16.456580-240 I7140950E671 LEVEL: Error
PID : 19688 TID : 199455926624 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-14180 APPID:
LOCAL.db2inst1.198AA9065013
AUTHID : DB2INST1
EDUID : 10724 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, database utilities, sqluhBeginBatch,
probe:1981
MESSAGE : SQL2161N A damaged recovery history file could not be
fixed.
The specified action failed.
DATA #1 : String, 32 bytes
Error while opening history file
DATA #2 : String, 58 bytes
/home/db2inst1/db2inst1/NODE0000/SQL00002 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 Fix pack 6 *
**************************************************************** |
| Local Fix: |
renamed the file db2rhist.asc |
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 6. |
| Workaround |
Renamed the file db2rhist.asc |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.12.2011
14.04.2014
14.04.2014 |
| 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
|
 |
