MYSQL error with IBMDB2 engine -- WEB400

Tim,

Too bad I didn't get your message until after we did our upgrade.

Yeah, we discovered the upgrade problem with data directory existing.

We tried the the UPGMYSQL and got the datadir does not exist error.
We tried a lot of different slash, dash and quote combinations before we gave up.
It kept saying "check the upgrade.log file in the installation directory".
The only upgrade.log file we could find was from our May 2009 installation.

And I just gotta say that all you *nix experts know the significance of /usr, /local, /bin, /etc, and all that, but I sure have a hard time looking for stuff and figuring out what should be where. And while I can appreciate the need for symbolic links, shouldn't they be required to have unique names? and not be recursive? But I digress....

So then we tried the INSMYSQL and got errors about my.cnf existing, data dir existing.
So we renamed my.cnf, renamed our data dir and then it installed.

We renamed back to original names and to our surprise, everything worked. We used PHPMYADMIN to change the SUGARCRM USER file from MYISAM back to IBMDB2I and sure enough, MYSQL put it back on the Iseries. We did not have to reinstall SUGARCRM.

The only thing we did not do was (7) run bin/mysql_upgrade in the new version.

Kudos to the MYSQL/IBM team for getting the bugs out, points off for poor upgrade instructions/methods.

---Dale

Dale,

If you can wait until MySQL updates their documentation (hopefully soon), that will probably provide the easiest way to upgrade.
On the other hand, if you want to do this today...
Scott pointed out that my upgrade instructions still have a flaw and won't work when INSMYSQL is used, despite my amendments. I apologize that in my haste I didn't take the time to test those additional steps. I usually download the .tar package and do the installations manually (the steps that I originally listed should be correct in that case.) If you do follow my instructions using INSMYSQL, you'll find that INSMYSQL complains about the data directory existing. You can get around this by setting DATADIR to some throwaway path like /tmp/blah.

So, here are the steps I've just tested:
(1) as a saftey measure, back up your existing data (using mysqldump or similar tool); (2) shut down the old version of MySQL; (3) rename /etc/my.cnf to a temporary name (e.g. /etc/my.cnf2)
(4) run INSMYSQL, specifying DATADIR('/tmp/blah') or similar
(5) replace the existing /etc/my.cnf with the renamed file from step 3; optionally delete /tmp/blah
(6) call QP2TERM; run bin/mysqld_safe to start the new version of the server;
(7) run bin/mysql_upgrade in the new version;
Please let me know if you have any problems! Again, I apologize for the incompleteness of my original response.

Thank you,
Tim Clark