Data-migration-tool: [SQLSTATE 2300] Integrite Constraint Violation

[pollom]

Hello,

I keep getting the error below, even when I revert back to the initial state of the db in magento 2.2.1 :

Can anyone help me with this error?

Thanks.

[victor-v-rad]

Hi @pollom

Every customer_entity table in M1 and M2 have UNQ_CUSTOMER_ENTITY_EMAIL_WEBSITE_ID unique index. But seems the index is dropped in your M1 customer_entity table for some reason. Have you solved your issue?

[pollom]

Hi Victor,

Thanks for your reply. I was able to fix that error, but now I'm getting another error that I can't figure out.

The error is: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Defined' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'

I appreciate your help.

Mike

[victor-v-rad]

it is because of the second attempt of migration to the already migrated data. Reinstall magento 2 or restore the DB from a dump

[pollom]

When I reinstall magento 2 do I need to drop, and recreate, the database for magento 2?

[pollom]

Hi Victor,

I reinstalled magento 2 and ran magento migrate:data ... But I'm getting the error I had before:

[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '[email protected]' for key
'CUSTOMER_ENTITY_EMAIL_WEBSITE_ID'

Mike

[pollom]

The index is there but it isn't unique. I modified the index to make it unique, and am, now, getting that error in the database.

[pollom]

I fixed the Integrity constraint error.

Now I'm getting the following error:

[Exception]
Warning: Error while sending QUERY packet. PID=3226 in /var/www/vhosts/migration.makemynewspaper.com/vendor/magento/data-migrati
on-tool/src/Migration/ResourceModel/Adapter/Mysql.php on line 169

Mike

[pollom]

Hi Victor,

The above error seems to have vanished mysteriously, and, now, I am getting the following error:

[PDOException]
SQLSTATE[08S01]: Communication link failure: 1153 Got a packet bigger than 'max_allowed_packet' bytes

Mike

[victor-v-rad]

try to set max_allowed_packet = 1024M in my.conf of MySQL

[pollom]

Hi Victor,

I made the change you suggested in mariadb-server.cnf but am still getting the error:

[PDOException]
SQLSTATE[08S01]: Communication link failure: 1153 Got a packet bigger than 'max_allowed_packet' bytes

Mike

[pollom]

Your suggestion worked. I forgot to restart the database server. But now I am getting these warnings

Could not unserialize data of table_name.value with record id xxxxx

Mike

[pollom]

Does the stage below take a long time? It seems to be taking a long time.

0% [>---------------------------] Remaining Time: < 1 sec

[diazwatson]

@pollom An easy way around the

[PDOException]
SQLSTATE[08S01]: Communication link failure: 1153 Got a packet bigger than 'max_allowed_packet' 

message is to define the bulk size so the tool does not auto detect it.

Maybe something like
<bulk_size>100</bulk_size>

Yes it is going to take longer but it won't crash