Kbase P11477: ASCII Load from the .d files fails with (76)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/12/2008 |
|
Status: Verified
SYMPTOM(s):
ASCII Load from the .d files fails with (76) question marks "?" in character field
Load from the .d files fails with (76) characters listed in character field
** Invalid character in numeric input <character>. (76)
** Invalid character in numeric input ?. (76)
** Invalid character in numeric input A. (76)
Acceptable Error Percentage is 0
FACT(s) (Environment):
All Supported Operating Systems
Products / Versions
CAUSE:
During the load of data files (.d) using the Data Administration tool, the load might terminate with error (76). The error appears in the Progress generated error file (table_name.e) in the working directory.
Where the <character> is a first character in the trailing broken line.
This shows the error duplicated while using the customer table in the sports2000 database:
>> ERROR READING LINE #11 (Offset=1538): ** Invalid character in numeric input F. (76)
** Tolerable load error rate is: 0%.
** Loading table Customer is stopped after 1 error(s).
>> ERROR! Trailer indicated 83 records, but 10 records were loaded.
This error appears in the corresponding error file, in this case customer.e. Progress generates this file when there is an error during the data load into a table.
If the Progress .d file has previously been opened with an editor that formats or wraps long lines or you've compressed the .d files with a WinZip application, a single row of data might be broken into several lines in that file. Therefore, the .d file becomes corrupted. This causes a mismatch of the data with the corresponding fields in the table, and the data load is terminated with the above error message (76).
FIX:
Ascertain the importance of the table and verify how many of the records are actually corrupt by setting "Acceptable Error Percentage" to 100 and re-running the load. The resulting table_name.e will tell you how many records out of the total were loaded.
If this is unacceptable:
1) Delete the existing data in the database.
2) Re-dump the table, if this is not an option, open the errant .d file with WordPad, Notepad or any editor that does not format or wrap long lines, and re-align the data row in a correct fashion.
ie: Find the offset in the .d file and correct the entry.
3) Load the data again.