Kbase P185263: Character field decimal property causing error: Table CRCs do not match. Cannot load data into this
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  4/12/2011 |
|
Status: Verified
SYMPTOM(s):
Table CRCs do not match. Cannot load data into this table. (6713)
Binary Load failed. (6255)
Error loading data into database
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CHANGE:
Progress 9 database converted to OpenEdge 10.
CAUSE:
Character field unexpectedly has a decimal value. The decimal value was from the Length definition when the field was loaded.
ADD FIELD "FieldName" OF "Tablename" AS character
DESCRIPTION "Date after which to schedule the reset date"
FORMAT "X(8)"
INITIAL ""
POSITION 9
MAX-WIDTH 16
LENGTH 8 <---causes decimal value to be set for Character field.
ORDER 82
Dumping the field in OpenEdge 10 dumps and loads the Decimal value as "Length". Progress 9 does not dump the Length value. It defaults to "?"
FIX:
Remove the decimal definition of the field by running 4GL code to replace the decimal value with ?
Even though the binary load said it failed the data was loaded and after running the code below and building the indices involved,
all records from the binary load should be activated.
/* Fix Decimals */
for each _file
no-lock
where _file._file-num >= 0
and _file._file-num <= 32767:
for each _field of _file
exclusive-lock
where _field._decimals <> ?
and _field._decimals <> 0
and _field._data-type <> "decimal":
_field._decimals = ?.
end.
end.
Problem was caused by unexpected changes to the v9 database