DB2 - Problem description
Problem IC74472 | Status: Closed |
CTE0310 INDEX UPDATE IS NOT ALLOWED DUE TO INSUFFICIENT DISK SPACE. DOES NOT PROVIDE ENOUGH INFORMATION. | |
product: | |
DB2 NET SEARCH / 5765F3800 / 950 - DB2 | |
Problem description: | |
Customers have many text indexes , some with more that 800. The error message "CTE0310 Index update is not allowed due to insufficient disk space." does not provide enough information to allow the customer or IBM Support to determine the cause of the problem and to reslove the problem. The CTE0310 message should be correct in the following manner. 1) Identify the index by name or put the message into the index event log table. 2) Provide the amount of disk space needed and the amount avalible. Correcting the above 2 issuse will allow customer and l2 support make the filesystem or alter index changes to correct the issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using the update text index operation * **************************************************************** * PROBLEM DESCRIPTION: * * The error message "CTE0310 Index update is not allowed due * * to * * insufficient disk space." does not provide enough * * information * * to allow the customer or IBM Support to determine the cause * * of * * the problem and to resolve the problem. * **************************************************************** * RECOMMENDATION: * * Upgrade to v97fp5 * **************************************************************** CTE0310 needs to be updated to provide details of index space needed for index updation. | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to v97fp5 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC77630 IC77644 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.02.2011 05.04.2012 05.04.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.9 |