Skip to content

Foreign Key Constraint Fails in Integrity Check #455

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bhagdave opened this issue Feb 5, 2018 · 1 comment
Closed

Foreign Key Constraint Fails in Integrity Check #455

bhagdave opened this issue Feb 5, 2018 · 1 comment

Comments

@bhagdave
Copy link

bhagdave commented Feb 5, 2018

I am migrating a database from 1.9.0.1 to 2.2.2 and fail on the integrity checks. The first failure is
[2018-02-05 15:19:26][ERROR]: Foreign key (FK_mg_CAT_EAV_ATTR_ATTR_ID_mg_EAV_ATTR_ATTR_ID) constraint fails on source database. Orphan records id: 121,178,179,180,181,182,183,184,185,284,285,286,287,288,289,290,291,292,297 from mg_catalog_eav_attribute.attribute_id has no referenced records in mg_eav_attribute

So I looked for the records in mg_catalog_eav_attribute with an attribute_id equal to any of the numbers in the orphan list. And only one of them of them exists. So where have the other numbers come from?
@bhagdave bhagdave closed this as completed Feb 5, 2018
@bhagdave
Copy link
Author

bhagdave commented Feb 5, 2018

My bad... Looked at wrong database

@victor-v-rad victor-v-rad mentioned this issue Dec 4, 2018
Closed
@victor-v-rad victor-v-rad mentioned this issue Dec 18, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bhagdave