Virgin install database beef

[wickem]

Good evening Alfresco experts! I have been curious about Alfresco for a while and decided to dive in and see what all the excitement is about. I've downloaded the source for the community edition from SVN and have built Alfresco on OSX. I've installed Tomcat and MySQL and thought I was ready to go! I deployed the application to tomcat and fired up the JVM. It seems that Alfresco is able to connect to my database (which I created manually) and it begins to create the schema (whoo hoo!) Unfortunately, I run into the following issue while Alfresco is giving MySQL some love:

19:42:15,775  ERROR [domain.schema.SchemaBootstrap] Statement execution failed:
   SQL: alter table JBPM_ACTION add index FK_ACTION_REFACT (REFERENCEDACTION_), add constraint FK_ACTION_REFACT foreign key (REFERENCEDACTION_) references JBPM_ACTION (ID_)
   Error: Duplicate key name 'FK_ACTION_REFACT'
   File: /var/folders/p7/p7Xib+4mFFKT3z-hy9bUYE+++TI/-Tmp-/Alfresco/AlfrescoSchema-MySQLInnoDBDialect-Update-4307267907639510715.sql
   Line: 29
19:42:15,777  ERROR [domain.schema.SchemaBootstrap] Schema auto-update failed
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate key name 'FK_ACTION_REFACT'
‍‍‍‍‍‍‍‍

I've searched the forums and couldn't find anyone complaining about this schema object being a duplicate. Please let me know if I've done something (or not done something) to cause this beef-o-roni. Any help or insight you might have is appreciated!

Thanks!

[janv]

I've also seen something similar on my dev setup (also on Mac OS X, originally using MySQL 5.1.47 but also seen with 5.1.49) when dropping the database schema and then re-creating it. On a subsequent fresh bootstrap of Alfresco, I would often (but not always) see "Duplicate key name" (even though my schema was previously empty). In my case, the workaround was to simply restart MySQL (eg. using MySQL pref pane) and the bootstrap would always go through after the restart. Does this workaround work for you ?

Which exact version of MySQL are you using ? If you're not using the latest point release (5.1.51, at time of writing) then you could try upgrading to see if this makes any difference.

Thanks,
Jan