Kbase P11494: Load from the .d files fails with (5032) Oracle DataServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/22/2003 |
|
Status: Unverified
SYMPTOM(s):
Load from the .d files fails with (5032)
unique constraint violated (5032)
ORACLE DataServer
CAUSE:
During the load of data files (.d) using the Data Administration tool, the load might terminate with errors. These error appears in the Progress generated error file (table_name.e) in the working directory.
If a previous load had failed and (for example) revealed that only 10 out of 83 records were loaded into the database, the first 10 records ARE already in the database.
Therefore, next time that data is loaded into the database, for example into the same table, the existing records in the database either need to be deleted, or delete the rows of data that were loaded from the .d file already. By not deleteing the partially loaded data from the table or from the .d file, the data load will terminate with similar messages in the corresponding .e file:
With the ORACLE DataServer:
>> ERROR READING LINE #1 (Offset=0): ** unique constraint
(MAKBAR.CUSTOMER##CUSTNUM) violated (5032)
** Tolerable load error rate is: 0%.
** Loading table Customer is stopped after 1 error(s).
>> ERROR! Trailer indicated 83 records, but 0 records were loaded.
FIX:
To correct this scenario:
1) Delete the existing data in the database.
2) Re-dump the data, and load the data again.
or
1) Delete the rows of the partially loaded data in the corresponding
.d file.
2) Load the rest of the data.