Kbase P9038: SE: No blocks on free chain number. (759) after adding data extent
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/02/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1C
All Supported Operating Systems
SYMPTOM(s):
SYSTEM ERROR: No blocks on free chain number 2. (759)
SYSTEM ERROR: No blocks on free chain number <number>. (759)
SYSTEM ERROR: Incomplete microtransaction. (2255)
Problem occurred after adding a new data extent
CAUSE:
The condition here is that the master block reports that there are blocks on the free chain, but the pointer to the head of the free chain is zero. This is a fatal error.
FIX:
Seems to occur in every case after the user has run out of disk space.
The easiest way to reset the free chain is to run the index rebuild
- when it asks "build some or build all"
- choose SOME
Then for an index name type in "!".
This will scan the database and reset the pointers.
The previous workaround was to rebuild a small index.
Since the error in no way indicates index corruption, it will waste time to
start rebuilding indexes.
Simply reset the free chain in the instruction above.
Once that is complete, run the proutil -C chanalys and check the FREE CHAIN section .
It will tell you whether or not the free chain has been restored.
If it has not been restored, then this is a bug and we need to know about it
immediately since we are trying to track down the problem.
If the free chain has been restored correctly, then the customer can assume normal
processing.
This does not assume that they will never encounter the problem again, however
another out of disk space condition may lead to the same problem and resolution.