Upgrades

The following figure illustrates the possible upgrade paths for AVEVA Enterprise Resource Management:

You can automatically upgrade within a major version or to the next version using the upgrade paths as displayed in the figure. However, upgrades across multiple major versions is not supported. You can only upgrade from the previous major version.

For example: A 17.x version is upgraded to 18.x using an 18.x installation package, afterwards the 18.x version is upgraded to a 19.x version using a 19.x installation package.

Note: You must upgrade your current major version only to a minor/service pack version that is supported for major version migration (see the green and red arrows in the figure).

Minor, Service Pack, and Hotfix Version Upgrade

The first version number is unchanged in a minor, service pack, and hotfix version upgrades, for example 19.0.1.0 to 19.1.0.0.

To upgrade from a previous version to the current version within the same major version, perform the following:

1. Deploy AVEVA Enterprise Resource Management Application Server components for Application Server environment

   • To upgrade the AVEVA Enterprise Resource Management application server components and apply change scripts to the database schema, run AVEVA Enterprise Resource Management Deployment Manager (Deploy Application Server).

2. Install AVEVA Enterprise Resource Management Desktop Client

   • Run the Client MSI installer on the client machines, including the same SERVERHOST and SERVERPORT parameters as used during initial installation.

Upgrade Behaviour

For minor, service pack, and hotfix version upgrades, all the existing components are upgraded in-place and overwrite the previously installed version.

Major Version Upgrade

The first version number is changed in a major version upgrade, for example: 18.1.1.0 to 19.0.0.0.

Perform the same steps as for Minor, Service Pack, and Hotfix Version Upgrade, however also perform the database tasks.

Database Upgrade

For information on the database actions for major version upgraded, see Database actions for major version upgrades.

• Backup: Before updating, create a backup of the current AVEVA Enterprise Resource Management database schema or create a copy of the current schema and use the copy to upgrade.

• Rebuild Indexes: To keep performance optimal in the Oracle database, rebuild all indexes in the database periodically. Rebuilding all indexes in the database is recommended after each version upgrade.

Upgrade Behaviour

For a major version, different parts of the AVEVA Enterprise Resource Management is upgraded as follows:

• Client: For a major version upgrade, the AVEVA Enterprise Resource Management client is installed as a new application along with the previous version (since the product codes are different), so when the previous version is no longer required you can uninstall that version using the general MSI approach.

• Application Server: For a major version upgrade, the AVEVA Enterprise Resource Management application server upgrades any previously installed versions when using the same environment name. If the new major version is installed along with the previous version, then use a new environment name, for example, Test19 instead of Test18.

• Database: For a major version upgrade, the AVEVA Enterprise Resource Management database schema is upgraded in-place, so create a backup and import that into a new schema.