|
Problem IC60214
|
Status: Closed |
IF FILESYSTEM RUNS OUT OF SPACE DURING INDEX REWRITE THE TEXT INDEX BECOMES CORRUPT. |
| product: |
DB2 NET SEARCH / 5765F3802 / 910 - DB2 |
| Problem description: |
During text index rewrite operation if the filesystem
runs out of space , the text index becomes corrupt. NSE does
not check to see if filesystem has enough space to complete
index rewrite operation. |
| Problem Summary: |
PROBLEM DESCRIPTION:
During text index rewrite operation if the filesystem runs
out of space , the text index becomes corrupt. NSE does not
check to see if filesystem has enough space to complete
index rewrite operation. |
| Local Fix: |
Put text index files in thier own filesystem and monitor
freespace. |
| available fix packs: |
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
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 |
To avoid index corruption due to insufficient disk space, the
new fix introduces a check for available disk space each time an
update index is issued. If the available disk space is less than
the required estimation then a message is displayed and the
index update is terminated. The fix is applicable only for a
single update and multiple index updates is not considered. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.03.2009
27.10.2009
27.10.2009 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.8
|
 |
