Data Migration error In magento 2 intergrity constraint violation : duplicate entry :1-Migration_DefaultSQL Error: Integrity constraint violation: 1062 Duplicate entryData migration Eav step errorSQLSTATE[23000]: Integrity constraint violation:1062 Duplicate entry '2000734" for keySQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry while indexingMagento 2 : Unique constraint violation found when adding product, categories or mega menu itemsGetting an error in Indexing after migration in Magento 2.2.6SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '18-227' for key 'EAV_ENTITY_ATTRIBUTE_ATTRIBUTE_SET_ID_ATTRIBUTE_ID'SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1' for key 'SALES_ORDER_INCREMENT_ID_STORE_ID'Data Migration > Eav step errorDuplicate entry '1-Migration_Default' for key
How long should I wait to plug in my refrigerator after unplugging it?
Which one is more important between endgame studies and tactics?
Can a Hogwarts student refuse the Sorting Hat's decision?
Is the first page of a novel really that important?
Probably terminated or laid off soon; confront or not?
Make lens aperture in Tikz
The warlock of firetop mountain, what's the deal with reference 192?
Getting Lost in the Caves of Chaos
Can the Cauchy product of divergent series with itself be convergent?
Why do rocket engines use nitrogen actuators to operate the fuel/oxidiser valves instead of electric servos?
Is there a way to improve my grade after graduation?
…down the primrose path
How does Rust's 128-bit integer `i128` work on a 64-bit system?
How do people drown while wearing a life jacket?
Is there any difference between "result in" and "end up with"?
Is an "are" omitted in this sentence
Piece de Resistance - Introduction & Ace and A's
Is there a difference between `board[x, y]` and `board[x][y]` in Python?
conditional probability of dependent random variables
How to check a file was encrypted
ZFS on Linux: Which mountpoint option when mounting manually per script?
How easy is it to get a gun illegally in the United States?
Is it okay to use different fingers every time while playing a song on keyboard? Is it considered a bad practice?
Is there a command-line tool for converting html files to pdf?
Data Migration error In magento 2 intergrity constraint violation : duplicate entry :1-Migration_Default
SQL Error: Integrity constraint violation: 1062 Duplicate entryData migration Eav step errorSQLSTATE[23000]: Integrity constraint violation:1062 Duplicate entry '2000734" for keySQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry while indexingMagento 2 : Unique constraint violation found when adding product, categories or mega menu itemsGetting an error in Indexing after migration in Magento 2.2.6SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '18-227' for key 'EAV_ENTITY_ATTRIBUTE_ATTRIBUTE_SET_ID_ATTRIBUTE_ID'SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1' for key 'SALES_ORDER_INCREMENT_ID_STORE_ID'Data Migration > Eav step errorDuplicate entry '1-Migration_Default' for key
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Error : SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'
I reinstall the setup with a fresh database and it did not solve the issue. Please suggest a solution for this.
After reinstalling magento2 setup: a new error occured : Notice: Undefined offset: 8 in /opt/lampp/htdocs/namuk/NAMU/branches/namuk2.2.5/vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php
magento2 database error data-migration
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
add a comment |
Error : SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'
I reinstall the setup with a fresh database and it did not solve the issue. Please suggest a solution for this.
After reinstalling magento2 setup: a new error occured : Notice: Undefined offset: 8 in /opt/lampp/htdocs/namuk/NAMU/branches/namuk2.2.5/vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php
magento2 database error data-migration
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
Migrate in which Magento?
– Dhaduk Mitesh
Jun 28 '18 at 11:13
from 1.9.2.4 to 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:41
Can you check1-Migration_Defaultthis value exists ineav_attribute_settable?
– Dhaduk Mitesh
Jun 28 '18 at 12:45
add a comment |
Error : SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'
I reinstall the setup with a fresh database and it did not solve the issue. Please suggest a solution for this.
After reinstalling magento2 setup: a new error occured : Notice: Undefined offset: 8 in /opt/lampp/htdocs/namuk/NAMU/branches/namuk2.2.5/vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php
magento2 database error data-migration
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
Error : SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'
I reinstall the setup with a fresh database and it did not solve the issue. Please suggest a solution for this.
After reinstalling magento2 setup: a new error occured : Notice: Undefined offset: 8 in /opt/lampp/htdocs/namuk/NAMU/branches/namuk2.2.5/vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php
magento2 database error data-migration
magento2 database error data-migration
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
edited Jun 28 '18 at 13:06
Divya Muralidharan
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
asked Jun 28 '18 at 11:01
Divya MuralidharanDivya Muralidharan
4441 gold badge4 silver badges18 bronze badges
4441 gold badge4 silver badges18 bronze badges
Migrate in which Magento?
– Dhaduk Mitesh
Jun 28 '18 at 11:13
from 1.9.2.4 to 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:41
Can you check1-Migration_Defaultthis value exists ineav_attribute_settable?
– Dhaduk Mitesh
Jun 28 '18 at 12:45
add a comment |
Migrate in which Magento?
– Dhaduk Mitesh
Jun 28 '18 at 11:13
from 1.9.2.4 to 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:41
Can you check1-Migration_Defaultthis value exists ineav_attribute_settable?
– Dhaduk Mitesh
Jun 28 '18 at 12:45
Migrate in which Magento?
– Dhaduk Mitesh
Jun 28 '18 at 11:13
Migrate in which Magento?
– Dhaduk Mitesh
Jun 28 '18 at 11:13
from 1.9.2.4 to 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:41
from 1.9.2.4 to 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:41
Can you check
1-Migration_Default this value exists in eav_attribute_set table?– Dhaduk Mitesh
Jun 28 '18 at 12:45
Can you check
1-Migration_Default this value exists in eav_attribute_set table?– Dhaduk Mitesh
Jun 28 '18 at 12:45
add a comment |
3 Answers
3
active
oldest
votes
Try to use the latest version of the tool It has fixes which may help.
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
Iam using latest version of the tool 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:40
add a comment |
Go to table eav_attribute_group and see if there are multiple entries for 1-Migration_Defaul in attribute_group_code column of the table. Delete any one row or try running migration command without -r|--reset arguments like this - php bin/magento bin/magento migrate:data <path to config.xml>
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
there is no multiple entries
– Divya Muralidharan
Jun 28 '18 at 12:41
In which database are you checking? Check in destination database.
– mighty_hk
Jun 28 '18 at 12:43
Yes in the destination database @mighty_hk
– Divya Muralidharan
Jun 28 '18 at 13:05
Then try running command without -r argument like this - php bin/magento bin/magento migrate:data <path to config.xml>
– mighty_hk
Jun 29 '18 at 4:46
add a comment |
I think I know what happens, it's one I have banged my head against in the past
It happens that if an error stops the migration then the migration of the attribute sets does not get reverted, and several tables get left in a state that will break the next migration attempt. So the next time you will get undefined offset, then duplicate entry, then undefined offset, then duplicate entry
m2's eav_attribute_set table ends up containing the "migration_"
entries after the undefined offset error or any other error during a
further substep of the eav process (hence causing the "duplicate"
error next time)m2's eav_attribute_set table ends up completely empty after this
error (causing the "undefined offset" error next time as the default entries are missing)on and on forever
Note that you first have to have another error, like missing document.
Ideally you keep a snapshot of the eav_attribute... tables and reset them.
For those struggling, I have managed to pass through by MANUALLY (in SQL) rebuilding the eav_attribute_set and eav_attribute_group tables in the database to have only the original entries, but with the IDs from after my first migration
But if I then get another error in the EAV step (eg: class name reference from a module I am not planning to migrate) then this error is back on the next run so I have to do that manual clean up over and over.
See my second comment on this issue on the migration tool bug tracker for details of the SQL https://github.com/magento/data-migration-tool/issues/204 to
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f231703%2fdata-migration-error-in-magento-2-intergrity-constraint-violation-duplicate-en%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try to use the latest version of the tool It has fixes which may help.
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
Iam using latest version of the tool 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:40
add a comment |
Try to use the latest version of the tool It has fixes which may help.
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
Iam using latest version of the tool 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:40
add a comment |
Try to use the latest version of the tool It has fixes which may help.
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
Try to use the latest version of the tool It has fixes which may help.
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
edited Jun 28 '18 at 11:13
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
answered Jun 28 '18 at 11:07
Nikunj VadariyaNikunj Vadariya
3,0331 gold badge9 silver badges25 bronze badges
3,0331 gold badge9 silver badges25 bronze badges
Iam using latest version of the tool 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:40
add a comment |
Iam using latest version of the tool 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:40
Iam using latest version of the tool 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:40
Iam using latest version of the tool 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:40
add a comment |
Go to table eav_attribute_group and see if there are multiple entries for 1-Migration_Defaul in attribute_group_code column of the table. Delete any one row or try running migration command without -r|--reset arguments like this - php bin/magento bin/magento migrate:data <path to config.xml>
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
there is no multiple entries
– Divya Muralidharan
Jun 28 '18 at 12:41
In which database are you checking? Check in destination database.
– mighty_hk
Jun 28 '18 at 12:43
Yes in the destination database @mighty_hk
– Divya Muralidharan
Jun 28 '18 at 13:05
Then try running command without -r argument like this - php bin/magento bin/magento migrate:data <path to config.xml>
– mighty_hk
Jun 29 '18 at 4:46
add a comment |
Go to table eav_attribute_group and see if there are multiple entries for 1-Migration_Defaul in attribute_group_code column of the table. Delete any one row or try running migration command without -r|--reset arguments like this - php bin/magento bin/magento migrate:data <path to config.xml>
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
there is no multiple entries
– Divya Muralidharan
Jun 28 '18 at 12:41
In which database are you checking? Check in destination database.
– mighty_hk
Jun 28 '18 at 12:43
Yes in the destination database @mighty_hk
– Divya Muralidharan
Jun 28 '18 at 13:05
Then try running command without -r argument like this - php bin/magento bin/magento migrate:data <path to config.xml>
– mighty_hk
Jun 29 '18 at 4:46
add a comment |
Go to table eav_attribute_group and see if there are multiple entries for 1-Migration_Defaul in attribute_group_code column of the table. Delete any one row or try running migration command without -r|--reset arguments like this - php bin/magento bin/magento migrate:data <path to config.xml>
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
Go to table eav_attribute_group and see if there are multiple entries for 1-Migration_Defaul in attribute_group_code column of the table. Delete any one row or try running migration command without -r|--reset arguments like this - php bin/magento bin/magento migrate:data <path to config.xml>
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
answered Jun 28 '18 at 11:30
mighty_hkmighty_hk
5021 silver badge11 bronze badges
5021 silver badge11 bronze badges
there is no multiple entries
– Divya Muralidharan
Jun 28 '18 at 12:41
In which database are you checking? Check in destination database.
– mighty_hk
Jun 28 '18 at 12:43
Yes in the destination database @mighty_hk
– Divya Muralidharan
Jun 28 '18 at 13:05
Then try running command without -r argument like this - php bin/magento bin/magento migrate:data <path to config.xml>
– mighty_hk
Jun 29 '18 at 4:46
add a comment |
there is no multiple entries
– Divya Muralidharan
Jun 28 '18 at 12:41
In which database are you checking? Check in destination database.
– mighty_hk
Jun 28 '18 at 12:43
Yes in the destination database @mighty_hk
– Divya Muralidharan
Jun 28 '18 at 13:05
Then try running command without -r argument like this - php bin/magento bin/magento migrate:data <path to config.xml>
– mighty_hk
Jun 29 '18 at 4:46
there is no multiple entries
– Divya Muralidharan
Jun 28 '18 at 12:41
there is no multiple entries
– Divya Muralidharan
Jun 28 '18 at 12:41
In which database are you checking? Check in destination database.
– mighty_hk
Jun 28 '18 at 12:43
In which database are you checking? Check in destination database.
– mighty_hk
Jun 28 '18 at 12:43
Yes in the destination database @mighty_hk
– Divya Muralidharan
Jun 28 '18 at 13:05
Yes in the destination database @mighty_hk
– Divya Muralidharan
Jun 28 '18 at 13:05
Then try running command without -r argument like this - php bin/magento bin/magento migrate:data <path to config.xml>
– mighty_hk
Jun 29 '18 at 4:46
Then try running command without -r argument like this - php bin/magento bin/magento migrate:data <path to config.xml>
– mighty_hk
Jun 29 '18 at 4:46
add a comment |
I think I know what happens, it's one I have banged my head against in the past
It happens that if an error stops the migration then the migration of the attribute sets does not get reverted, and several tables get left in a state that will break the next migration attempt. So the next time you will get undefined offset, then duplicate entry, then undefined offset, then duplicate entry
m2's eav_attribute_set table ends up containing the "migration_"
entries after the undefined offset error or any other error during a
further substep of the eav process (hence causing the "duplicate"
error next time)m2's eav_attribute_set table ends up completely empty after this
error (causing the "undefined offset" error next time as the default entries are missing)on and on forever
Note that you first have to have another error, like missing document.
Ideally you keep a snapshot of the eav_attribute... tables and reset them.
For those struggling, I have managed to pass through by MANUALLY (in SQL) rebuilding the eav_attribute_set and eav_attribute_group tables in the database to have only the original entries, but with the IDs from after my first migration
But if I then get another error in the EAV step (eg: class name reference from a module I am not planning to migrate) then this error is back on the next run so I have to do that manual clean up over and over.
See my second comment on this issue on the migration tool bug tracker for details of the SQL https://github.com/magento/data-migration-tool/issues/204 to
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
add a comment |
I think I know what happens, it's one I have banged my head against in the past
It happens that if an error stops the migration then the migration of the attribute sets does not get reverted, and several tables get left in a state that will break the next migration attempt. So the next time you will get undefined offset, then duplicate entry, then undefined offset, then duplicate entry
m2's eav_attribute_set table ends up containing the "migration_"
entries after the undefined offset error or any other error during a
further substep of the eav process (hence causing the "duplicate"
error next time)m2's eav_attribute_set table ends up completely empty after this
error (causing the "undefined offset" error next time as the default entries are missing)on and on forever
Note that you first have to have another error, like missing document.
Ideally you keep a snapshot of the eav_attribute... tables and reset them.
For those struggling, I have managed to pass through by MANUALLY (in SQL) rebuilding the eav_attribute_set and eav_attribute_group tables in the database to have only the original entries, but with the IDs from after my first migration
But if I then get another error in the EAV step (eg: class name reference from a module I am not planning to migrate) then this error is back on the next run so I have to do that manual clean up over and over.
See my second comment on this issue on the migration tool bug tracker for details of the SQL https://github.com/magento/data-migration-tool/issues/204 to
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
add a comment |
I think I know what happens, it's one I have banged my head against in the past
It happens that if an error stops the migration then the migration of the attribute sets does not get reverted, and several tables get left in a state that will break the next migration attempt. So the next time you will get undefined offset, then duplicate entry, then undefined offset, then duplicate entry
m2's eav_attribute_set table ends up containing the "migration_"
entries after the undefined offset error or any other error during a
further substep of the eav process (hence causing the "duplicate"
error next time)m2's eav_attribute_set table ends up completely empty after this
error (causing the "undefined offset" error next time as the default entries are missing)on and on forever
Note that you first have to have another error, like missing document.
Ideally you keep a snapshot of the eav_attribute... tables and reset them.
For those struggling, I have managed to pass through by MANUALLY (in SQL) rebuilding the eav_attribute_set and eav_attribute_group tables in the database to have only the original entries, but with the IDs from after my first migration
But if I then get another error in the EAV step (eg: class name reference from a module I am not planning to migrate) then this error is back on the next run so I have to do that manual clean up over and over.
See my second comment on this issue on the migration tool bug tracker for details of the SQL https://github.com/magento/data-migration-tool/issues/204 to
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
I think I know what happens, it's one I have banged my head against in the past
It happens that if an error stops the migration then the migration of the attribute sets does not get reverted, and several tables get left in a state that will break the next migration attempt. So the next time you will get undefined offset, then duplicate entry, then undefined offset, then duplicate entry
m2's eav_attribute_set table ends up containing the "migration_"
entries after the undefined offset error or any other error during a
further substep of the eav process (hence causing the "duplicate"
error next time)m2's eav_attribute_set table ends up completely empty after this
error (causing the "undefined offset" error next time as the default entries are missing)on and on forever
Note that you first have to have another error, like missing document.
Ideally you keep a snapshot of the eav_attribute... tables and reset them.
For those struggling, I have managed to pass through by MANUALLY (in SQL) rebuilding the eav_attribute_set and eav_attribute_group tables in the database to have only the original entries, but with the IDs from after my first migration
But if I then get another error in the EAV step (eg: class name reference from a module I am not planning to migrate) then this error is back on the next run so I have to do that manual clean up over and over.
See my second comment on this issue on the migration tool bug tracker for details of the SQL https://github.com/magento/data-migration-tool/issues/204 to
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
answered Aug 17 '18 at 8:33
iphigenieiphigenie
4962 silver badges16 bronze badges
4962 silver badges16 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f231703%2fdata-migration-error-in-magento-2-intergrity-constraint-violation-duplicate-en%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Migrate in which Magento?
– Dhaduk Mitesh
Jun 28 '18 at 11:13
from 1.9.2.4 to 2.2.5
– Divya Muralidharan
Jun 28 '18 at 12:41
Can you check
1-Migration_Defaultthis value exists ineav_attribute_settable?– Dhaduk Mitesh
Jun 28 '18 at 12:45