Upgrading Db2 Data Management Console from Version 4.0 to Version 4.6

A project administrator can upgrade Db2 Data Management Console from Cloud Pak for Data Version 4.0 to Version 4.6.

Important: To complete this task, you must be running Db2 Data Management Console Version 4.0.2 or later. (Version 4.0.2 was released with Cloud Pak for Data Version 4.0 Refresh 2.)
Supported upgrade paths
If you are running Db2 Data Management Console Version 4.0.2 or later, you can upgrade to Versions 4.6.0 - 4.6.2.
Unsupported upgrade paths
You cannot upgrade from Version 4.0 to Version 4.6.3 or later. You must upgrade to 4.6.2 before you upgrade to 4.6.3 or later.
What permissions do you need to complete this task?
The permissions that you need depend on which tasks you must complete:
  • To update the Db2 Data Management Console operators, you must have the appropriate permissions to create operators and you must be an administrator of the project where the Cloud Pak for Data operators are installed. This project is identified by the ${PROJECT_CPD_OPS} environment variable.
  • To upgrade Db2 Data Management Console, you must be an administrator of the project where Db2 Data Management Console is installed. This project is identified by the ${PROJECT_CPD_INSTANCE} environment variable.
When do you need to complete this task?
If you didn't upgrade Db2 Data Management Console when you upgraded the platform, you can complete this task to upgrade your existing Db2 Data Management Console installation.

If you want to upgrade all of the Cloud Pak for Data components at the same time, follow the process in Upgrading the platform and services instead.

Important: All of the Cloud Pak for Data components in a deployment must be installed at the same release.

Information you need to complete this task

Review the following information before you upgrade Db2 Data Management Console:

Environment variables
The commands in this task use environment variables so that you can run the commands exactly as written.
  • If you don't have the script that defines the environment variables, see Setting up installation environment variables.
  • To use the environment variables from the script, you must source the environment variables before you run the commands in this task, for example:
    source ./cpd_vars.sh
Installation location
Db2 Data Management Console is installed in the same project (namespace) as the Cloud Pak for Data control plane. This project is identified by the ${PROJECT_CPD_INSTANCE} environment variable.
Storage requirements
You don't need to specify storage when you upgrade Db2 Data Management Console.

Before you begin

This task assumes that the following prerequisites are met:

Prerequisite Where to find more information
The cluster meets the minimum requirements for Db2 Data Management Console. If this task is not complete, see System requirements.
The workstation from which you will run the upgrade is set up as a client workstation and includes the following command-line interfaces:
  • Cloud Pak for Data CLI: cpd-cli
  • OpenShift® CLI: oc
If this task is not complete, see Setting up a client workstation.
The Cloud Pak for Data control plane is upgraded. If this task is not complete, see Upgrading the platform and services.
For environments that use a private container registry, such as air-gapped environments, the Db2 Data Management Console software images are mirrored to the private container registry. If this task is not complete, see Mirroring images to a private container registry.

Procedure

Complete the following tasks to upgrade Db2 Data Management Console:

  1. Logging in to the cluster
  2. Updating the operator
  3. Upgrading the service
  4. Validating the upgrade
  5. Upgrading the service instance
  6. What to do next

Logging in to the cluster

To run cpd-cli manage commands, you must log in to the cluster.

To log in to the cluster:

  1. Run the cpd-cli manage login-to-ocp command to log in to the cluster as a user with sufficient permissions to complete this task. For example:
    cpd-cli manage login-to-ocp \
    --username=${OCP_USERNAME} \
    --password=${OCP_PASSWORD} \
    --server=${OCP_URL}
    Tip: The login-to-ocp command takes the same input as the oc login command. Run oc login --help for details.

Updating the operator

The Db2 Data Management Console operator simplifies the process of managing the Db2 Data Management Console service on Red Hat® OpenShift Container Platform.

To upgrade Db2 Data Management Console, ensure that all of the Operator Lifecycle Manager (OLM) objects in the ${PROJECT_CPD_OPS} project, such as the catalog sources and subscriptions, are upgraded to the appropriate release. All of the OLM objects must be at the same release.

Who needs to complete this task?
You must be a cluster administrator (or a user with the appropriate permissions to install operators) to create the OLM objects.
When do you need to complete this task?
Complete this task only if the OLM artifacts have not been updated for the current release using the cpd-cli manage apply-olm command with the --upgrade=true option.

It is not necessary to run this command multiple times for each service that you plan to upgrade. If you complete this task and the OLM artifacts already exist on the cluster, the cpd-cli will recreate the OLM objects for all of the existing components in the ${PROJECT_CPD_OPS} project.

To update the operator:

  1. Update the OLM objects:
    cpd-cli manage apply-olm \
    --release=${VERSION} \
    --cpd_operator_ns=${PROJECT_CPD_OPS} \
    --upgrade=true
    • If the command succeeds, it returns [SUCCESS]... The apply-olm command ran successfully.
    • If the command fails, it returns [ERROR] and includes information about the cause of the failure.

What to do next: Upgrade the Db2 Data Management Console service.

Note: After the OLM objects are updated, if the Db2 Data Management Console custom resource status is failed, an error might occur. To resolve the issue, you can upgrade the Db2 Data Management Console service.

Upgrading the service

After the Db2 Data Management Console operator is updated, you can upgrade Db2 Data Management Console.

Who needs to complete this task?
You must be an administrator of the project where Db2 Data Management Console is installed.
When do you need to complete this task?
Complete this task for each instance of Db2 Data Management Console that is associated with an instance of Cloud Pak for Data Version 4.6.

To upgrade the service:

  1. Update the custom resource for Db2 Data Management Console.
    cpd-cli manage apply-cr \
    --components=dmc \
    --release=${VERSION} \
    --cpd_instance_ns=${PROJECT_CPD_INSTANCE} \
    --license_acceptance=true \
    --upgrade=true

Validating the upgrade

Db2 Data Management Console is upgraded when the apply-cr command returns [SUCCESS]... The apply-cr command ran successfully.

However, you can optionally run the cpd-cli manage get-cr-status command if you want to confirm that the custom resource status is Completed:

cpd-cli manage get-cr-status \
--cpd_instance_ns=${PROJECT_CPD_INSTANCE} \
--components=dmc

Upgrading the service instance

After you upgrade Db2 Data Management Console, you must upgrade the service instance that is associated with Db2 Data Management Console.

To upgrade the service instance:

  1. Get the Db2® Data Management Console instance name.
    oc get dmc -n ${PROJECT_CPD_INSTANCE}
  2. Edit the Db2 Data Management Console instance.
    oc edit dmc {instance-name} -n ${PROJECT_CPD_INSTANCE}
  3. Change the version to 4.6.4.
    cat << EOF | oc apply -f -
    apiVersion: dmc.databases.ibm.com/v1
    kind: Dmc
    spec:
      arch: x86_64
      version: 4.6.4
      description: "Data Management Console"
      scaleConfig: small
      storageClass: "YOUR_STORAGECLASS"
      storageSize: 10Gi   
      license:
        accept: true 
        license: Standard   
    EOF
  4. Save your changes and exit.

What to do next

Db2 Data Management Console is ready to use.