Kbase 19713: Binary Dump and Load will not replace pre-existing records
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
SYMPTOM(s):
Binary Dump and Load will not replace pre-existing records
Fix RECID <recid>, <file-name> already exists with <field value>. (1127)
SYSTEM ERROR: Index in for recid could not be deleted. (1422)
CAUSE:
These errors appear when you rebuild an index following a binary dump of a table into an existing table that contains data. No indication of a problem appears prior to the rebuild.
FIX:
Binary load does not update index entries when loading data.
It loads data in the same manner as a bulkload. You must perform an index rebuild if you want the indexes to be updated.
If you perform a binary load of a table into an existing table that contains data, it will not overwrite the current contents. Errors indicative of duplication do not appear until you perform the index rebuild.
You receive the error:
Fix RECID recid, file-name already exits with field-name value (1127)
Refer to Progress Solution 12760 "How to Eliminate Duplicate Keys or Records in an Index".