Upgrading Db2 Big SQL from Version 4.7 to Version 5.0

Information you need to complete this task

Review the following information before you upgrade Db2 Big SQL:

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 Big SQL 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 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

Storage requirements

You don't need to specify storage when you upgrade Db2 Big SQL.

Before you begin

This task assumes that the following prerequisites are met:

Procedure

Complete the following tasks to upgrade Db2 Big SQL:

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

Upgrading the service

To upgrade Db2 Big SQL:

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 Big SQL.

   cpd-cli manage apply-cr \
   --components=bigsql \
   --release=${VERSION} \
   --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --license_acceptance=true \
   --upgrade=true

Validating the upgrade

[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=bigsql

Upgrading existing service instances

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

To upgrade the service instances:

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.

1. If you are upgrading Db2 Big SQL from Cloud Pak for Data 4.7.0, 4.7.1, or 4.7.2, in the Cloud Pak for Data instance project, disable FGAC:

   for headnode in $(oc get pods -l icpdsupport/podSelector==bigsql-compute,name==dashmpp-head-0 --no-headers -o custom-columns=POD:.metadata.name) ; 
   do 
       oc exec -ti -c db2u ${headnode} -- su - db2inst1 -c "db2 -td@ -f /opt/dv/current/build_time/fgac/dv-fgac-disable-ddl.sql ; echo FGAC disabled on ${headnode}" ; 
   done

   Expected output of the command:

   DB20000I  The SQL command completed successfully.

2. 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.
3. Get the list of Db2 Big SQL service instances:

   cpd-cli service-instance list \
   --service-type=bigsql \
   --profile=${CPD_PROFILE_NAME}

4. Set the INSTANCE_NAME environment variable to the name of the service instance that you want to upgrade:

   export INSTANCE_NAME=<instance-name>

5. Upgrade the service instance:

   cpd-cli service-instance upgrade \
   --service-type=bigsql \
   --instance-name=${INSTANCE_NAME} \
   --profile=${CPD_PROFILE_NAME}

6. Repeat the preceding steps to upgrade each service instance associated with this instance of Cloud Pak for Data.

Verifying the instance upgrade

oc get bigsql -l app.kubernetes.io/name=db2-bigsql

What to do next

After you upgrade your cluster to Red Hat OpenShift Container Platform Version 4.14 or later, Db2 Big SQL is ready to use. To get started with Db2 Big SQL, see Running SQL and exploring your service instance (Db2 Big SQL).