Kbase 21750: Error (6182) During Data Load Using SQL & ODBC DataServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/8/2002 |
|
SUMMARY:
During the load of data files (.d) in the ODBC DataServer or SQL Server DataServer using the Data Administration tool, the load might terminate with the following error in the .e file:
>> ERROR READING LINE #2 (Offset=174): "You tried to compare or to update a character field with a value longer than the maximum length. (6182)
>> ERROR READING LINE #2 (Offset=174): Field num: 3, value: Urpon Frisbee. (2651)
>> ERROR READING LINE #2 (Offset=174): ** Unable to update Customer Field. (142)
** Tolerable load error rate is: 0%.
** Loading table Customer is stopped after 1 error(s).
NOTE: The sports2000.customer table was used to reproduce the error example above.
EXPLANATION:
Error (6182) appeared when the data was being loaded using the "Load Data and Definition" utility in the Progress Data Administration screen. It can appear with the SQL Server DataServer or ODBC DataServer and a minimum of 4GL Development license installed in the system.
By design, Progress allows users to insert more data than the format of a field in a table. When you load the Progress table definitions (.df) in the foreign database, the foreign database takes the Progress field's format as the length of that corresponding field. Thus, if you have more data in a field than its format in the Progress database, and you try to dump the data from that Progress database and load the .d into the foreign database, the data load terminates with error 6182.
SOLUTION:
Follow the steps to fix the problem:
1) Use the foreign database utility to change the field length.
2) Go to the DataServer for the appropriate database and choose
"Update/Add Table Definitions".
3) Supply the user name and password in the "User ID and password"
screen.
4) Enter the table name you just modified in the "Object Name" input
text box on the Pre-Selection Criteria for Schema Pull screen.
This should bring up that table.
5) Double click on the table to select it. You should see a star
before the table name if the table was selected. Click OK to
submit the updates.
6) Using the foreign database query tool, delete the data that may
have loaded in the modified table. If you do not delete the data,
you might get the duplicate record error in the unique index.
7) Now you can load the .d successfully.
When you open the Progress Data Dictionary, you might not see the change in the field format. If you want to keep the existing field format, you can leave it as it was, or you can change the field format to have the same length as in the foreign database.