Kbase P25005: Error '** already exists with . (132)' is generated multiple times when used with NO-UNDO TEMP-TABL
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/17/2009 |
|
Status: Verified
SYMPTOM(s):
Multiple '** <file-name> already exists with <field/value...>. (132)' generated.
Multiple records created with exactly the same Primary Unique Index
TEMP-TABLE defined NO-UNDO option and PRIMARY UNIQUE INDEX.
FACT(s) (Environment):
Progress 8.x
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
This is expected behavior.
For technical reasons the record cannot be undone unless the temp-table is undoable and the creates take place within separate transactions.
Because they are not undone, the error 132 will keep occurring.
FIX:
1. Remove the NO-UNDO option from TEMP-TABLE definition and enclose the CREATE / ASSIGN statements in transaction blocks.
or
2. Check if a record already exists with the unique key values before creating the new records.