4.258
Sometimes when upgrading from an older version of Moab to a newer version, you must update your database schema. If the schema Moab expects to operate against is different from the actual schema of the database Moab is connected to, Moab might not be able to use the database properly and data might be lost.
When upgrading the Moab database schema from an old version, you must perform each version upgrade in order. You cannot skip versions.
If upgrading a Moab version prior to 7.2.0, contact Adaptive Computing.
Complete the following as needed:
- Migrate from Moab 7.2.0-7.2.5 to Moab 7.2.6
- Migrate from Moab 7.2.6-7.2.10 to Moab 7.5
- Migrate from Moab 7.5 to Moab 8.0
- Migrate from Moab 8.0 to Moab 8.1 and after
4.258.1 Migrate from Moab 8.0 to Moab 8.1 and after
In Moab Workload Manager 8.1, a new accounting event 'AMCONTINUE was added and the datatypes of some reservation statistics were changed. To upgrade your database with these changes, use the moab-db-<database>-upgrade8_1.sql file located in the contrib/sql directory.
This contrib/sql directory is either in the $MOABHOMEDIR (if you used RPM method) or in the expanded tarball directory (if you used Manual method).
For example, to migrate your MySQL database from the 8.0 (or later) schema, run the following:
[root@]# mysql -u root -D <database name> -p < moab-db-mysql-upgrade8_1.sql
The database name is usually 'Moab'.
Similar migration scripts exist for Oracle and PostgreSQL.
4.258.2 Migrate from Moab 7.5 to Moab 8.0
In Moab Workload Manager 8.0, column names that have become reserved words in newer versions of MySQL, PostgreSQL, and Oracle were renamed to eliminate the need to quote column names in SQL statements. Also, a few additional columns were added to existing tables to support Moab's Green feature. To upgrade your database with these changes, use the moab-db-<database>-upgrade8_0.sql file located in the contrib/sql directory.
This contrib/sql directory is either in the $MOABHOMEDIR (if you used RPM method) or in the expanded tarball directory (if you used Manual method).
For example, to migrate your MySQL database from the 7.5 (or later) schema, run the following:
[root@]# mysql -u root -D <database name> -p < moab-db-mysql-upgrade8_0.sql
The database name is usually "Moab".
Similar migration scripts exist for Oracle and PostgreSQL.
4.258.3 Migrate from Moab 7.2.6-7.2.10 to Moab 7.5
In Moab Workload Manager 7.5, column names that are reserved words in databases supported by Adaptive Computing were renamed to eliminate the need to quote column names in SQL statements. To upgrade your database with these changes, use the moab-db-<database>-upgrade7_5.sql file located in the contrib/sql directory.
This contrib/sql directory is either in the $MOABHOMEDIR (if you used RPM method) or in the expanded tarball directory (if you used Manual method).
For example, to migrate your MySQL database from the 7.2.6 (or later) schema, run the following:
[root@]# mysql -u root -D <database name> -p < moab-db-mysql-upgrade7_5.sql
The database name is usually "Moab".
Similar migration scripts exist for Oracle and PostgreSQL.
4.258.4 Migrate from Moab 7.2.0-7.2.5 to Moab 7.2.6
In Moab Workload Manager 7.2.6, several columns were extended and the primary key on the Triggers table changed. To upgrade your database with these changes, use the moab-db-<database>-upgrade7_2_6.sql file located in the contrib/sql directory.
This contrib/sql directory is either in the $MOABHOMEDIR (if you used RPM method) or in the expanded tarball directory (if you used Manual method).
For example, to migrate your MySQL database from the 7.2.x (pre-7.2.6) schema to the 7.2.6 schema, run the following:
[root@]# mysql -u root -D <database name> -p < moab-db-mysql-upgrade7_2_6.sql
The database name is usually "Moab".
Similar migration scripts exist for Oracle and PostgreSQL.
The 7.2.6 database upgrade is compatible with all earlier versions of 7.2.