|
Problem IC84313
|
Status: Closed |
A PAGE CORRUPTION WHICH WAS DETECTED BY A DB2 PREFETCHER SHOULD CREATE FODC DIRECTORY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If a page corruption is first detected by a DB2 prefetcher we
should create the FODC directory and call the
db2cos_datacorruption call out script.
Currently only the call out script is being called by the
prefetcher edu, but no FODC package is setup so that all data is
dumped just under DIAGPATH directory. Only when DB2 attempts to
re-read the bad page via a different code path via an db2agent
edu,
then we create the FODC directory under
<DIAGPATH>/FODC_BadPage_<date>.
This behavior is inconsistent and need to be changed. We should
create the directory in all cases. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 FP1 or subsequent fix pack. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem First Fixed in DB2 10.1 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
05.02.2013
05.02.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
