Consultor Eletrônico

SUMMARY:

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.

** Invalid character in numeric input <character>. (76)

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.

EXPLANATION:

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 you've opened the Progress .d file 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
mismatch of the data with the corresponding fields in the table, and
the data load is terminated with the above error message.

Additional details, as seen in the example above, reveal that only 10 out of 83 records were loaded into the database. So you know the first 10 records are in the database. Therefore, next time you load the data into the database, for example into the same table, you either delete the existing records in the database, or delete the rows of data that were loaded from the .d file. If you did not delete 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 Progress database:

>> ERROR READING LINE #1 (Offset=0): ** Customer already exists
with Cust Num 1. (132)
** 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.

With the DataServer, SQL Server or ODBC:

>> ERROR READING LINE #1 (Offset=0): 23000: [Microsoft][ODBC SQL
Server Driver][SQL Server]Cannot insert duplicate key row in object
'customer' with unique index 'customer##custnum'.
>> ERROR READING LINE #1 (Offset=0): 01000: [Microsoft][ODBC SQL
Server Driver][SQL Server]The statement has been terminated.
>> ERROR READING LINE #1 (Offset=0): Duplicate unique key in
database table. (1443)
** 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.

With the ORACLE DataServer:

>> ERROR READING LINE #1 (Offset=0): ** unique constraint
(MAKBAR.CUSTOMER##CUSTNUM) violated
** 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.

With the Progress/400 DataServer:

>> ERROR READING LINE #1 (Offset=0): Customer already exists with
this unique index value. (2471)
** 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.


SOLUTION:

There are several options to fix this issue:

-- First Option:

1) Delete the existing data in the database.

2) Open the .d file with WordPad, Notepad or any editor that does
not format or wrap long lines, and align the data row in a correct
fashion.

3) Load the data again.


-- Second option:

1) Delete the rows of the partially loaded data in the corresponding
.d file.

2) Load the rest of the data.


-- Third option:

1) Delete the existing data in the database.

2) Re-dump the data, and load the data again.