Kbase 17990: SYSTEM ERROR: kmkinit -- idx not found. (131)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/1/1998 |
|
SYSTEM ERROR: kmkinit -- idx not found. (131)
This error typically shows up when changed indexes are being updated.
Index keys are being checked for validity and created if needed
throughout this process. We are checking for the type of update being
peformed, such as SQL for example, and making the necessary changes
to the index. (creates, updates, deletes etc.)
When we get to the stage when we are adding a new index entry, we are
scanning through all of the records validating all the keys. If we
encounter a duplicate key at this point, an error message will be sent
out and the index would have to be repaired, preferably with idxfix.
If we don't have a problem with the index key validation process, we
then assign an initialized status to the index. This is the point
where we can see the SYSTEM ERROR: kmkinit -- idx not found. (131).
Before kmkinit can assign a status to the index,we must go through the
index manager to find the index. If we don't find it, then we see the
error.
It seems strange that we are in the process of validating components
of the index, yet when it is time to assign a status to the index we
cannot find it. If this sounds like index corruption to you, then you
are heading in the right direction. In most cases, and index rebuild
should eliminate this error and has been very effective in doing so.
A potential cause of the problem may be an error process of modifying,
creating , or deleting an index. However, the proutil -C idxbuild
should get you around the problem.If not, then test indices could be
run, and that would take significantly longer.
SDA 6/1/98