MySQL Bugs: #29395: MySQL Migration Toolkit fails with JRE1.6

Bug #29395	MySQL Migration Toolkit fails with JRE1.6
Submitted:	27 Jun 2007 17:16	Modified:	16 Feb 2009 11:09
Reporter:	neil walker	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S2 (Serious)
Version:	1.1.12	OS:	Windows (XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	jre1.6, jre6, Migration Toolkit

Description:
Hello,
On starting the mysql migration toolkit, it tells me under 'initialised java loader' 'an error occurred... make sure you have the JRE 5 update 8 installed'.

I am running JRE6.

How to repeat:
Use JRE6 (1.6) as your active java runtime and run the program.

Suggested fix:
Don't check for a specific version, as java versions change.

Thank you for the bug report.

as a workaround the old java version can be found here:
http://java.sun.com/products/archive/j2se/5.0_08/index.html

Hello,

Nothing happened since August 2007.
Same error but the migration toolkit works with the latest JRE 5 Update 14.

What are the big differences between JRE 5 and JRE 6 for the toolkit ?

My machine have both jre1.5.0_12 and jre1.6.0_4.
(But primary version is jre1.6.0, as `java -version' on command line shows: 1.6.0_04-b12)

Migration toolkit does not work with same Java Loader error.

I think this issue is very important..., today many machine has already installed
Java 1.6.

I am unable to reproduce this issue in Java 1.6 in Win XP SP2 running under VMWare Fusion on OS X 10.4 with MySQL Migration Toolkit v1.1.12. After installing Java via http://www.java.com/ it required a restart of migration tool, but works nicely, without any Java-related issue.

The version of Java that I'm using that it seems to work with is v1.6.0_07-b06

Migration Toolkit Error screen

Attachment: Java Error.jpg (image/pjpeg, text), 26.94 KiB.

My previous comment was sent prematurely by the software. I installed Java 6.7 on both Windows Xp Professional and Windows Vista. The Migration Tool gives me the error screen in the previous comment whenever I attempt to convert an Access database. Evidently a LUA module is needed and hasn't been installed. What software (MySql or Java) depends on this module and how is it normally installed?

I've been trying to convert to MySql for over a week and am constantly hitting these roadblocks. I'm starting to feel like this is a deadend path and I'm wasting my time with MySql.

Error screen

Attachment: Error Screen 2.JPG (image/pjpeg, text), 43.53 KiB.

It seems this bug reporting tool won't let me send a file along with my comments.

The previous comment's error screen occurred after I installed Java JRE 5.0 Update 8. It is still the same error as with Jave JRE 6.7.

After installing the Java RJE, are there any manual settings I need to make to initialize Java? If so, can you be specific on what I need to do?

I have the same problem running Migration Toolkit 1.1.14 on a Vista Ultimate machine.  I have JRE 6.0 upgrades 2, 7 and 10 installed.  I also downloaded and installed JRE 5.8, as suggested, but it makes no difference.  The error message from MT suggests that MT is looking for Java in the ./Java or the ./Java/bin directories.  Java no longer installs there.  Instead, the ./java folder contains a series of subfolders, one for each upgrade version, and these contain their own separate /bin subsubfolders.  I could not find an .ini file that told MT where to find Java, so that it could be modified.  I will try moving Java executables into the /Program Files/Java directory, but I anticipate registry problems.  How about a bug fix?  As it stands, MT is unrunnable, and so for all my practical purposes the MySQL installation is dead in the water.

It's December 2008. Sun owns MySQL. But MySQL's Migration Toolkit still doesn't run on the current version of Sun's Java, requiring users to instead install an earlier version of Java (5) to run the toolkit.

Installing 5 worked for me, but I found that doing so caused me to be a bit confused about the relationship between Sun and MySQL. What's happening here? Will this be fixed?

We are sorry for this long delay before coming back to this report. Fact is, MT has always only worked with JRE 5.x and also indicated that in an eventual error message. Due to certain contraints we haven't been able to fix the parts in MT which would make it work with Java 6.

In order to improve that situation we decided to include MT's functionality into MySQL Workbench (version 5.2), but that means we will not fix MT itself. Hope this is still good news for you.

Saying that the functionality is included in Workbench isn't much help for those without an enterprise subscription.