Integrity constraint violation: 1062 Duplicate entry '0' for key 'PRIMARY'
I'm trying to migrate from Magento 1 to 2 and when I get to this part:
[2017-10-06 14:04:36][INFO][mode: data][stage: data migration][step: Map Step]: started
33% [=========>------------------] Remaining Time: 3 mins
I then get this error
[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '0' for key 'PRIMARY'
Any ideas?
migration data
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm trying to migrate from Magento 1 to 2 and when I get to this part:
[2017-10-06 14:04:36][INFO][mode: data][stage: data migration][step: Map Step]: started
33% [=========>------------------] Remaining Time: 3 mins
I then get this error
[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '0' for key 'PRIMARY'
Any ideas?
migration data
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm trying to migrate from Magento 1 to 2 and when I get to this part:
[2017-10-06 14:04:36][INFO][mode: data][stage: data migration][step: Map Step]: started
33% [=========>------------------] Remaining Time: 3 mins
I then get this error
[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '0' for key 'PRIMARY'
Any ideas?
migration data
I'm trying to migrate from Magento 1 to 2 and when I get to this part:
[2017-10-06 14:04:36][INFO][mode: data][stage: data migration][step: Map Step]: started
33% [=========>------------------] Remaining Time: 3 mins
I then get this error
[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '0' for key 'PRIMARY'
Any ideas?
migration data
migration data
asked Oct 6 '17 at 14:12
Fred
213
213
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I am getting the same error. When doing the migration with verbose mode on, I can see that the issue is with the "customer_group" table. Primary key 0 is the "NOT LOGGED IN" customer group.
That is how far I am into for now. I will let you know if I find anything else.
How do you know which table is causing the issue?
– Fred
Oct 9 '17 at 8:21
add a comment |
I had the same problem.. to get past it at least temporarily, I added this to the map.xml file under source and under document_rules
<ignore>
<document>customer_group</document>
</ignore>
add a comment |
The problem should go away if you change bulk_size
to something other than 0 in your config.xml. It doesn't seem to auto-detect correctly on the customer_group
table. Setting mine to 100 solved the problem for me.
To find out what table is the problem, try adding some debugging info to your src/Migration/Step/Map/Data.php
file. Something like $this->logger->info("DEBUG: " . $sourceDocName );
around line 136. This should output the table the migration tool is currently working on in the console.
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%2f196221%2fintegrity-constraint-violation-1062-duplicate-entry-0-for-key-primary%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
I am getting the same error. When doing the migration with verbose mode on, I can see that the issue is with the "customer_group" table. Primary key 0 is the "NOT LOGGED IN" customer group.
That is how far I am into for now. I will let you know if I find anything else.
How do you know which table is causing the issue?
– Fred
Oct 9 '17 at 8:21
add a comment |
I am getting the same error. When doing the migration with verbose mode on, I can see that the issue is with the "customer_group" table. Primary key 0 is the "NOT LOGGED IN" customer group.
That is how far I am into for now. I will let you know if I find anything else.
How do you know which table is causing the issue?
– Fred
Oct 9 '17 at 8:21
add a comment |
I am getting the same error. When doing the migration with verbose mode on, I can see that the issue is with the "customer_group" table. Primary key 0 is the "NOT LOGGED IN" customer group.
That is how far I am into for now. I will let you know if I find anything else.
I am getting the same error. When doing the migration with verbose mode on, I can see that the issue is with the "customer_group" table. Primary key 0 is the "NOT LOGGED IN" customer group.
That is how far I am into for now. I will let you know if I find anything else.
edited Oct 6 '17 at 20:50
Abhishek Panchal
3,4122929
3,4122929
answered Oct 6 '17 at 19:31
Wesley J
513
513
How do you know which table is causing the issue?
– Fred
Oct 9 '17 at 8:21
add a comment |
How do you know which table is causing the issue?
– Fred
Oct 9 '17 at 8:21
How do you know which table is causing the issue?
– Fred
Oct 9 '17 at 8:21
How do you know which table is causing the issue?
– Fred
Oct 9 '17 at 8:21
add a comment |
I had the same problem.. to get past it at least temporarily, I added this to the map.xml file under source and under document_rules
<ignore>
<document>customer_group</document>
</ignore>
add a comment |
I had the same problem.. to get past it at least temporarily, I added this to the map.xml file under source and under document_rules
<ignore>
<document>customer_group</document>
</ignore>
add a comment |
I had the same problem.. to get past it at least temporarily, I added this to the map.xml file under source and under document_rules
<ignore>
<document>customer_group</document>
</ignore>
I had the same problem.. to get past it at least temporarily, I added this to the map.xml file under source and under document_rules
<ignore>
<document>customer_group</document>
</ignore>
answered Oct 24 '17 at 21:35
Anthony B
11
11
add a comment |
add a comment |
The problem should go away if you change bulk_size
to something other than 0 in your config.xml. It doesn't seem to auto-detect correctly on the customer_group
table. Setting mine to 100 solved the problem for me.
To find out what table is the problem, try adding some debugging info to your src/Migration/Step/Map/Data.php
file. Something like $this->logger->info("DEBUG: " . $sourceDocName );
around line 136. This should output the table the migration tool is currently working on in the console.
add a comment |
The problem should go away if you change bulk_size
to something other than 0 in your config.xml. It doesn't seem to auto-detect correctly on the customer_group
table. Setting mine to 100 solved the problem for me.
To find out what table is the problem, try adding some debugging info to your src/Migration/Step/Map/Data.php
file. Something like $this->logger->info("DEBUG: " . $sourceDocName );
around line 136. This should output the table the migration tool is currently working on in the console.
add a comment |
The problem should go away if you change bulk_size
to something other than 0 in your config.xml. It doesn't seem to auto-detect correctly on the customer_group
table. Setting mine to 100 solved the problem for me.
To find out what table is the problem, try adding some debugging info to your src/Migration/Step/Map/Data.php
file. Something like $this->logger->info("DEBUG: " . $sourceDocName );
around line 136. This should output the table the migration tool is currently working on in the console.
The problem should go away if you change bulk_size
to something other than 0 in your config.xml. It doesn't seem to auto-detect correctly on the customer_group
table. Setting mine to 100 solved the problem for me.
To find out what table is the problem, try adding some debugging info to your src/Migration/Step/Map/Data.php
file. Something like $this->logger->info("DEBUG: " . $sourceDocName );
around line 136. This should output the table the migration tool is currently working on in the console.
edited Nov 18 '17 at 0:02
Abhishek Panchal
3,4122929
3,4122929
answered Nov 17 '17 at 18:18
Sean Michaud
311
311
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f196221%2fintegrity-constraint-violation-1062-duplicate-entry-0-for-key-primary%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