Kbase P139716: Getting error Binary load failed (6255) and error creating record with error comment -1223.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/01/2009 |
|
Status: Unverified
SYMPTOM(s):
Getting error Binary load failed with error -1223.
Error creating record 8919334, error -1223.
Binary Load failed. (6255)
FACT(s) (Environment):
Table was binary dumped without error.
Dbtool finds no errors in the records of the table.
Index check finds no errors in the indices of the table.
The table does not use clobs.
Original table number the record data was dumped from is 84.
New table number the record data is being loaded into is 208.
Record size reported with the 4GL / ABL function record-length is 32000.
Creation of a new database with only this table allows binary data to be loaded without error.
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
Progress 8.x
CAUSE:
Bug # OE00179620
CAUSE:
The record has reached its non-Clob limit of 32000. When attempting to load this table into the database into a new table, the table number is imprinted into the record in the database. If the table number is 128 or less it only requires one byte to record the table number.
The record data is 31999 bytes.
The old table number required 1 byte.
The new table number, 208, requires 2 bytes and is not able to be written by the binary load as it exceeds the 32000 byte record size limit of a non-Clob record.
FIX:
Two workarounds exist:
1) Recreate the database and load the definition of this table earlier so the table number assigned is less than or equal to 128.
2) Decrease the size of the record to 31998 to allow the two byte table number to be stored correctly during the binary load.