Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

Progress 9.x
OpenEdge 10.x

SYMPTOM(s):

Binary load fails with error 6271 after database migration

The number of fields in the schema is <num>, expected <num>. (6271)

Binary dump performed on source database

Binary load performed on target database

Table schema for target database is different from source database

Fields have been renamed or deleted in new database

CAUSE:

A binary dump for a table can only be loaded into a database if the field order and data types match those from the database where the dump was performed.
This is because the dumped data is dumped using the original field order (and position markers) and does not include the table schema. Usually, the main issue is that the field order is different. This happens if the fields in the target database were not created in the same order as the fields in the original database, or if some fields were deleted in the original database prior to the dump. This issue prevents the data from being directly binary loaded into the records in the target database.

FIX:

Use an ASCII dump and the bulkload utility, as follows:
1. open Data Administration on the original database.
2. dump the table data to .d file(s).
3. create a Bulk loader definition file (.fd) for the tables that have been dumped.
4. for each field that has been renamed in the target database, edit the .fd file and modify the field name accordingly.
5. for each field that has been deleted in the target database, create a temporary field in the target database with the same name and data type as in the original database.
6. load the data using the command: proutil <db> -C bulkload <fdfile>
7. remove temporary fields created at step 5.