# RHEL or CentOS - upgrade process community to percona or.... **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [January 25, 2013, 4:00pm UTC](https://forums.percona.com/t/rhel-or-centos-upgrade-process-community-to-percona-or/1979 "2013-01-25T16:00:49Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mcubedpe](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@mcubedpe](https://forums.percona.com/u/mcubedpe)\ **Post date:** [January 25, 2013, 4:00pm UTC](https://forums.percona.com/t/rhel-or-centos-upgrade-process-community-to-percona-or/1979/1 "2013-01-25T16:00:49Z")
Hello, Question about RHEL or CentOS - upgrade process community to percona or… Reviewing: The Percona 5.1 documentation site - it says nothing about how to “Upgrade”. It only shows install. www dot percona dot com /doc/percona-server/5.1/installation.html 2 questions. #1 Community → to Percona - Upgrade process: Should I use: ( for example with 5.1.66 ) "rpm -Uvh Percona-Server-server-51-5.1.66-rel14.2.501.rhel5.x86\_64.rpm Percona-Server-client-51-5.1.66-rel14.2.501.rhel5.x86\_64.rpm Percona-Server-shared-51-5.1.66-rel14.2.501.rhel5.x86\_64.rpm Percona-Server-shared-compat-5.1.66-rel14.2.501.rhel5.x86\_64 .rpm " OR… rpm -e MySQL-server-community MySQL-client-community MySQL-shared-compat MySQL-shared-community and then: rpm -ivh Percona-Server-server-51-5.1.66-rel14.2.501.rhel5.x86\_64.rpm Percona-Server-client-51-5.1.66-rel14.2.501.rhel5.x86\_64.rpm Percona-Server-shared-51-5.1.66-rel14.2.501.rhel5.x86\_64.rpm Percona-Server-shared-compat-5.1.66-rel14.2.501.rhel5.x86\_64 .rpm Question #2 - from Percona to Percona. What should the process be? rpm -e old… rpm -ivh new… or just rpm -Uvh to new. And for simplicity of answering - I mean within the same major version rev. 5.1.x to 5.1.y 5.5.x to 5.5.y I know there are more in-depth guides written on how to upgrade from say 5.1 to 5.5. SO I’m not asking that question. -Michael ---
**Author:** ![mcubedpe](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@mcubedpe](https://forums.percona.com/u/mcubedpe)\ **Post date:** [January 26, 2013, 2:02pm UTC](https://forums.percona.com/t/rhel-or-centos-upgrade-process-community-to-percona-or/1979/2 "2013-01-26T14:02:05Z")
To somewhat answer my own question: #1 - Community to Percona Server; I found this in the RPM script: rpm -qp --scripts Percona-Server-server-51-5.1.66-rel14.2.501.rhel5.x86\_64.rpm … if [“$old\_family” != “$new\_family”]; then error\_text="$error\_text Upgrading directly from MySQL $old\_family to MySQL $new\_family may not be safe in all cases. A manual dump and restore using mysqldump is recommended. It is important to review the MySQL manual’s Upgrading section for version-specific incompatibilities. " … Where “old\_family” would be MySQL\_ ; and where new\_family would be Percona- So I decided that “rpm -Uvh” would not be suitable after seeing this warning in the scripts. #2 - In theory ( though I didn’t try it ) - based on this same script excerpt above - one would think that doing “Percona Server 5.1.x to 5.1.y” or “Percona Server 5.5.x to 5.5.y” via ; rpm -Uvh - would work fine. Although I did not try it. Instead I did the ; stop MySQL ; rpm --nodeps -e MySQL(Community 5.1.66) ; rpm -ivh Percona(Server 5.1.67) - start Percona… and all seemed well… until I tried running ; mysql\_upgrade - which is giving me heartburn on a few wordpress databases for no particularly interesting reason I can find right now. ( replied to another thread with the issue basically getting “Error: Table ‘(realname).(garbled junk)’ doesn’t exist” - so far been unable to get mysql\_upgrade to finish. sigh. -Michael ---
**Author:** ![scott.nemes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/scott.nemes/32/5_2.png) [@scott.nemes](https://forums.percona.com/u/scott.nemes)\ **Post date:** [January 28, 2013, 11:27am UTC](https://forums.percona.com/t/rhel-or-centos-upgrade-process-community-to-percona-or/1979/3 "2013-01-28T11:27:45Z")
I always remove the old RPMs and install the new ones as you did, so that part is good. If you are doing a minor update, that is probably enough depending on how big of a jump you are doing. If you end up going from 5.1 to 5.5 (or potentially a large jump within the 5.1 branch), it is recommended that you dump your data and reload it into the server after installing the new RPMs.