Upgrading Data Virtualization from Version 4.8 to Version 5.0

Information you need to complete this task

Review the following information before you upgrade Data Virtualization:

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 Data Virtualization 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

Common core services

Data Virtualization 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 Data Virtualization. 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 Data Virtualization.

Before you begin

This task assumes that the following prerequisites are met:

Prerequisite services

Before you upgrade Data Virtualization, ensure that the following services are upgraded and running:

• Db2 Data Management Console: If you do not manually upgrade Db2 Data Management Console, Data Virtualization 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 Data Virtualization:

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

Upgrading the service

To upgrade Data Virtualization:

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 Data Virtualization.

   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 Data Virtualization, you must upgrade any service instances that are associated with Data Virtualization.

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 Data Virtualization pods are installed.

   oc project ${PROJECT_CPD_INST_OPERANDS}

3. Get the list of Data Virtualization service instances:

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

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 service instance that you want to upgrade:

      export WQ_INSTANCE_NAME=<instance-name>

   2. 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}

   3. Run one of the following commands to verify that the version now reads 3.0.3 for the upgraded instances:

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

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

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

Upgrading remote connectors

If you installed remote connectors, you can upgrade the remote connectors by using the UPDATEREMOTECONNECTOR stored procedure. You run this procedure by using the SQL editor or the Db2 console on the cluster.

• To update all remote connectors, run the following stored procedure.

  call dvsys.updateremoteconnector('',?,?)

• If you need to upgrade a set of remote connectors, pass in a comma-separated list.

  call dvsys.updateremoteconnector('<REMOTE_CONNECTOR_NODES>',?,?)

  1. In the datavirtualization.env file, change the export JAVA_HOME file path to the Java 21 JRE file path.

     export JAVA_HOME=<Java 21 JRE file path>

  2. Start the agent by running this Linux® command:

     nohup ./datavirtualization_start.sh &

• You can obtain the <REMOTE_CONNECTOR_NODES> by running the following command.

  select node_name from dvsys.listnodes where AGENT_CLASS='R'

What to do next

1. After you upgrade to Data Virtualization on Cloud Pak for Data version 5.0.3, you must manually edit data sources that use SSL connections. Otherwise, the data sources are invalid and your queries on the data will fail. Complete the following steps to edit the SSL-enabled data sources so that they are valid for use:

   1. On the Data Virtualization Data sources page, find the SSL-enabled data sources that show a status of Invalid.
   2. Complete the following steps to edit each invalid data source:
      1. Select Edit connection at the end of the data source row.
      2. Make a minor change to the name or description, but don’t change any other values.
      3. Save the change to trigger an update to the data source.
      The data sources that you edited are now valid and you can proceed to use them in your queries.

2. 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 Data Virtualization.

Data Virtualization is ready to use. For more information, see Virtualizing data.