MySQL Bugs: #16628: SQLAnywhere: The list of schema names could not be retrieved (error: 0).

Bug #16628	SQLAnywhere: The list of schema names could not be retrieved (error: 0).
Submitted:	19 Jan 2006 11:13	Modified:	8 Jun 2006 14:54
Reporter:	Andreas Götz	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S2 (Serious)
Version:	1.0.22rc	OS:	Windows (WinXP SP2)
Assigned to:		CPU Architecture:	Any

Description:
Receiving error message reverse engineering a SQLAnywhere DB:

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)

How to repeat:
.

Suggested fix:
.

Thank you for a problem report. It looks like a bug in that generic JDBC over ODBC driver... Can you try to repeat with another JDBC driver for SQLAnywhere?

Mhhm. This is the generic Sun driver. How could I add another one?

Thanks,
Andi

As for where to get other JDBC drivers, look at:

http://www.sybase.com/products/informationmanagement/sqlanywherestudio or http://www.ianywhere.com/developer/technotes/sas_jdbc_driver.html

I am neither Sybase expert, nor big fan, but Google search may give you more results. If you still want to use that generic JDBC over ODBC driver, please, switch on trace for the appropriate ODBC data source, try the same migration actions and upload that trace file here.

Anyway, I still see no evidence of bug in any part of MySQL code in this report.

Your feedback is much appreciated- could you give a hint how to enable tracing? 

Thanks a lot,
Andi

To switch on ODBC tracing, please, select:

Start > Control Panel > Administration > ODBC Administrator > ... your DSN > Properties (or Settings, don't remember) > Advanced tab. Then, in case of Connector/ODBC 3.51.12 > Debug tab > Trace Driver Calls To myodbc.log.

Something like this... In case of older connector version, please, upgrade first. Send that myodbc.log, if it has some errors.

ODBC Trace File

Attachment: sql.LOG (text/plain), 53.31 KiB.

Valeriy,

added trace file, thank you. Not a big fan either- thats why having the data in MySQL will simplify things...

Thanks,
Andi

If that error log is from MySQL ODBC-based data source, then I see no errors there (as I informed you before). Looks like the problem is NOT in MySQL code, as I informed you already. Have to tried other JDBC/ODBC drivers for SQL Anywhere?

Valeriy,

the trace is obviously from the source DB, so SQLAnywhere, not mysql?! Anyway, if you think there's no bug and no help then I'll have to live with that and there won't be migration from SQLAnywhere to Mysql. In this case, please close the bug.

Regards,
Andreas

Please, try to repeat with a newer version, 1.0.23-rc, and inform about the results.

Still the same problem:

Connecting to source database and retrieve schemata names.
Fetching schemata list.
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)

Sorry,
Andreas

Problem still exists with 1.0.25- anything I could do to help?
Follow-on problem is that when reloading application state errors out, the advanced button for the logfile is not visible yet- only after next/back clicks will it appear.

Thanks,
Andi

Looks like we have to wait for version 1.1.x to get complete support for migration from SQLAnywhere.

This bug is not scheduled to be fixed at this time.