Bug #13885 The schema could not be reverse engineered (error: 0).
Submitted: 10 Oct 2005 0:40 Modified: 21 Nov 2005 18:06
Reporter: sfx Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:1.0.18 RC OS:Microsoft Windows (Windows XP Pro SP2)
Assigned to: Bugs System CPU Architecture:Any

[10 Oct 2005 0:40] sfx
Description:
When migrating an Access database to MySQL 5 with the latest Migration Toolkit I get the following error message:

The schema could not be reverse engineered (error: 0).
Illegal group reference
Details: 
java.util.regex.Matcher.appendReplacement(Unknown Source)
java.util.regex.Matcher.replaceAll(Unknown Source)
java.lang.String.replaceAll(Unknown Source)
com.mysql.grt.modules.ReverseEngineeringGeneric.establishConnection(Unknown Source)
com.mysql.grt.modules.ReverseEngineeringAccess.reverseEngineer(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
com.mysql.grt.Grt.callModuleFunction(Unknown Source)

I have enabled System objects from within Access and granted Administrative permissions to each system table.

How to repeat:
MS Access

1. Enable System objects from MS Access.
2. Grant Administrative permissions to Access system tables.

MySQL MT

1. Run MT.
2. Initiate connection to Access database in question.
3. Follow the necessary prompts.
4. Error occurs after selecting the yellow database container icon from the object selection screen and clicking next.
[11 Oct 2005 18:22] Jorge del Conde
I was able to repeat this bug using Access 2003 and by doing the following:

1. Enable System objects from MS Access.
2. Grant Administrative permissions to Access system tables.
[19 Oct 2005 13:08] Michael G. Zinner
Could you please attach the .mdb file that does not work? Thanks.
[21 Nov 2005 18:06] Jorge del Conde
This problem doesn't seem o happen in 1.0.20 anymore.
[13 Sep 2007 21:14] Fabricio Jacome
I get the same error condition but trying to migrate from mysq 4.1 to mysql 5.0. The funny thing is that if i use a different database , it works fine. The database I need to backup is a large one , but it is similar to the others i dont know why it does not work.