Question

How to upgrade to mysql5 on VPS if it was installed via PPM?

Resolution

  1. Upgrade mysql on VPS manually:

    # mysql -p
mysql> FLUSH TABLES WITH READ LOCK;
mysql> SET GLOBAL read_only = ON;
# mysqldump -p --all-databases --lock-all-tables --add-drop-database --create-options --extended-insert --quick --quote-names > alldb-dump.sql
# /etc/init.d/mysqld stop
# rpm -e MySQL4-server-4.1.22-4.glibc23.pem MySQL4-Max-4.1.22-4.glibc23.pem.i386 MySQL4-client-4.1.22-4.glibc23.pem.i386
# yum install -y MySQL-server-community MySQL-client-community
# mysql_upgrade -p

  2. Finish the upgrade from POA MN:

    # /usr/local/pem/bin/MySQL_ctl upgradeToMySQL5 changePPMOnly 21
DEBUG [upgradeToMySQL5_changePPMOnly] ===> ENTRY
WARNING:
This command changes PPM package for MySQL component and does not execute any upgrade scripts.
It also does not process any native dependencies. All native dependencies must be satisfied before running.
Continue ? (y/n): y
DEBUG [AA::PEM_Current::context] ===> ENTRY
DEBUG [AA::PEM_Current::context] <=== EXIT [0.000089]
DEBUG [SDK::TPackage<unnamed>::getLastMySQL4Component] ===> ENTRY
DEBUG [SDK::TPackage<unnamed>::getLastMySQL4Component] <=== EXIT [0.018920]
DEBUG [void<unnamed>::MySQLUpdater::changePPM] ===> ENTRY
DEBUG [AA::PEM_Current::context] ===> ENTRY
DEBUG [AA::PEM_Current::context] <=== EXIT [0.000030]
DEBUG [Naming] trying to invalidate unknown obj
DEBUG [void<unnamed>::MySQLUpdater::changePPM] <=== EXIT [0.085094]
DEBUG [upgradeToMySQL5_changePPMOnly] <=== EXIT [1.521757]

    That steps are described in 'Upgrading MySQL Database to Version from OS Distribution' section in Services Upgrade and Migration Guide.

Internal content