Easiest way to go from mysql 5.0.77 to percona 5.5

  • Filter
  • Time
  • Show
Clear All
new posts

  • Easiest way to go from mysql 5.0.77 to percona 5.5

    I've read up on Percona a fair bit, and would like to upgrade my server to run on the latest stable 5.5 release.

    I'm still on Mysql 5.0.77 though. CentOS 5.6.

    I went to http://www.percona.com/docs/wiki/percona-server:start#instal lation_instructions to read what I need to do, but unless I'm being blind there's no information there? The "migrating from" text has no link to follow?

    My website is popular, but a few hours downtime isn't the end of the world. I don't have any other boxes that I can test on, and don't really want to go to the trouble of creating a VM. I'm happy just to backup and do it live on the production box, knowing I can undo it all and revert back to MySQL 5.0 if need be.

    I feel all of my database usage is pretty standard - I doubt there will be any compatibility issues with my SQL as it's just run-of-the-mill select/update/deletes etc. I'll obviously test it thoroughly once I'm up and running though.

    So, any pointers? I feel I should just do a sql dump, uninstall mysql, install percona, and load the db back in from that batch file? Is this a terrible idea? Educate me!

    Cheers all

  • #2
    You don't even have to create a dump and import it.

    Read my answer 7 posts further down on this forum:
    http://forum.percona.com/index.php?t=msg&th=1910&got o=7158&S=de13cdf3165204ee27b5d9fe387fcac8#msg_7158


    • #3
      I did already read that but it didn't seem to help me as you offered two solutions

      1) quick and easy if going from 5.0 to 5.0
      2) complex with slaves etc if going from 5.0 to 5.5

      I didn't see a quick and easy for going from 5.0 to 5.5 option?


      • #4
        OK, I jumped in and went for it, and it all seems to be ok.

        1) added percona RPM
        2) mysql_dump (just in case)
        3) service mysqld stop
        4) copy mysql data files (just in case)
        5) yum remove mysql
        6) yum install Percona-Server-shared-compat.x86_64
        7) yum install Percona-Server-server-55.x86_64
        service mysql start QUESTION: why is this now "mysql" when it was "mysqld" before?
        9) mysql_upgrade

        done. Simples! I'm a bit of a newb so spent a while trying to work out why I couldn't run "mysql_upgrade" from a mysql shell - whoops, supposed to be run from the linux shell. Also spent a while wondering why "service mysqld start" wasn't working, before I tried it without the "d".

        20 mins of downtime maybe, just because I didn't know what I was doing and was googling as I went.


        • #5
          God for you!
          That was what I meant with checking my other post, just remove the master slave replication stuff and you have the simple way that you just did!


          • #6
            Yes I maybe didn't read your post closely enough. I saw lots of talk of "masters" and "slaves" and thought you were talking about test VMs etc.

            Can you answer my mysqld v mysql question? Other than that oddity I'm 100% happy with the switchover.


            • #7
              I'm glad this worked well for you. mysql/mysqld is because we distribute RPM and Debian packages which are built the same as MySQL Enterprise, so Percona Server is a seamless replacement for MySQL Enterprise. Debian, Red Hat, and all the others distribute their own customizations, some of which are not even documented well, some of which are pretty brain dead. We want to stay close to Oracle's version. DBAs who are using Oracle's binaries don't want to switch away from what they are used to, and we don't want to support a variety of different packages.