Duplicate entry 'CIG Coordinator' error MySQL, 2.4.0 to 2.5.0 conversion
Description
Attachments
relates to
Activity
John Hall January 15, 2008 at 8:41 AM
I'm still seeing three errors with Beta 2, which I just reported in
ERROR 1062 (23000) at line 137: Duplicate entry 'site.upd.site.mbrshp' for key 2
ERROR 1048 (23000) at line 650: Column 'REALM_KEY' cannot be null
ERROR 1048 (23000) at line 651: Column 'REALM_KEY' cannot be null
I'm not sure which ticket these should be worked on under, or alternatively, if I'm the only one seeing these three errors it may just be something messed up in my data.
Christopher Maurer January 14, 2008 at 12:50 PM
John, We think this was addressed in SAK-12027. Please see if this issue has been resolved with the new beta2 tag.
Bryan Holladay (old account) October 26, 2007 at 12:20 PMEdited
this was more than likely resolved by http://jira.sakaiproject.org/jira/browse/SAK-12027
John Hall October 18, 2007 at 10:23 AM
I've attached the output from running this with mysql's '-f' option to force continuing on with the conversion even on errors:
http://jira.sakaiproject.org/jira/secure/attachment/14653/sakai-upg-errors.txt
There are around 400 errors – mostly but not entirely duplicate entry errors. It looks like most of those lines deal with setting up OSP roles, permissions etc.
John Hall October 18, 2007 at 10:20 AM
Full list of errors experienced with "force" option, to keep going when errors are encountered.
The sakai_2_4_0-2_5_0_mysql_conversion.sql script from QA_007 against data from our pilot server results in the error:
ERROR 1062 (23000) at line 135: Duplicate entry 'CIG Coordinator' for key 2
Line 135 does:
INSERT INTO SAKAI_REALM_ROLE VALUES (DEFAULT, 'CIG COORDINATOR');
This data is from a server that has been running OSP sites since v. 2.2.0 and upgraded 3 times. We defined 3 custom portfolio types derived from the 'stock' each which have "CIG Coordinators". I'm hypothesizing that could be the root of the problem.