Deploying Db2 Warehouse using the Db2uCluster custom resource

Once the Db2 Operator is installed, the Db2uCluster custom resource (CR) provides the interface required to deploy Db2 Warehouse. This CR is supported by an OpenShift Custom Resource definition.

You can use the Db2uCluster CR to complete the following tasks:

Accessing the Db2uCluster custom resource

You deploy Db2 Warehouse by running Db2uCluster CR commands through a YAML script. You can do this in several ways:
  • Through the Red Hat® OpenShift® console.
  • Through the Red Hat OpenShift command-line tool.
  • Through the command-line tool of a Kubernetes cluster.
To use the Red Hat OpenShift console, go to Installed Operators > IBM Db2 and click the Db2uCluster tab. Through this tab page you create your Db2 Warehouse instance, either by following the on-screen instructions of the form view, or by entering and running the YAML script.

The following sections cover CR options that can be included in the YAML file. An example of a completed Db2uCluster CR is also included.

Configure the Db2 Warehouse version

Specifies the version of the Db2 Warehouse database based on the Db2 Operator installed.
spec:
  version: "s11.5.9.0-cn<container layer release number>"

For a list of Db2 Operator versions, see Table 1 of Db2 on Red Hat OpenShift.

Configure the database name

Specifies the name of the desired Db2 Warehouse database.

The following example shows how to configure the database name: 
spec:
  environment:
    database:
      name: bludb

Deploy on a dedicated node

Specifies how to target labels on specific nodes for dedicated deployments. Deploying on dedicated nodes is a best practice in production. See Setting up dedicated nodes for your Db2 deployment.

The following example shows how to deploy a dedicated node:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: database
            operator: In
            values:
            - db2u-affinity
  tolerations:
  - effect: NoSchedule
    key: database
    operator: Equal
    value: db2u-affinity

Configure memory and CPU consumption

When deploying Db2 Warehouse using the Db2 Operator, you can assign a CPU and Memory profile. This assign CPU/MEM values to the container running the Db2 Common SQL Engine.

The following example shows how set memory and CPU limits for your Db2 Warehouse instance:
spec:
  podConfig:
    db2u:
      resource:
        db2u:
          limits:
            cpu: 2
            memory: 4Gi

Configure storage

Configure separate storage areas for the following storage categories:
Note: With certain storage solutions, the same storage class can be specified for both.
For example,
spec:
  storage:
  - name: meta
    spec:
      accessModes:
      - ReadWriteMany
      resources:
        requests:
          storage: 100Gi
      storageClassName: ocs-storagecluster-cephfs
    type: create
  - name: data
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 100Gi
      storageClassName: ocs-storagecluster-ceph-rbd
    type: template
  - name: activelogs
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 100Gi
      storageClassName: ocs-storagecluster-ceph-rbd
    type: template
  - name: backup
    spec:
      accessModes:
      - ReadWriteMany
      resources:
        requests:
          storage: 100Gi
      storageClassName: ocs-storagecluster-cephfs
    type: create
  - name: tempts
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 100Gi
      storageClassName: ocs-storagecluster-ceph-rbd
    type: template

See Certified storage options for Db2 for a full list of for supported storage solutions.

Use existing persistent storage claims

Existing persistent volume claims can be used also for deployment.

The following example shows the adding of an existing single, shared volume claim:
storage:
  - claimName: <data-pvc-name>
    name: data
    spec:
      resources: {}
    type: existing
The following example shows the adding of four existing and separate volume claims:
storage:
  - claimName: <meta-pvc-name>
    name: meta
    spec:
      resources: {}
    type: existing
  - claimName: <meta-pvc-name>
    name: data
    spec:
      resources: {}
    type: existing
  - claimName: <backup-pvc-name>
    name: backup
    spec:
      resources: {}
    type: existing
  - claimName: <activelogs-pvc-name>
    name: activelogs
    spec:
      resources: {}
    type: existing
  - claimName: <tempts-pvc-name>
    name: tempts
    spec:
      resources: {}
    type: existing

Enable 4K support

When your Db2 Warehouse on OpenShift deployment is configured to use either OpenShift Container Storage (OCS) or Portworx container storage (PX), ensure that you have enabled 4K support.

The following example code shows the 4K support set to ON:
spec:
  environment:
    ...
    instance:
      registry:
        DB2_4K_DEVICE_SUPPORT: "ON"

Disable LDAP

The LDAP directory service is enabled by default. The following example shows how to disable LDAP:
spec:
  environment:
    ldap:
      enabled: false
Note: If you are deploying a Db2uCluster on version s11.5.8.0-cn1 with LDAP disabled and have an existing instance with LDAP enabled, or you are trying to disable LDAP on s11.5.8.0-cn2, see this troubleshooting doc first: Recovering a Db2u deployment from failure due to missing user-mgmt secret.

Disable the Node Port service

By default, the creation of the Db2u instance activates a nodeport service, for moving external data into your cluster. The following example shows how to disable this behavior.
spec:           
  environment:
    database:
      disableNodePortService: true

Deploy a Db2 Warehouse instance with limited privileges

You can set parameters in your CR to create the Db2 Warehouse instance with limited privileges. This option improves security. The following example shows how to set limited privileges with unsafe sysctls:

spec:
  account:
    privileged: false
