Consultor Eletrônico

Status: Verified

SYMPTOM(s):

Problems as a result of binary dump and load.

Fix RECID <recid>, <file-name> already exists with <field value>. (1127)

Table <name> is number <num> in dump file and <num> in schema. (6183)

The table numbers do not match, but the number of fields are the same

CAUSE:

A binary dump of a table dumps a table and fields based on the order in which they appear in the .df file. If you binary load a table into a database which has a different cycle redundancy check (CRC) due to order of fields, you might introduce logical corruption into the database.

In this example:

DB1 - Table = customer - Fields = A B C
DB2 - Table = customer - Fields = C A B

if you perform a binary dump of customer table from database 1 (DB1), the data is is in a specific order based on the order of the fields within that table. If you then attempt to load that data into database 2 (DB2), the data will load, however, when you rebuild an index, you might experience Error (1127):

Fix RECID <recid>, <file-name> already exists with <field value>. (1127)

This means you either:

- Loaded the table more than once. The dump does not use indices, therefore no checking is done on the load to see if data already exists

or,

- Loaded a binary dump table that has a different order of fields based on the original database versus the one you have just loaded into. Typically, you encounter this error when one of the fields is a unique index. Because you have now loaded the incorrect information into the incorrect fields due to the
ordering of those fields, the result is logical corruption.

FIX:

Use bulk load to work around the issue.