Upgrading Db2 from Version 5.1 to Version 5.3

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 IBM Software Hub must be installed at the same release. For example, if the IBM Software Hub control plane is at Version 5.3.0, you must upgrade Db2 to Version 5.3.0.

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, run:

  source ./cpd_vars.sh

Before you begin

This task assumes that the following prerequisites are met:

System requirements

This task assumes that the cluster meets the minimum requirements for Db2.

Where to find more information
If this task is not complete, see System requirements.

Workstation

This task assumes that the workstation from which you will run the upgrade is set up as a client workstation and has the following command-line interfaces:

• IBM Software Hub CLI: cpd-cli
• OpenShift® CLI: oc
• Helm CLI: oc

Where to find more information
If this task is not complete, see Updating client workstations.

Control plane

This task assumes that the IBM Software Hub control plane is upgraded.

Where to find more information
If this task is not complete, see Upgrading an instance of IBM Software Hub.

Private container registry

If your environment uses a private container registry (for example, your cluster is air-gapped), this task assumes that the following tasks are complete:

1. The Db2 software images are mirrored to the private container registry.

   Where to find more information
   If this task is not complete, see Mirroring images to a private container registry.

2. The cpd-cli is configured to pull the olm-utils-v4 image from the private container registry.

   Where to find more information
   If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry.

Cluster-scoped resources

This task assumes that the cluster-scoped resources, such as custom resource definitions, cluster roles, and cluster role bindings, were updated.

Where to find more information
If this task is not complete, see Updating the cluster-scoped resources for the platform and services.

Image pull secrets

This task assumes that the secrets that contain the image pull credentials for the instance exist.

Where to find more information
If this task is not complete, see Creating image pull secrets for an instance of IBM Software Hub.

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

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 operator and custom resource for Db2.

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=db2oltp \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET} \
   --upgrade=true

Validating the upgrade

[SUCCESS]... The install-components 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

If you have previously upgraded your license, see Upgrading the license before you deploy Db2 to upgrade to Db2 12.1.

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

The profile must be associated with a IBM Software Hub 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. Monitor your Db2uCluster or Db2uInstance status to check if the custom resource state changes to Not Ready and then to Ready state:
   • For Db2uCluster custom resource, run the following command:

     oc get db2ucluster <instance_id> -o jsonpath='{.status.state} {"\n"}'

   • For Db2uInstance custom resource, run the following command:

     oc get db2uinstance <instance_id> -o jsonpath='{.status.state} {"\n"}'

   If the custom resource state returns as UpgradeCheckFailed, see troubleshooting db2ckupgrade issues.
6. Verify that the service instance is upgraded and is ready to use.
7. Repeat the preceding steps to upgrade each service instance associated with this instance of IBM Software Hub.

Verifying the service instance upgrade

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

Command

1. Get your Db2uCluster or Db2uInstance status. Wait for the status to change to Ready:
   • For Db2uCluster custom resource, run the following command:

     oc get db2ucluster <instance_id> -o jsonpath='{.status.state} {"\n"}'

   • For Db2uInstance custom resource, run the following command:

     oc get db2uinstance <instance_id> -o jsonpath='{.status.state} {"\n"}'

2. Check the status of your Db2 service instance:

   cpd-cli service-instance status ${INSTANCE_NAME} \
   --profile=${CPD_PROFILE_NAME} \
   --service-type=db2oltp

3. Check if the service instance is 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

You must complete Post-installation setup for the Db2 service before users can access Db2.