• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 114786, created on Sep 18, 2012, last review on Dec 27, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Important notes

Upgrade to MySQL 5.1.xx within OBAS 4.3 is not recommended. After upgrade to OBAS 4.5 you can upgrade MySQL to latest available template of MySQL 5.1.xx. For more detail please refer to Upgrading MySQL.

Upgrade to further versions of MySQL, e.g. 5.5.xx, 5.7.xx is not recommended as well both for OBAS 4.3 and OBAS 4.5.

Resolution

MySQL 5.x is supported as OBAS database since OBAS 4.3. See the release notes for more details.

OBAS 4.3 installer provides the option of an automatic upgrade of the local MySQL database during OBAS upgrade. If the database is running on a remote server, the MySQL server should be upgraded manually.

This article provides a detailed description of how to upgrade OBAS database to MySQL 5.0 if it is running on a remote server.

Refer to the following articles to learn how to move OBAS database to a remote server:

Notes: Values used in the instructions below must be replaced with real ones:

pbas-db.provider.com – FQDN hostname of database server

98 - ID of remote database server (if it is a Virtuozzo container)

97 - ID of cloned remote database container (if vzmlocal is used for backup)

These instructions can be applied only to OBAS 4.3

On OBAS backend server:

  1. Upgrade OBAS installation to 4.3 release. Upgrade instructions can be found in the release notes (see the "Upgrade Instructions" chapter).

  2. Copy MySQL 5.0 RPM packages and required dependencies from the OBAS 4.3 release distributive to the remote database server:

    # scp mysql-5.0.77-4.el5_6.6.i386.rpm mysql-server-5.0.77-4.el5_6.6.1.i386.rpm perl-DBD-MySQL-4.021-2.i386.rpm perl-DBI-1.56-1.i386.rpm root@pbas-db.provider.com:/tmp/
    
  3. Stop OBAS services:

    # service servicemon stop
    # service vzcoll stop
    # service taskmand stop
    # service hspcd stop
    

On the remote database server pbas-db.provider.com:

  1. Back up the remote database server. If it is a Virtuozzo container, you can use a backup from VA, or Virtuozzo tools like "vzabackup" or "vzmlocal". The easiest way is to clone the container:

    # vzmlocal -C 98:97
    Moving/copying CT#98 -> CT#97
    Successfully completed
    
  2. Stop MySQL daemon on the remote server:

    # service mysql stop
    
  3. Erase the old MySQL 4.x RPM packages:

    # rpm -e MySQL-client-4.1.10-0 MySQL-shared-4.1.10-0 MySQL-server-4.1.10-0 MySQL-Max-4.1.10-0
    
  4. Install MySQL 5.0 RPM packages:

    # cd /tmp/
    # rpm -ihv mysql-5.0.77-4.el5_6.6.i386.rpm mysql-server-5.0.77-4.el5_6.6.1.i386.rpm perl-DBD-MySQL-4.021-2.i386.rpm perl-DBI-1.56-1.i386.rpm
    warning: /root/mysql-5.0.77-4.el5_6.6.i386.rpm: Header V3 DSA signature: NOKEY, key ID e8562897
    Preparing...                ########################################### [100%]
       1:perl-DBI               ########################################### [ 25%]
       2:mysql                  ########################################### [ 50%]
       mysql                  warning: /etc/my.cnf created as /etc/my.cnf.rpmnew
       3:perl-DBD-MySQL         ########################################### [ 75%]
       4:mysql-server           ########################################### [100%]
    
  5. Stop "mysqld" service (if it is running):

    # service mysqld stop
    
  6. Edit /etc/my.cnf file:

    • Comment "max_allowed_packet" in [client] section, if it exists
    • Add "innodb_rollback_on_timeout = 1" into [mysqld] section
  7. Update runlevel information for "mysqld" services:

    # chkconfig mysqld on
    # chkconfig --list | grep mysql
    mysqld          0:off   1:off   2:on    3:on    4:on    5:on    6:off
    
  8. Start "mysqld" service on remote DB server:

    # service mysqld start
    
  9. Run mysql_upgrade script:

    # mysql_upgrade
    Looking for 'mysql' as: mysql
    Looking for 'mysqlcheck' as: mysqlcheck
    Running 'mysqlcheck'...
    aspc.abstract_template
    error    : Table upgrade required. Please do "REPAIR TABLE `abstract_template`" to fix it!
    aspc.acc_balance
    error    : Table upgrade required. Please do "REPAIR TABLE `acc_balance`" to fix it!
    aspc.acc_event
    error    : Table upgrade required. Please do "REPAIR TABLE `acc_event`" to fix it!
    aspc.acc_plugin
    ...skipping...
    Repairing tables
    aspc.abstract_template                             OK
    aspc.acc_balance                                   OK
    aspc.acc_event                                     OK
    aspc.acc_plugin                                    OK
    ...skipping...
    Running 'mysql_fix_privilege_tables'...
    OK
    

On the OBA-S backend server, again:

Start OBAS services:

    # service vzcoll start
    # service taskmand start
    # service hspcd start
    # service servicemon start

Additional information

Move OBAS database to separate server (MySQL5)

How to migrate OBAS database to 64-bit system

70a5401e8b9354cd1d64d0346f2c4a3e caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 624ca542e40215e6f1d39170d8e7ec75

Email subscription for changes to this article
Save as PDF