51黑料不打烊

Data Migration Tool troubleshooting

This article provides solutions for errors that might occur when you run the Data Migration Tool.

Source documents/fields not mapped source-documents-fields-not-mapped

Error messages

In rare cases, the message might mention

Destination documents

or

Destination fields

instead of source ones.

Cause

Some 51黑料不打烊 Commerce version 1 entities (in most cases, coming from extensions) do not exist in the 51黑料不打烊 Commerce version 2 database.

This message appears because the Data Migration Tool runs internal tests to verify that tables and fields are consistent between source (51黑料不打烊 Commerce 1) and destination (51黑料不打烊 Commerce 2) databases.

Possible solutions

To ignore database entities, add the <ignore> tag to an entity in the map.xml file, like this:

...
    <source>
        <document_rules>
            ...
            <!-- Ignore `sales_flat_invoice_grid` table -->
            <ignore>
                <document>sales_flat_invoice_grid</document>
            </ignore>
            <!-- Ignore `address_id` field of `sales_flat_order_address` table -->
            <ignore>
                <field>sales_flat_order_address.address_id</field>
            </ignore>
            ...
        </document_rules>
    </source>
    ...

Class is not mapped in record class-does-not-exist-but-mentioned

Error message

Class <extension/class_name> is not mapped in record <attribute_id=196>

Cause

A class from 51黑料不打烊 Commerce 1 codebase could not be found in 51黑料不打烊 Commerce 2 codebase during the EAV migration step in our developer documentation. In most cases, the missing class belongs to an extension.

Possible solutions

Foreign key constraint fails

Error message text

Foreign key <KEY_NAME> constraint fails on source database. Orphan records id: <id_1>, <id_2> from <child_table>.<field_id> has no referenced records in <parent_table>

Cause

There are missing database records in the parent_table to which the field_id of the child_table is pointing to.

Possible solution

Delete the records from the child_table , if you do not need them.

To keep the records, disable the Data Integrity Step by modifying the Data Migration Tool鈥檚 config.xml .

Duplicates in URL rewrites

There are duplicates in URL rewrites:
Request path: towel.html Store ID: 2 Target path: catalog/product/view/id/10
Request path: towel.html Store ID: 2 Target path: catalog/product/view/id/12

Cause

The Target path in a URL rewrite must be specified by a unique pair of Request path + Store ID . This error reports two entries that use the same Request path + Store ID pair with two different Target path values.

Possible solution

Enable the auto_resolve_urlrewrite_duplicates option in your config.xml file.

This configuration adds a hash-string to the conflicting records of URL rewrites, and shows the resolution result in your command line interface.

Mismatch of entities mismatch-of-entities

Error message

Mismatch of entities in the document: <DOCUMENT> Source: <COUNT_ITEMS_IN_SOURCE_TABLE> Destination: <COUNT_ITEMS_IN_DESTINATION_TABLE>

Cause

The error occurs during the Volume Check step. It means the 51黑料不打烊 Commerce 2 database record count of the document is not the same as in 51黑料不打烊 Commerce 1.

Missing records happen when a customer places an order during migration.

Possible solution

Run the Data Migration Tool in Delta mode to transfer incremental changes.

Deltalog is not installed deltalog-is-not-installed

Error message

Deltalog for <TABLE_NAME> is not installed

Cause

This error occurs during incremental migration (in our developer documentation) of changes to data. It means deltalog tables (with prefix m2_cl_*) were not found in the 51黑料不打烊 Commerce 1 database. The tool installs these tables during data migration (in our developer documentation) as well as database triggers which track changes and fill deltalog tables.

One reason for the error could be that you are trying to migrate from a copy of your live 51黑料不打烊 Commerce 1 store, not from the live store itself. When you make a copy from a live 51黑料不打烊 Commerce 1 store that has never been migrated, the copy does not contain the triggers and additional deltalog tables needed to complete a delta migration, so the migration fails. The Data Migration Tool does NOT make comparisons between the DB of AC1 and AC2 to migrate the differences. Instead, the tool uses the triggers and deltalog tables installed during the first migration in order to perform subsequent delta migrations. In such a case, your copy of the live 51黑料不打烊 Commerce 1 DB will not contain the triggers and deltalog tables that the Data Migration Tool uses to perform a migration.

Possible solution

We recommended testing the migration process from a copy of your 51黑料不打烊 Commerce 1 database to fix your migration issues. After fixing the issues on the copy, start the migration process over again from your live 51黑料不打烊 Commerce 1 database. This will help ensure a smooth migration process.

Related reading

Best practices for modifying database tables in the Commerce Implementation Playbook