The following example shows how to set limited privileges by setting IPC kernel parameters on the nodes: 
spec:
  account:
    privileged: false
  advOpts:
    hostIPC: true

Deploying Db2Db2 Warehouse with a custom service account

A service account is an OpenShift Container Platform account that allows a component to directly access the API. You can set parameters in your CR to create the Db2 or Db2 Warehouse instance with a custom service account.

The following example shows the syntax for identifying your custom service account in the CR:
spec:
  account:
    serviceAccountName: ${SERVICE_ACCOUNT}

Specifying a license certificate key

The 2 licenses available for Db2 Warehouse are:
  • Developer edition
  • Enterprise edition
License keys for the Enterprise edition can be downloaded from the IBM Passport Advantage site:
  • Db2 Warehouse Enterprise Edition: dashDB_c.lic
Note: You must be entitled to use a license before you can download it. Ensure that you or your organization has purchased the required license.
To specify a license certificate:
  1. Encode your Db2 Warehouse license to base64 by running the following command:
    LICENSE_KEY="./dashdb_c.lic"
cat ${LICENSE_KEY} | base64 | tr -d '\n'
  2. The following example shows how to set the license key for your Db2 Warehouse instance:
    spec:
  license:
    value: <ENCODED STRING FROM STEP 1 GOES HERE>

Override the default database settings

You can override the default database settings for your Db2 Warehouse instance.
CAUTION:
You should only override the default database settings if you are aware of the risks involved. If you are at all unsure, accept the default settings.
The following example shows how to set the database values for your Db2 Warehouse instance:
spec:
  environment:
    database:
      settings:
        dftTableOrg: "COLUMN"
        dftPageSize: "32768"
        encrypt: "NO"
        codeset: "UTF-8"
        territory: "US"
        collation: "IDENTITY"

Override the Db2 Warehouse database configuration (dbConfig) settings

You can override the default database configuration settings for your Db2 Warehouse instance.
CAUTION:
You should only override the dbConfig settings if you are aware of the risks involved. If you are at all unsure, accept the default settings.
The following example shows how to set the dbConfig values for your Db2 Warehouse instance:
spec:
  environment:
    database:
      dbConfig:
        LOGPRIMARY: "50"
        LOGSECOND: "35"
        APPLHEAPSZ: "25600"
        STMTHEAP: "51200 AUTOMATIC"

Set the Db2 Warehouse registry variable

You can override the default Db2 Warehouse registry variable values for your Db2 instance.
CAUTION:
You should only override the Db2 Warehouse registry variable settings if you are aware of the risks involved. If you are at all unsure, accept the default settings.
The following example shows how to set the Db2 Warehouse registry variable values for your Db2 Warehouse instance:
spec:
  environment:
    instance:
      registry:
        DB2_ATS_ENABLE: "NO"
        DB2_OBJECT_STORAGE_SETTINGS: "OFF"
        DB2_DISPATCHER_PEEKTIMEOUT: "2"
        DB2_COMPATIBILITY_VECTOR: "ORA"

Example of a complete Db2uCluster CR

The following example shows the CR code to deploy a Db2 Warehouse cluster. The CR creates a Db2 Warehouse instance with the following configuration:
  • Database name: BLUDB.
  • 4 CPUs.
  • 16 GB of memory.
  • 5 storage volumes (meta, data, backup, activelogs, and tempts).
  • Db2 4K SUPPORT enabled.
  • LDAP disabled.
  • Privileged instance.
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
  name: db2wh-test
  namespace: db2u
spec:
  account:
    privileged: true
  environment:
    database:
      name: bludb
    dbType: db2wh
    ldap:
      enabled: false
  license:
    accept: true
  podConfig:
    db2u:
      resource:
        db2u:
          limits:
            cpu: "4"
            memory: 16Gi
  size: 1
  storage:
  - name: meta
    spec:
      accessModes:
      - ReadWriteMany
      resources:
        requests:
          storage: 10Gi
      storageClassName: ocs-storagecluster-cephfs
    type: create
  - name: data
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 10Gi
      storageClassName: ocs-storagecluster-ceph-rbd
    type: template
  - name: backup
    spec:
      accessModes:
      - ReadWriteMany
      resources:
        requests:
          storage: 1Gi
      storageClassName: ocs-storagecluster-cephfs
    type: create
  - name: activelogs
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 10Gi
      storageClassName: ocs-storagecluster-ceph-rbd
    type: template
  - name: tempts
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 10Gi
      storageClassName: ocs-storagecluster-ceph-rbd
    type: template
  version: s11.5.9.0-cn2

Deploying a Db2 Warehouse MPP instance

Db2 Warehouse can be deployed in either a single-node (SMP) or multi-node deployment designed for massively parallelized processing (MPP). In MPP deployments, Db2 Warehouse segments a query into smaller tasks that are then spread across multiple database partitions.

You control these parameters in your CR to create a Db2 Warehouse MPP instance. The size specifies the number of nodes and environment.mln.total specifies the total number of MLN(multiple logical node). By default, a single-node (SMP) deployment has size: 1 without a specification in environment.mln.total This example provides us a Db2 Warehouse MPP instance of 3 nodes with 4 multiple logical node per node. The value in environment.mln.total must be evenly divisible by size.

size: 3
environment:
  mln:
    total: 12