Upgrading Db2 from Version 4.8.x to Version 5.0

An instance administrator can upgrade Db2 from Cloud Pak for Data Version 4.8 to Version 5.0.

Who needs to complete this task?

Instance administrator To upgrade Db2, you must be an instance administrator. An instance administrator has permission to manage software in the following projects:

The operators project for the instance

The operators for this instance of Db2 are installed in the operators project. In the upgrade commands, the ${PROJECT_CPD_INST_OPERATORS} environment variable refers to the operators project.

The operands project for the instance

The custom resources for the control plane and Db2 are installed in the operands project. In the upgrade commands, the ${PROJECT_CPD_INST_OPERANDS} environment variable refers to the operands project.

When do you need to complete this task?

Review the following options to determine whether you need to complete this task:

  • If you want to upgrade the Cloud Pak for Data control plane and one or more services at the same time, follow the process in Upgrading an instance of Cloud Pak for Data instead.
  • If you didn't upgrade Db2 when you upgraded the Cloud Pak for Data control plane, complete this task to upgrade Db2.

    Repeat as needed If you are responsible for multiple instances of Cloud Pak for Data, you can repeat this task to upgrade more instances of Db2 on the cluster.

Information you need to complete this task

Review the following information before you upgrade Db2:

Version requirements

All the components that are associated with an instance of Cloud Pak for Data must be installed at the same release. For example, if the Cloud Pak for Data control plane is at Version 5.0.3, you must upgrade Db2 to Version 5.0.3.

Environment variables
The commands in this task use environment variables so that you can run the commands exactly as written.
  • If you do not 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, run:
    source ./cpd_vars.sh
Storage requirements
You don't need to specify storage when you upgrade Db2.

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. 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 has the following command-line interfaces:
  • Cloud Pak for Data CLI: cpd-cli
  • OpenShift® CLI: oc
 If this task is not complete, see Updating client workstations.
The Cloud Pak for Data control plane is upgraded. If this task is not complete, see Upgrading an instance of Cloud Pak for Data.
For environments that use a private container registry, such as air-gapped environments, the Db2 software images are mirrored to the private container registry. If this task is not complete, see Mirroring images to a private container registry.
For environments that use a private container registry, such as air-gapped environments, the cpd-cli is configured to pull the olm-utils-v3 image from the private container registry. If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry.
If you plan to use features that require GPUs, the operators required to use GPUs are installed. If this task is not complete, see Installing operators for services that require GPUs.

Procedure

Complete the following tasks to upgrade Db2:

  1. Upgrading the service
  2. Validating the upgrade
  3. Upgrading existing service instances
  4. Verifying the service instance upgrade
  5. What to do next

Upgrading the service

Important: The Operator Lifecycle Manager (OLM) objects for Db2 were updated when you upgraded the Cloud Pak for Data platform. The cpd-cli manage apply-olm updates all of the OLM objects in the operators project at the same time.

To upgrade Db2:

  1. Log the cpd-cli in to the Red Hat® OpenShift Container Platform cluster:
    ${CPDM_OC_LOGIN}
    Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.
  2. Update the custom resource for Db2.
    cpd-cli manage apply-cr \
--components=db2oltp \
--release=${VERSION} \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--license_acceptance=true \
--upgrade=true

Validating the upgrade

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

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

cpd-cli manage get-cr-status \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=db2oltp

Upgrading existing service instances

After you upgrade Db2, you must upgrade any service instances that are associated with Db2.

Before you begin

Create a profile on the workstation from which you will upgrade the service instances.

The profile must be associated with a Cloud Pak for Data user who has either the following permissions:

  • Create service instances (can_provision)
  • Manage service instances (manage_service_instances)

For more information, see Creating a profile to use the cpd-cli management commands.

Remove custom patches and override scripts, if applicable:
  1. Log in to Red Hat OpenShift Container Platform as a user with sufficient permissions to complete the task:
    oc login OpenShift_URL:port
  2. Run the following command to remove custom patches and override scripts:
    oc set volume statefulset/c-${DB2U_ID}-db2u -n ${PROJECT_CPD_INST_OPERANDS} --remove --name=<volume_name>
Procedure

To upgrade the service instances:

  1. Get the list of Db2 service instances:
    cpd-cli service-instance list \
--service-type=db2oltp \
--profile=${CPD_PROFILE_NAME}
  2. Set the INSTANCE_NAME environment variable to the name of the service instance that you want to upgrade:
    export INSTANCE_NAME=<instance-name>
  3. Run the following command to check whether your Db2 service instances is in running state:
    cpd-cli service-instance status ${INSTANCE_NAME} \
--profile=${CPD_PROFILE_NAME} \
--service-type=db2oltp
  4. Upgrade the service instance:
    cpd-cli service-instance upgrade \
--service-type=db2oltp \
--instance-name=${INSTANCE_NAME} \
--profile=${CPD_PROFILE_NAME}
  5. Repeat the preceding steps to upgrade each service instance associated with this instance of Cloud Pak for Data.

Verifying the service instance upgrade

You can use a command or the web console to verify that the service instance was upgraded and is ready to use.

Command
Run the following command and wait for the status to change to Ready:
oc get db2ucluster <instance_id> -o jsonpath='{.status.state} {"\n"}'
Run the following command to check the status of your Db2 service instances: 
cpd-cli service-instance status ${INSTANCE_NAME} \
--profile=${CPD_PROFILE_NAME} \
--service-type=db2oltp
Run the following command to check that the service instances have updated:
cpd-cli service-instance list \
--profile=${CPD_PROFILE_NAME}\
--service-type=db2oltp
Web console
From the Database details page, wait for the database version to change.

What to do next

Attention: If you have a Q Replication deployment, you need to exchange TLS certificates after upgrading. For more information, see Trusting targets and exchanging Db2 TLS certificates.

Review Post-installation setup for the Db2 service to determine whether any tasks need to be completed before users can access the Db2 service.