The u_e_pkey index is defined in lib/pkp/xml/schema/controlledVocab.xml. At a guess, it sounds like a user has the same reviewing interest specified more than once in your XML.
Regards,
Alec Smecher
Public Knowledge Project Team
Is it possible that you’re importing a user who already exists, and has that reviewing interest already assigned to their account? (If you can confirm this, it would be a good aspect of the code to improve.)
Regards,
Alec Smecher
Public Knowledge Project Team
I cleared all the users from the system and tried the import again but got the same error, this time instead of DB Error: Duplicate entry ‘39-441’ for key ‘u_e_pkey’
I got DB Error: Duplicate entry ‘74-441’ for key ‘u_e_pkey’
So it definitely a user user causing the issue, but im not sure how to identify the user.
I managed to import all the users in batches of 42.
For some reason the import kept on failing on the 43 or 44 record, even tho the record had a first_name, the entry in the db would have “user1” as the first_name and he rest of the record would be empty except for the dates.
This happened every time I had more than 42 records in die XML file.
Ah, that note about the number of users is helpful. I see this has already been caught at Importing users from 2.2.4 to 2.4.8. You should be able to increase your server’s max_input_vars setting to allow more at a time. (Note that the OJS 3.x plugin doesn’t have this limit.)
Regards,
Alec Smecher
Public Knowledge Project Team
Could you post this as a new topic with as many relevant details as you can include? That’ll help keep the forum organized. I’d suggest seeing if you can determine what step in the upgrade process is being executed – if you’re not using the command-line upgrade tool, then I’d recommend it; it provides more information on what the upgrade is doing.
Regards,
Alec Smecher
Public Knowledge Project Team