Upgrading Integrated Analytics System

Read this section if you plan to upgrade your IAS platform to a newer version. Starting with version 1.0.9.0, you can perform the upgrade by yourself using the apupgrade utility.

Before you upgrade, always read the release notes to be aware of all prerequisites and known issues for your particular release. Cumulative release notes can be found in Release notes.

Note:

A full upgrade is needed by the 4^th version. For example, if you are on version on 1.0.21.0. you can perform partial upgrades to 1.0.22.1, 1.0.23.2 and 1.0.24.0 with apupgrade --security or apupgrade --essentials. The upgrade to 1.0.25.0 must be a full one. When upgrading to IAS 1.0.26, you must do a full upgrade.
If you are upgrading to IAS 1.0.26.0 with Windows AD or a custom bluadmin group name, see Upgrading to IAS 1.0.26 or Db2 Warehouse 11.5.6 with a custom bluadmin group name.

The apupgrade utility can be used to manage Integrated Analytics System software bundles, and initiate upgrades to a specific software level, but also inspect potential upgrades, and run preliminary upgrade readiness checks.

The preparation steps that you need to run before the actual upgrade are described in Preparation steps. Note that it might take significant time to fix any potential issues, so it is important to run the described pre-checks well ahead of the upgrade window.

Basic help for the apupgrade script can be acquired by running the command:

apupgrade --help

Typical use case help can be acquired by running the command:

apupgrade --typical-help

Detailed help and descriptions can be acquired by running the command:

apupgrade --detailed-help

Note: You must be logged in as apuser to run apupgrade.

Select parameters:

--upgrade-apupgrade: Allows you to upgrade the apupgrade RPM so that you can get the latest upgrade options that are available in the package.
--security and --essentials: Applies only security related fixes on top of a full release. The base IAS version cannot go back more than 3 full versions. The --essentials and --security features are interdependent. For example, if the base version is 1.0.22.1 and a 1.0.24.0 --essentials is applied, a 1.0.23.0 --security isn't allowed. The security version is required to be no more than 3 times greater than the base version and must be at least equal to any --essentials applied. The same requirement should be there for essentials in the other direction as well, it cannot be applied as a version lower than any applied security option.

--database-and-console: Upgrades just the container and is to be used primarily for special builds. This option allows you to upgrade to special builds and not require support. The path parameter is required.