MySQL Bugs: #13701: Can't migrate mssql to mySQL. "The list of schema names could not be retrieved"

Bug #13701	Can't migrate mssql to mySQL. "The list of schema names could not be retrieved"
Submitted:	3 Oct 2005 7:55	Modified:	13 Jun 2006 12:40
Reporter:	KAZANCI ibrahim	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S1 (Critical)
Version:	1.0.18 rc	OS:	Windows (Win XP)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
Cannot migrate from mssql to mysql

Connecting to source database and retrieve schemata names.
Initializing JDBC driver ... 
Driver class MS SQL JDBC Driver
Opening connection ... 
Connection jdbc:jtds:sqlserver://server:1433/database;user=sa;password=xxx
The list of schema names could not be retrieved (error: 0).
Could not find a Java charset equivalent to DB charset iso_1.
Details: 
net.sourceforge.jtds.jdbc.ConnectionJDBC2.loadCharset(ConnectionJDBC2.java:909)
net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:295)
net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:178)
java.sql.DriverManager.getConnection(Unknown Source)
java.sql.DriverManager.getConnection(Unknown Source)
com.mysql.grt.modules.ReverseEngineeringGeneric.establishConnection(Unknown Source)
com.mysql.grt.modules.ReverseEngineeringMssql.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:
Make MSSQL server collation : SQL_Latin1_General_CP1_CI_AS

Open mysql migration toolkit

select source (mssql 8.0) and target (mysql 5)

The list of schema names could not be retrieved (error: 0).
Could not find a Java charset equivalent to DB charset iso_1.

In addition just selecting source and giving parameters and then click the "..." button near the database edit box giving the same error message.

Suggested fix:
a temporary solution: if you can allow the source db on mssql to be manually selected. Altough we can write source db name manually but it force query the db names on mssql again and do not allow to migrate.

Thank you for your bug report.  I was able to reproduce this bug using the charset SQL_Latin1_General_CP1_CI_AS.  I was unable to repeat this problem using different charsets such as the default ones.

I'm experiencing the same error message with Sybase's SQL Anywhere:

Connecting to source database and retrieve schemata names.
Initializing JDBC driver ... 
Driver class Generic Jdbc
Opening connection ... 
Connection jdbc:odbc:SEAW Samp Db default instance;user=DBA;password=SQL
The list of schema names could not be retrieved (error: 0).
ReverseEngineeringGeneric.getSchemata :Column not found
Details: 
sun.jdbc.odbc.JdbcOdbcResultSet.findColumn(Unknown Source)
sun.jdbc.odbc.JdbcOdbcResultSet.getString(Unknown Source)
com.mysql.grt.modules.ReverseEngineeringGeneric.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)

Any update on this one?

Thanks,
Andreas

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
    http://www.mysql.com/doc/en/Installing_source_tree.html