Kbase P125078: Loading a binary dump file generates error 6713 when df doesn't include POSITION
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/03/2009 |
|
Status: Verified
SYMPTOM(s):
Loading a binary dump file generates error 6713 when df doesn't include POSITION
The df file used to create the target database does not include field POSITIONs.
Table CRCs do not match. Cannot load data into this table. (6713)
Binary Load failed. (6255)
FACT(s) (Environment):
When dumping the definitions file (.df), the option to include POSITION for .r compatibility was deselected.
All Supported Operating Systems
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
OpenEdge Database Category: Maintenance
OpenEdge Database Category: Configuration
CAUSE:
The binary load process requires that the CRC of the binary file matches that of the table within the database.
When dumping the df file, deselecting the "Include POSITION for .r Compatibility" will cause the df to not include field positions, and when loaded, the field positions of each table may be different to what the binary load file expects.
e.g. The original database may have fields A, B, ,D. Field C is missing because it had been deleted. So the three fields have positions 1,2,4. If you binary dump that table, when reloading it will expect those fields to be in that order.
However if the option to include POSITION was deselected when dumping the df, when you load that df file the field positions will now be 1,2,3 not 1,2,4 and the binary load will fail.
CAUSE:
Bug# OE00154917
FIX:
Upgrade to 10.1C or later.
Workaround:
1. Dump the definitions (.df) file again from the original database and ensure that the option to include POSITION for .r compatibility is selected.
2. Load the df file into an empty database.
3. Load the binary dump file.