Upgrading Watson Query from Version 4.7 to Version 4.8

Information you need to complete this task

Review the following information before you upgrade Watson Query:

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 4.8.9, you must upgrade Watson Query to Version 4.8.9.

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

Common core services

Watson Query requires the Cloud Pak for Data common core services.

If the common core services are not at the correct version in the operands project for the instance, the common core services are automatically upgraded when you upgrade Watson Query. The common core services upgrade increases the amount of time the upgrade takes to complete.

Storage requirements

You don't need to specify storage when you upgrade Watson Query.

Before you begin

If you are upgrading Watson Query from a version older than Cloud Pak for Data 4.8.2 to a version newer than 4.8.2, you must temporarily update the Duplicate asset handling settings of your catalogs to Allow duplicates. After the upgrade, you can revert the Duplicate asset handling configuration. For steps on updating this setting, see Changing catalog settings.

This task assumes that the following prerequisites are met:

Prerequisite services

Before you upgrade Watson Query, ensure that the following services are upgraded and running:

• Db2® Data Management Console: If you do not manually upgrade Db2 Data Management Console, Watson Query upgrades it for you. If you have already upgraded Db2 Data Management Console, make sure that a Db2 Data Management Console instance has been provisioned. For more information, see Upgrading Db2 Data Management Console.

Procedure

Complete the following tasks to upgrade Watson Query:

1. Upgrading the service
2. Validating the upgrade
3. Upgrading existing service instances
4. Upgrading any remote connectors that you installed
5. What to do next

Upgrading the service

To upgrade Watson Query:

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 Watson Query.

   cpd-cli manage apply-cr \
   --components=dv \
   --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=dv

Upgrading existing service instances

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

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. Change to the project where Watson Query pods are installed.

   oc project ${PROJECT_CPD_INST_OPERANDS}

3. Get the names of the Watson Query service instances:

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

   For more information about the service-instance list command, see service-instance list in the Cloud Pak for Data command-line interface reference.
4. Upgrade one instance at a time. For each instance that you want to upgrade, complete the following steps:
   1. Set the WQ_INSTANCE_NAME environment variable to the name of the instance that you want to upgrade:

      export WQ_INSTANCE_NAME=<instance-name>

   2. Set the AUDIT_PVC_SIZE environment variable:

      export AUDIT_PVC_SIZE=30Gi

   3. Verify that the STG_CLASS_FILE and CPD_PROFILE_NAME environment variables are set.
   4. Create an instance override file for the instance that you are upgrading. Use the file name dv_override_${WQ_INSTANCE_NAME}.yaml and include the following parameters:

      cat <<EOF > dv_override_${WQ_INSTANCE_NAME}.yaml
      parameters:
       workerCount: $(cpd-cli service-instance get ${WQ_INSTANCE_NAME} --service-type dv --profile=${CPD_PROFILE_NAME} | grep workerCount | cut -d':' -f2 | cut -d'"' -f2)
      
       resources.dv.requests.cpu: $(cpd-cli service-instance get ${WQ_INSTANCE_NAME} --service-type dv --profile=${CPD_PROFILE_NAME} | grep resources.dv.requests.cpu | cut -d':' -f2 | cut -d'"' -f2)
       resources.dv.requests.memory: $(cpd-cli service-instance get ${WQ_INSTANCE_NAME} --service-type dv --profile=${CPD_PROFILE_NAME} | grep resources.dv.requests.memory | cut -d':' -f2 | cut -d'"' -f2)
      
       persistence.storageClass: $(cpd-cli service-instance get ${WQ_INSTANCE_NAME} --service-type dv --profile=${CPD_PROFILE_NAME} | grep persistence.storageClass | cut -d':' -f2 | cut -d'"' -f2)
       persistence.size: $(cpd-cli service-instance get ${WQ_INSTANCE_NAME} --service-type dv --profile=${CPD_PROFILE_NAME} | grep persistence.size | cut -d':' -f2 | cut -d'"' -f2)
      
       persistence.cachingpv.storageClass: $(cpd-cli service-instance get ${WQ_INSTANCE_NAME} --service-type dv --profile=${CPD_PROFILE_NAME} | grep persistence.cachingpv.storageClass | cut -d':' -f2 | cut -d'"' -f2)
       persistence.cachingpv.size: $(cpd-cli service-instance get ${WQ_INSTANCE_NAME} --service-type dv --profile=${CPD_PROFILE_NAME} | grep persistence.cachingpv.size | cut -d':' -f2 | cut -d'"' -f2)
      
       persistence.auditpv.storageClass: ${STG_CLASS_FILE}
       persistence.auditpv.size: ${AUDIT_PVC_SIZE}
      EOF

      Important: A separate override file is required for each instance that you upgrade. The file contains instance-specific settings. You must upgrade one instance at a time to ensure that override file for each instance is applied correctly.
   5. Open the override file and verify that it is complete.

      Warning: The upgrade fails if the override file does not contain values for all of the parameters.

      The following example shows an override file with the parameter values set:

      parameters:
       workerCount: 1
      
       resources.dv.requests.cpu: 4
       resources.dv.requests.memory: 16Gi
      
       persistence.storageClass: nfs-client
       persistence.size: 50Gi
      
       persistence.cachingpv.storageClass: nfs-client
       persistence.cachingpv.size: 50Gi
      
       persistence.auditpv.storageClass: nfs-client
       persistence.auditpv.size: 30Gi

   6. Run the following command to upgrade the instance:

      cpd-cli service-instance upgrade \
      --instance-name=${WQ_INSTANCE_NAME} \
      --service-type=dv \
      --profile=${CPD_PROFILE_NAME} \
      --override dv_override_${WQ_INSTANCE_NAME}.yaml
      

      Important:

      The upgrade fails if one or more of the following scenarios is true:

      • You do not include the override file when you run the upgrade command.
      • The override file has sections without values.
      • You do not specify a file storage class that supports ReadWriteMany (RWX) for ${STG_CLASS_FILE} in the persistence.auditpv.storageClass: ${STG_CLASS_FILE} part of the override file.
   7. Run one of the following commands to verify that the version now reads 2.2.8 for the upgraded instances:

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

      • oc get bigsql db2u-dv -o jsonpath='{.status.version}{"\n"}'

Wait until the instance upgrades are complete before you proceed to the next step.

Upgrading remote connectors

What to do next

1. After you upgrade, all active or inactive caches with refresh schedules are reset. You must edit the active caches and set the refresh rate again. For more information, see Adding data caches in Watson Query.

Watson Query is ready to use. For more information, see Virtualizing data with Watson Query.