MySQL Bugs: #41208: c-tree to MySQL - The list of schema names could not be retrieved (error: 0)

Bug #41208	c-tree to MySQL - The list of schema names could not be retrieved (error: 0)
Submitted:	3 Dec 2008 18:18	Modified:	22 Jan 2009 13:07
Reporter:	Petrus van Bork	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S1 (Critical)
Version:	1.1.14	OS:	Windows (Vista SP1)
Assigned to:		CPU Architecture:	Any
Tags:	c-tree, faircom, schema

Description:
Using the generic JDBC driver category and Faircom's JDBC driver am attempting to migrate Faircom c-tree database to MySQL using Migration tool.  I get the dreaded schema error and I am already using the very latest version of the migration tool.

I get:

Connecting to source database and retrieve schemata names.
The list of schema names could not be retrieved (error: 0).
ReverseEngineeringGeneric.getSchemata :ctree.jdbc.ctreeDriver
Details: 
java.net.URLClassLoader$1.run(Unknown Source)
java.security.AccessController.doPrivileged(Native Method)
java.net.URLClassLoader.findClass(Unknown Source)
java.lang.ClassLoader.loadClass(Unknown Source)
sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
java.lang.ClassLoader.loadClass(Unknown Source)
java.lang.ClassLoader.loadClassInternal(Unknown Source)
java.lang.Class.forName0(Native Method)
java.lang.Class.forName(Unknown Source)
com.mysql.grt.modules.ReverseEngineeringGeneric.establishConnection(ReverseEngineeringGeneric.java:84)
com.mysql.grt.modules.ReverseEngineeringGeneric.getSchemata(ReverseEngineeringGeneric.java:230)
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)

..faircom says this is not their headache, they know nothing of MySQL and that it is a problem with the migration tool....help!

How to repeat:
Install JDBC Driver:

(settings verified by Faircom as correct...)

classname: ctree.jdbc.ctreeDriver

connection string: dbc:ctree:6597@localhost:ctreeSQL

Username <default>
Password <default>

...this gets it every time.

Suggested fix:
...I am sorry, I am not familiar enough with these databases to really suggest anything solid.

Thank you for a problem report. Please, try to repeat with a newer version, 1.1.15, and inform about the results.

Dear Valeriy inter alia:

I have been in extensive correspondence with Faircom and it proves to be the case that there was a 'stand alone' ODBC driver for their older c-treePLUS product (now superceded by c-treeACE).  This ODBC driver is not compatible with the newer c-tree versions nor with their JDBC driver.  We are now purchasing this legacy ODBC driver (for use with the legacy c-treePLUS files, as it turns out..  We will test the legacy driver with a JDBC/ODBC bridger driver for use with the migration tool.  So...there is no 'bug' in the sense of a fault with the migration tool despite appearances.  Note, while Faircom does not support the bridge driver they believe that their legacy ODBC driver will likely work wtih it based on field reports.

Question:  should I report our experience with the JDBC/ODBC bridge driver and the migration tool after we work with these, anywhere?

Thank you for your attention to this 'bug.'

Very Best,

Petrus

Yes, please, report about any results with migration. We need to know all cases when Migration Toolkit works and, even more, when it does NOT work.

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".