Kbase P51240: Getting error (132) even though record is unique as per the Unique Index.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/02/2010 |
|
Status: Verified
SYMPTOM(s):
Getting error (132) even though record is unique as per the Unique Index.
** <tablename> already exists with <value>. (132)
An index rebuild completes successfully but doesn't resolve the problem.
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
Workaround:
1. Create a new field the same as the field that is causing the problems.
2. For each record, copy the data from the old field to the new field.
3. Delete the unique index.
4. Delete the old field causing the problems.
5. Rename the new field to be the same as the old field name.
6. Recreate the Unique Index and rebuild it.