Kbase P124452: Error 132 on a database record even though there is no duplicate record.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
SYMPTOM(s):
Application errors out with error 132:
** <file-name> already exists with <field/value...>. (132)
The table mentioned in error 132 is a database table.
There is actually no duplicate record with the same key values in the database.
Application uses BUFFER-COPY on a TEMP-TABLE some time before the 132 error appears.
TEMP-TABLE has been defined with a BEFORE-TABLE
TEMP-TABLE has no indexes defined.
TEMP-TABLE is part of ProDataSet
The TEMP-TABLE's TRACKING-CHANGES attribute is set to TRUE before the BUFFER-COPY takes place.
CAUSE:
This is a known issue.
Performing a BUFFER-COPY on a TEMP-TABLE with a BEFORE-TABLE defined, no indexes, and whose TRACKING-CHANGES attribute is set to TRUE, causes some memory not to be cleaned up properly.
Following table operations, even on database tables, may yield unpredictable results, such as generating error 132 while there actually is no duplicate record in the database.
FIX:
All four conditions are required for this problem to appear:
- BUFFER-COPY
- BEFORE-TABLE defined
- TEMP-TABLE with no indexes
- TRACKING-CHANGES set to TRUE.
Removing any of these conditions will work around the problem. Usually, the easiest workaround is to add at least one index to the TEMP-TABLE.