Kbase P13453: Errors 2765 and 2766 during index rebuild.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
Errors during idxbuild or idxfix
Large word-indexed text fields require a larger stack. (2765)
Out of stack space! Increase PROGRESS stack -s. (2766)
Data was loaded via proutil -C bulkload.
CAUSE:
The bulkloader utility does not perform any check on the indexed character fields when loading data.
Therefore it's possible, for example, to load a 256-character string into the Name field of a customer record. Bulkload will not complain about it.
Then, once the indexes are rebuild with idxbuild or fixed with idxfix errors 2765 and 2766 will pop up.
Please note that, even though error 2765 refers to word-indexes, the affected index may well not be a word-index.
Also, because Progress 4GL does check that the indexed fields are not too long, this problem usually happens only when the .d file was generated with a non-Progress application (for example during a migration from a non-Progress database), or generated by a table with different index definitions, or if the .d has been manipulated or hand-edited.
FIX:
You need to identify the offending table, for which unfortunately the error messages do not help (they don't point to the index giving the problem).
Then, you need to access the records of that table via another of the active indexes and make sure that all the indexed fields are within the Progress limits.