Installing Db2 Big SQL

An instance administrator can install Db2® Big SQL on IBM® Software Hub Version 5.4.

Who needs to complete this task?

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

The operators project for the instance

The operators for this instance of Db2 Big SQL are installed in the operators project.

In the installation 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 Big SQL are installed in the operands project.

In the installation 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 install multiple services at the same time, follow the process in Running a batch installation of solutions and services instead.
  • If you didn't install Db2 Big SQL as part of a batch installation, complete this task to add Db2 Big SQL to your environment.

    Repeat as needed If you are responsible for multiple instances of IBM Software Hub, you can repeat this task to install more instances of Db2 Big SQL on the cluster.

Information you need to complete this task

Review the following information before you install Db2 Big SQL:

Version requirements

All of 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 installed at Version 5.4.0, you must install Db2 Big SQL at Version 5.4.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
Security context constraint

Db2 Big SQL requires a custom security context constraint (SCC). For more information, see Creating the custom security context constraint for embedded Db2 databases.

Storage requirements
You don't need to specify storage information when you install Db2 Big SQL. However, you do need to specify storage when you provision an instance of Db2 Big SQL.

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 Big SQL.
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 installation 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: helm
Where to find more information
If this task is not complete, see Setting up a client workstation.
Control plane
This task assumes that the IBM Software Hub control plane is installed.
Where to find more information
If this task is not complete, see Installing 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 Big SQL 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-v4 image from the private container registry.
Custom SCC
This task assumes that the custom security context constraint (SCC) for Db2 Big SQL exists.
Where to find more information
If this task is not complete, see Creating the custom security context constraint for embedded Db2 databases.
Process IDs limit
The process IDs limit setting is adjusted for Db2 Big SQL.
Where to find more information
If this task is not complete, see Changing the process IDs limit.
Kernel parameters
The kernel parameter settings are adjusted for Db2 Big SQL.
Where to find more information
If this task is not complete, see Changing kernel parameter settings.

Procedure

Complete the following tasks to install Db2 Big SQL:

  1. Installing the service
  2. Validating the installation
  3. What to do next

Installing the service

To install 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. Install the operator and custom resource for Db2 Big SQL.
    cpd-cli manage install-components \
--license_acceptance=true \
--components=bigsql \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--operator_ns=${PROJECT_CPD_INST_OPERATORS} \
--instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--image_pull_prefix=${IMAGE_PULL_PREFIX} \
--image_pull_secret=${IMAGE_PULL_SECRET}

Validating the installation

Db2 Big SQL is installed when the install-components command returns:
[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=bigsql

What to do next

Complete post-installation setup.