Pre-upgrade tasks

Before you upgrade to IBM® Db2® Data Management Console, you need to complete the pre-upgrade tasks.

Back up data of your repository database

Although upgrading to IBM Db2 Data Management Console does not affect the original data that is used by IBM Data Server Manager in the repository database, it is suggested to back up your repository database before you upgrade. Backing up data helps to protect your data in case you encounter an unexpected severe failure.

Upgrade the repository database if it does not meet the minimum version requirement

Check the type and version of your repository database. Currently, upgrade is supported for Db2 version 11.1 and later.

If the version of your repository database is earlier than Db2 v11.1, upgrade your database first.

Check disk space of repository database

When you upgrade to IBM Db2 Data Management Console, new tables are created and data in the repository database is migrated if you choose full data migration path. Check the disk space of your repository database, and make sure it has enough free disk space to complete all the processes.

Upgrade IBM Data Server Manager to the latest version

Check the version of your IBM Data Server Manager product.

Upgrade your IBM Data Server Manager product to the latest fix pack level (2.1.5.4) before you perform the upgrade.

Confirm the status of IBM Data Server Manager

IBM Data Server Manager is not required to be stopped before you begin the upgrade process. If you keep IBM Data Server Manager running, IBM Db2 Data Management Console helps you detect the installation path of your IBM Data Server Manager and its status whether it is running or stopped. You can also choose to start the IBM Db2 Data Management Console or not after the upgrade. However, you need to be aware of the following:
  • Avoid potential port conflict of two products. You can modify the default setup configuration before the upgrade if you want to keep both the products alive.
  • If IBM Data Server Manager is kept running, it will write data into repository database during and after the upgrade.
  • When the upgrade is completed, and if you keep both the products alive, be careful to avoid double-monitoring of databases.