Configuring a Db2 Big SQL instance

Configure a Db2 Big SQL instance.

About this task

For each Db2 Big SQL instance that you provision, you can do the following tasks:

  • Scale the instance up or down by allocating more or fewer resources.

    For more information, see Scaling Db2 Big SQL.

  • Scale the instance out or in by adding or removing workers.

    After you scale out an instance, validate the multi-worker configuration by running a health check. For more information, see Running the Db2 Big SQL health check command.

  • Edit the following credential-related information:
    • The Hadoop cluster username and password
    • The Kerberos admin principal and password
    • The object store access and secret key
    Note: After you modify any of these items (except the object store access and secret key), you must restart the Db2 Big SQL instance for the updated information to take effect.

Procedure

  1. Sign in to the Cloud Pak for Data web client as an administrator.
  2. From the navigation menu, click Services > Instances.
  3. From the instances list, select the instance that you want to modify.
  4. Click Edit.
  5. Make the configuration changes that you want.
  6. To restart the Db2 Big SQL instance, do the following steps.
    Best practice: You can run the commands in this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.

    Ensure that you source the environment variables before you run the commands in this task.

    1. Log in to Red Hat® OpenShift® Container Platform as an instance administrator.
      ${OC_LOGIN}
      Remember: OC_LOGIN is an alias for the oc login command.
    2. Change to the project where the Cloud Pak for Data control plane is installed:
      oc project ${PROJECT_CPD_INST_OPERANDS}
      Note: This command uses an environment variable so that you can run the command exactly as written. For information about sourcing environment variables, see Setting up installation environment variables.
    3. Identify the Db2 Big SQL instance ID:
      oc get cm -l component=db2bigsql -o custom-columns="Instance Id:{.data.instance_id},Instance Name:{.data.instance_name},Created:{.metadata.creationTimestamp}"
    4. Get the name of the Db2 Big SQL head pod:
      head_pod=$(oc get pod -l app=bigsql-<instance_id>,name=dashmpp-head-0 --no-headers=true -o=custom-columns=NAME:.metadata.name)
    5. Restart Db2 Big SQL:
      oc exec -i $head_pod -- sudo su - db2inst1 -c "bigsql stop; bigsql start"