MySQL Bugs: #16274: Migration from MySql 3.23.52

Bug #16274	Migration from MySql 3.23.52
Submitted:	7 Jan 2006 4:07	Modified:	12 Jan 2006 0:01
Reporter:	Daniel Lima	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S2 (Serious)
Version:	1.0.21	OS:	Windows (Windows XP SP2)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
In migration from MySql 3.23.52 to MySql 5.0.16 in Step 2 (Object Selection) after Selected Object and pressed Next, the MySql Migration Tool Close yourself.

How to repeat:
In migration from MySql 3.23.52 to MySql 5.0.16 in Step 2 (Object Selection) after Selected Object and pressed Next, the MySql Migration Tool Close yourself.

Which version of Migration kit are you using since in the version field you
edited the server version?

Thank in advance.

Version:
MySql Migration Toolkit - 1.0.21
Source: MySql Server - 3.23.52-nt
Source: MySql Engine - 3.23.52
Source: MySql Client - 3.23.51
Target: MySql Server - 5.0.16-nt
Target: MySql Client - 5.0.11
CPU: Pentium4-2.8G-480MB

I was unable to repeat this issue. I started the 3.23.58 server using port 3307,
create a database/table and I was able to export to 5.0.19 using port 3306.
Both server were running on the same machine.

I did exactly as you did, but not worked to me. 
PS:MySql is 3.23.52, I will upgrade to 3.23.58.
Tanks.

Not work with MySql 3.23.58, too.

I am having the same problems trying to migrate from 3.23.54-max-nt to MySQL 5, the MySQL Migration Toolkit 1.0.25 crashes with no error, it simply shuts down. This occurs when I select the source schemata and click next. Both databases are on the same server running windows 2k advanced server. One is using port 3306 and mysql 5 is on port 3309. The migration tookit successfully connects to both servers. I was able to migrate a simple table with no data, but not able to migrate any schemas with data in it.

I have the same issue.  Two servers, one is MySQL 3.23.56 max and 5.0.18.  Trying to use the Migration Toolkit to move two full schema from 3 to 5.  When I get to the part where I choose a schema, Migration Toolkit quits with no errors.  I'm using version 1.1.10 of the Toolkit.  I don't see any resolution on this bug, was it just forgotten or is it specifically ignored for some reason?

I have reproduced this bug.

Some of my databases 3.23 databases migrate correctly.   Some cause the Migration program to quit -- no error message, program just disapears.  It appears to be data releated, I just don't know what data.

I can confirm this bug also using migration tool 1.1.12 trying to migrate data from 3.23.58-nt to 4.1.22-community-nt-log.

I have successfully been able to use the MySQL Administrator 1.2.12 to backup and restore from 3.23.58 to 4.1.22 when the data was good.  I was able to confirm some data sets did have corrupt data so used the tool to fix the problem and that data then successfully backed up and restored.  In other instances, I had to convert certain data sets to use latin1 rather than utf-8, as per:

http://forum.mamboserver.com/archive/index.php/t-30925.html

Most of the data was either PHPNuke or Mambo sets and those were the ones that were either corrupted or required conversion to latin1 on the restore.

I should also note that one of the PHPNuke data sets have been auto scanned on the newly "migrated" 4.1.22 server and was found to contain Nimda and was healed.  Not sure how that will affect the data at this time but that injection would have occured prior to the migration, as the data set is no longer used.