Bug #14330 The list of schema names could not be retrieved (error: 0).
Submitted: 26 Oct 2005 13:24 Modified: 26 Nov 2005 21:33
Reporter: Leith Tussing Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S1 (Critical)
Version:1.0.20 RC OS:Windows (Windows 2003 Server SP1)
Assigned to: CPU Architecture:Any

[26 Oct 2005 13:24] Leith Tussing 
Description:
This seemed a little different then all the other "The list of schema names could not be retrieved (error: 0)" errors since all of the rest could initiate a connection with the Source database.  However it seems that it can not connect to the source database in my scenario.

Two installations of MySQL on the same Windows 2003 Server.  MySQL 4.1.15 and 5.0.15.  One runs on port 5001 the other on 5002.  Sun java 1.5.0_05.

Connecting to source database and retrieve schemata names.
The list of schema names could not be retrieved (error: 0).
ReverseEngineeringMysqlJdbc.getSchemata :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.ReverseEngineeringMysqlJdbc.getSchemata(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)

How to repeat:
Start MT (running on the same server as the two DBs)
Direct Migration Mode
Fill in the MySQL4 Source information (locahost, port, account with full permissions used)
Fill in the MySQL5 destination information (locahost, port, account with full permissions used)
Click Next
"Connecting to source database system" has a red X
"Retrieve schema information from source database system" has a red X
Clicking Advanced gives the text listed in the Description above.

Suggested fix:
none
[26 Oct 2005 21:32] Jorge del Conde 
I was unable to reproduce this bug using 1.0.20.  Is there any other information you can give us so that we can successfully reproduce this problem ?

Thanks!
[27 Nov 2005 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[1 Feb 2007 11:54] Marco Zoqui 
I got the same problem when I was trying to migrate a database from MS SQL Express (sql 2005 developer edition).

In Source Database page, I could not manage to browse the database, and I think it is because SQL Express uses a different name for the default instance, and I it is required you specify the hostname\instance name, instead of only the hostname.
The SQL Express it supposed to be the same server program version as the SQL SERVER 2005.
Do you have any idea how to migrate from SQL Express?

zoqui