Kbase P112751: idxbuild error 1127 reporting incorrect field value
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/26/2009 |
|
Status: Verified
SYMPTOM(s):
idxbuild error 1127 reporting incorrect field value
Fix RECID <recid>, <file-name> already exists with <field value>. (1127)
FACT(s) (Environment):
Progress 9.1D
Progress 9.1E
OpenEdge 10.0B
OpenEdge 10.1x
OpenEdge 10.2x
All Supported Operating Systems
CAUSE:
This is a known issue being investigated by Development.
There are duplicate records on unique index keys, but the filed value entires are not those associated with the unique index, but the field values of another index. This does not mean that there is/was not corruption, it's just that the 1127 message is reporting the wrong information
CAUSE:
Bug# OE00126014
FIX:
When unique indexes are inactive, there is nothing preventing Progress from adding duplicates. This situation can arise from binary loading table entries more than once or during database processing when unique indexes are de-activated. The idxbuild utility used to re-create indexes (including de-activated one's unless otherwise specified) will then find these unique and report on these unique entry issues and subsequently, not build the index on those entries.
This Solution is merely highlighting the fact that the field values reported in the 1127 error are incorrect. The 1127 message is correctly reported and corrective actions are to eliminate the duplicate record entries, or to review the key value entries of the unique index.
In order to discover in which index the problem actually lies, run proutil -C idxcheck to check the indexes of the table error 1127 refers to.