From: Gary W. Smith [mailto:gary@stripped]
Sent: Wednesday, February 25, 2009 4:36 PM
To: Claudio Nanni; Jerry Schwartz
Subject: RE: Upgrade story / request for insight
To touch a little more on Claudio's statement, you are trying to compare
monkey's and trucks when you talk about mysql on these two different OS's.
Microsoft is a different best when it comes to the install.
[JS] That part I understand. I was more concerned with checking my
production code to make sure nothing broke. I was astonished that the
Windows upgrade didn't go through smoothly, and that's what led to my
What caught my attention though is you are running mysql 4.0 on CentOS.
This means that you are probably running an older version of CentOS as 5.x
comes with mysql 5.0 (I believe). You might want to setup a similar
environment with the same OS and do a db upgrade on that (without your
actual data) and see if everything works first. You might find some lib
issues with the older CentOS.
[JS] Thanks for the warning. I'm on CentOS 4.7, and I wouldn't have thought
about the library issues.
Unfortunately, I don't have another Linux machine to play with.
From: Claudio Nanni [mailto:claudio.nanni@stripped]
Sent: Wed 2/25/2009 12:50 PM
To: Jerry Schwartz
Subject: Re: Upgrade story / request for insight
probably does not help you very much and excuse me in advance for this,
but there is little use in having a development/preproduction system on
none of the issues you faced with windows (services installation probably)
will show up on a CentOS box.
In particular an upgrade which involves filesystem and services installation
is quite different between Win and Linux.
From a 'service' point of view (MySQL server) there will be no difference
for any client in accessing a Win or a Linux box,
but from a maintenance point of view you are facing problems that are
peculiar of the platform,
in windows in fact mysql is installed as a service so you should check
windows services as well.
In any case I strategy I always used for migration is to install the new
version and export / import data,
this is good because you have two parallel servers up and you can compare
and test both of them,
provided you are using different 'sockets', that is different PORT if just
using TCP/IP connection method.
2009/2/25 Jerry Schwartz <jschwartz@stripped>
> My ultimate goal is to upgrade a production server (MySQL 4.1.22 on
> to a modern 5.1 release. My development system is a Windows Vista x86
> machine, and although the process is not that similar I decided to try an
> upgrade there. (I've never done one.) I figured this would give me some
> insight as to whether or not our code would break.
> The upgrade from 5.0.45 to 5.1.31 was a horror show! I downloaded the
> msi package, and ran the wizard. The Windows notes seemed to say that for
> this upgrade I didn't need to uninstall the old one, and that might have
> been a mistake. In any case, the wizard attempted to install 5.1.31, but
> after it asked me if I wanted to configure an instance it just
> I ran the instance configuration wizard by hand, and it showed two
> server versions. The older one was apparently still running. I tried
> shutting it down; I tried deleting it with the sc command, which (after a
> reboot) did make it go away; but the instance configuration wizard still
> listed it. In fact, it still listed it after I renamed the MySQL 5.0
> The 5.1 server would attempt to start, but would fall over dead
> I uninstalled 5.0, and that made no difference. I uninstalled 5.1, and
> I reinstalled it I got the same basic behavior.
> Eventually I went through the registry and wiped out every reference to
> MySQL that I could find. After a reboot and one last installation of 5.1,
> things started to work right. From there on I was able to run
> and get myself back on the air.
> Can anyone guess where I went astray?
> Jerry Schwartz
> The Infoshop by Global Information Incorporated
> 195 Farmington Ave.
> Farmington, CT 06032
> 860.674.8796 / FAX: 860.674.8341