Re: Major upgrade on MySQL (5.0.xx to 5.1.xx) -- WEB400

Tim,

Thanks! I have arrived where you told me I would (a harder place). So, here is what I know so far:

The upgrade DID work,sort of, using your instructions with the only wrinkle being that the mysql_upgrade stumbled a little. I should have saved the error message when I ran mysqld_safe so it might help the next person. The reality was, as far as I could tell, MySQL really didn't start so when I ran mysql_upgrade and nothing happened it was because the DB wasn't running. Not sure why. So recovery was what I was after. I checked the status of MySQL using netstat and found the port not in use. I tried to start it through the Zend menus but nothing happened. So I made sure that everything regarding MySQL was quiesced and then I used QP2TERM to run the mysqld_safe command and this time it seemed to start with no errors and then I ran the upgrade. I got a few errors on tables that indicated that my Wordpress instance was running so I killed the Apache instances and then ran the REPAIR TABLE command to fix the tables that were in error.
I still got errors when Navicat tried to access the tables so I ended the MySQL instance again and then restarted MySQL (again, using QP2TERM). Just to be on the safe side, I ran the mysql_upgrade again and it returned with nothing to upgrade. Navicat worked, my blogs and web pages were back up so I assumed that all was well. So, I shut down the instances and tried to start them using the Zend menus. The error I eventually found was that the Zend method of starting the MySQL instance was looking for a mysql.sh file which was not in the bin folder. I copied the old one over but it still wouldn't start although I could run the script from QP2TERM. So, I have just left it at that. I'll tweak my startup routines if necessary so MySQL will start at IPL but for the moment the dust has settled and things seem to be humming along.

The most curious thing in all of this was that my installation is in /usr/local/ (rather than QOpenSys/usr/local) and I didn't have a my.cnf file in etc. It is simply named my .

Yes, the MySQL site docs could use some tweaking. You may want to pull the Upgrade instructions out of the Installation section and move them, corrected, to the upgrade section with a subsection on i5/OS. I don't know where the most sensible placement would be.

If there is something I still should do to ensure that the database is properly updated, let me know.

Pete

Timothy P Clark wrote:

Hi Pete,

Since I'm responsible for providing the instructions that you're probably referring to, I'll do my best to help you here.
First, the instructions that I gave back in September were for upgrading MySQL 5.1.x to MySQL 5.1.y. Going from 5.0 to 5.1 is a little trickier, as you've discovered. Second, it appears that you're using the Zend Core tools to manage the MySQL server. That also makes things harder.

Before I go off and describe a solution that doesn't apply to you, can you help me understand whether you are wanting to continue using the Zend Core tools to manage the MySQL server? Or are you comfortable managing the server from a PASE command line instead?

Tim

Subject: Re: Major upgrade on MySQL (5.0.xx to 5.1.xx)
From: Pete Helgren <pete@xxxxxxxxxx>
Date: Wed, 06 Jan 2010 13:35:53 -0700

Looked like this worked, except it didn't (bummer).
I followed the instructions but the mysqld_safe threw errors about the database even through it indicated that MySQL started. Running the mysql_upgrade produced no output so I assumed it was correct.

Applications using the tables seemed to be working OK but a MySQL tool I use (Navicat) indicates an issue with a system table. So I shut down all instances of MySQL and now it won't start at all. I see this error in the spool file from the job:

Cannot open /usr/local/mysqldata/zmysql.pid.

Looks hosed up. Can anyone help?

Pete

Pete Helgren wrote:

Back in September there were some posts regarding this and some promises to update documentation but I don't see any i5/OS specific instructions on the links in the post. I am using the SAVF method for upgrading and got the "Major upgrades are not allowed using the upgrade installer" error indicating that you can't upgrade.

The posts look like you have to rename a file, run the INSMYSQL procedure pointing to a temporary folder for the data so it doesn't hammer the existing data, and then rename the file back and run the mysql upgrade command. The instructions suggest this route rather than MYSQLINST/UPGMYSQL (which seems counter intuitive). Is that correct? Has anyone had success in upgrading using a SAVF and those instructions?

Thanks

Pete