MySQL Forums :: MySQL Workbench - Database Migration :: MySQL 4.1 to 5.1 large scale upgrade


Advanced Search

MySQL 4.1 to 5.1 large scale upgrade
Posted by: Jcink Cink ()
Date: March 21, 2011 08:00PM

Hello,

I'm looking for some general advice about an upgrade from MySQL 4.1 to MySQL 5.1. I have already the FAQ page which says "If you perform a binary upgrade without dumping and reloading tables, you cannot upgrade directly from MySQL 4.1 to 5.1 or higher."

With that said here is the environment, a multi-forum host with lots of tables in the database (1.5 to 2 million). Dumping and reloading would be really nasty for us.

However, I don't really know if it's necessary.

> Our tables are all MyISAM
> Our collations are all latin1_swedish_ci
> No InnoDB tables; skipped them in the config

Under the "Changes that cause index rebuilding to be necessary" on the FAQ page, none of what's written there applies to us.

I set up a test environment with one of our backups and tried just dropping everything in. The /mysql/ folder didn't like it, so I just erased it and let it recreate a new one. No problem.

Added new accounts, and then loaded up some test forums. I couldn't find a single thing that wasn't working. I made posts, went into places where I knew some queries were complicated and didn't find any issues at all. Search worked, deleting worked, etc. Debug output showed that things were pretty much the same in regard to MySQL reading from the existing indexes and I couldn't find any performance problems.

Yet CHECK TABLE still reports that "Table upgrade required."

Given all of the information above, is it *really* required? I feel like it's just displaying that message because it sees a version mismatch and that I could probably get away with this upgrade otherwise. A more painless way to bring the tables up to date for added performance reasons, etc, would be for me to do a background process to start checking them based on which ones are most active rather than going for them all.

For what it's worth: when I run REPAIR TABLE on any of the affected ones, it goes just fine. The table then reads OK during another CHECK TABLE.

If anyone has ever done anything like this before or can shed some light about what they think, it would be greatly appreciated.

Options: ReplyQuote


Subject Written By Posted
MySQL 4.1 to 5.1 large scale upgrade Jcink Cink 03/21/2011 08:00PM
Re: MySQL 4.1 to 5.1 large scale upgrade Rick James 03/22/2011 10:01PM
Re: MySQL 4.1 to 5.1 large scale upgrade Jcink Cink 03/23/2011 10:57AM
Re: MySQL 4.1 to 5.1 large scale upgrade Rick James 03/23/2011 07:36PM
Re: MySQL 4.1 to 5.1 large scale upgrade Saniya Deshpande 04/01/2011 12:15AM
Re: MySQL 4.1 to 5.1 large scale upgrade Rick James 04/02/2011 08:32AM
Re: MySQL 4.1 to 5.1 large scale upgrade Jcink Cink 04/02/2011 11:33AM
Re: MySQL 4.1 to 5.1 large scale upgrade Rick James 04/02/2011 12:00PM
Re: MySQL 4.1 to 5.1 large scale upgrade Jcink Cink 04/02/2011 02:34PM
Re: MySQL 4.1 to 5.1 large scale upgrade Rick James 04/02/2011 11:37PM
Re: MySQL 4.1 to 5.1 large scale upgrade Jcink Cink 04/06/2011 11:53AM
Re: MySQL 4.1 to 5.1 large scale upgrade jack albente 08/12/2011 08:31AM
Re: MySQL 4.1 to 5.1 large scale upgrade yu haimei 04/18/2011 03:21AM
Re: MySQL 4.1 to 5.1 large scale upgrade yu haimei 04/18/2011 03:16AM
Re: MySQL 4.1 to 5.1 large scale upgrade tuan phan 05/19/2011 06:52PM
Re: MySQL 4.1 to 5.1 large scale upgrade jack albente 10/21/2011 08:58AM
Re: MySQL 4.1 to 5.1 large scale upgrade outman007 outman007 04/08/2011 12:42AM
Re: MySQL 4.1 to 5.1 large scale upgrade yu haimei 04/18/2011 03:12AM
Re: MySQL 4.1 to 5.1 large scale upgrade yu haimei 04/18/2011 03:08AM
Re: MySQL 4.1 to 5.1 large scale upgrade Leo Wang 05/07/2011 02:41AM
Re: MySQL 4.1 to 5.1 large scale upgrade bennet bamrung 05/11/2011 11:27AM
MySQL 4.1 to 5.1 large scale upgrade Randeep Mann 08/30/2011 11:30PM
Re: MySQL 4.1 to 5.1 large scale upgrade rakesh kushwaha 09/14/2011 05:32AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.