Installing Db2 Big SQL

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

Important: Db2 Big SQL is not supported on Red Hat® OpenShift® Container Platform Version 4.12. You must ensure your cluster is running Red Hat OpenShift Container Platform Version 4.14 or later.

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.1.3, you must install Db2 Big SQL at Version 5.1.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
```

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:

Prerequisite	Where to find more information
The cluster meets the minimum requirements for installing Db2 Big SQL.	If this task is not complete, see System requirements.
The workstation from which you will run the installation is set up as a client workstation and includes the following command-line interfaces: IBM Software Hub CLI: `cpd-cli` OpenShift CLI: `oc`	If this task is not complete, see Setting up a client workstation.
The IBM Software Hub control plane is installed.	If this task is not complete, see Installing an instance of IBM Software Hub.
For environments that use a private container registry, such as air-gapped environments, the Db2 Big SQL software images are mirrored to the private container registry.	If this task is not complete, see Mirroring images to a private container registry.
For environments that use a private container registry, such as air-gapped environments, the `cpd-cli` is configured to pull the `olm-utils-v3` image from the private container registry.	If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry.
The custom security context constraint (SCC) for Db2 Big SQL exists.	If this task is not complete, see Creating the custom security context constraint for embedded Db2 databases.
The process IDs limit setting is adjusted for Db2 Big SQL.	If this task is not complete, see Changing the process IDs limit.
The kernel parameter settings are adjusted for Db2 Big SQL.	If this task is not complete, see Changing kernel parameter settings.

Procedure

Complete the following tasks to install Db2 Big SQL:

Installing the service
Validating the installation
What to do next

Installing the service

To install Db2 Big SQL:

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.
Run the following command to create the required OLM objects for Db2 Big SQL in the operators project for the instance:
```
cpd-cli manage apply-olm \
--release=${VERSION} \
--cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
--components=bigsql
```
Wait for the cpd-cli to return the following message before you proceed to the next step:
```
[SUCCESS]... The apply-olm command ran successfully
```
If the apply-olm fails, see Troubleshooting the apply-olm command during installation or upgrade.

Create 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

Validating the installation

Db2 Big SQL is installed when the apply-cr command returns:

[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

What to do next

Complete post-installation setup.