Bug #10852 Missing Tables / "Error 1061 Duplicate key name" migrating from Access97
Submitted: 25 May 2005 4:06 Modified: 15 Jun 2005 22:15
Reporter: joe parry Email Updates:
Status: Closed Impact on me:
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:1.0.6beta OS:Microsoft Windows (WindowsXP)
Assigned to: CPU Architecture:Any

[25 May 2005 4:06] joe parry
Migrating an access97 database results in missing tables.

When the database creation script is saved and run via the sql command line, the missing tables have the following error message associated with them: 

ERROR 1061 (42000): Duplicate key name '{FDF6109A-F141-4090-887E-698AAC7CE73B}'


ERROR 1061 (42000): Duplicate key name 'USER_TASKTASK_DIARY'

How to repeat:
If the bug will let me, i will attach the generated script and an empty copy of the database being used...

Suggested fix:
Im new to MySQL so cant really help here. Looks like a problem with unique naming of indexs or something, theres a few similar comments in the forums.
[25 May 2005 4:07] joe parry
Create Script generated by Migration Toolkit

Attachment: CreateScript.sql (text/plain), 11.67 KiB.

[25 May 2005 4:11] joe parry
Database that resulted in these errors

Attachment: JobTrak2Data.rar (application/octet-stream, text), 39.65 KiB.

[25 May 2005 12:27] MySQL Verification Team
Yes please attach the empty Access mdb file and the script for
test on our side.

Thanks in advance.
[25 May 2005 23:15] joe parry
Script (CreateScript.sql) and database (JobTrak2Data.rar) attached. (Note: Database is compressed and has no data in it.)
[6 Jun 2005 11:36] MySQL Verification Team
Verified with version 1.0.7.
Thank you for the feedback.
[6 Jun 2005 19:31] Michael G. Zinner
Could you check if the problem still exists in 1.0.8? Thanks.
[15 Jun 2005 22:15] Michael G. Zinner
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
[16 Jun 2005 2:12] joe parry
Top work peoples. I Look forward to the next release.