Not the answer you need?
Register and ask your own question!

What are the steps to upgrade standard 5.0.92 community edition to latest percona build 5.5?

iberkneriberkner ContributorInactive User Role Beginner
We have a dedicated server and I'd like to swap out the currently running version of 5.0.92-community-log MySQL Community Edition (GPL) with the latest Percona build (5.5) without losing any of the data, etc.

I'm sure its a fairly straightforward process, but would be great to get some advice / steps on how to do it.

Thanks!

Comments

  • xaprbxaprb Mentor Inactive User Role Beginner
    I wouldn't say it's straightforward. It depends on how risk-tolerant you are. At a minimum, the mysql_upgrade process needs to happen. I believe that if the data is important, using pt-upgrade to validate that everything still works as expected afterwards is also pretty much a minimal requirement for such a big upgrade.

    The MySQL manual's upgrading pages for each major version, and the changelogs between those versions, are important to read too.
  • iberkneriberkner Contributor Inactive User Role Beginner
    Thanks, I got the upgrade done.

    1. Backup (of course)
    2. Stopped old server.
    3. Uninstalled it (yum remove)
    4. Installed Percona mysql through RPM
    5. Addressed any library conflicts (had to remove additional 5.0 libraries)
    6. Updated configuration file to remove incompatible settings
    7. Started new mysql
    8. Run mysql_upgrade

    Things are looking good.
  • jcesariojcesario Contributor Current User Role Beginner
    One of the things I try to make everyone aware of when upgrading from 5.0 -> 5.1+ is the change in some of the charset/collations that happened in 5.1.24

    In specific this changelog.

    Incompatible Change: The utf8_general_ci and ucs2_general_ci collations did not sort the letter "U+00DF SHARP S" equal to 's'.

    As a result of this bug fix, indexes must be rebuilt for columns that use the utf8_general_ci or ucs2_general_ci collation for columns that contain SHARP S. See Section 2.13.3, "Checking Whether Tables or Indexes Must Be Rebuilt". (Bug #27877)


    Ensure you understand what this means and whether or not you want to use these charsets or whether you want to use the Percona compatible ones.

    This percona blog post mentions the compatibility patches introduced in 5.1.58 by percona:

    http://www.mysqlperformanceblog.com/2011/08/17/percona-serve r-5-1-58-12-9/
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.