Kbase P9390: Table content is not loaded due to error 132 about duplicated records
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/08/2003 |
|
Status: Unverified
SYMPTOM(s):
Table content is not loaded due to error 132 about duplicated records
Error 132 when dumping a table about record already exists with that primary key
** <file-name> already exists with <field/value...>. (132)
ERROR READING LINE #1 (Offset=0): ** Customer already exists with CustNum 1. (132)
** Tolerable load error rate is: 0%.
** Loading table Customer is stopped after 1 error(s).
ERROR! Trailer indicated 1119 records, but 0 records were loaded.
CAUSE:
This is an expected behaviour. If a record on the table exists with same primary key than the record that is being loaded in the same table this error appears and if the Acceptable error percentage is set to 0 the load process is aborted.
FIX:
Two options:
1) To keep the old values of the records already in the table with same primary key than the ones are being loaded then the "Acceptable error percentage" option should be increased to, i.e., 100% in the "Load Data Contents for Table <table_name>" window that appears after the table to load has been chosen.
2) To load the new values of the records with same primary key than the old records already in the DB, it is necessary to delete these old records before. This can be done through 4GL (with delete record).