Configuring, monitoring, and managing access to Db2 Big SQL instances

When you are logged in as an administrator, you can complete various administrative tasks from the Cloud Pak for Data web client.

Before you can administer the Db2® Big SQL service from the Cloud Pak for Data web client, complete the following steps:
  1. Sign in to the Cloud Pak for Data web client as an administrator.
  2. From the navigation menu, click Services or Administration and select the appropriate task from the navigation.

Managing access to Db2 Big SQL instances

There are two kinds of users in Db2 Big SQL: regular users and administrative users. Administrative users can perform administrative tasks on a Db2 Big SQL instance, such as scaling the instance and adding or removing other users.

To specify which users or groups of users can access a Db2 Big SQL instance, and which users are administrators, complete the following steps:
  1. From the navigation menu, click Services > Instances.
  2. From the instances list, find the instance that you want to modify. Click the options menu and select Manage access.
  3. Click Add users.

Updating instance configuration

You can provision multiple instances of Db2 Big SQL. For each instance, you can optionally:
  • Scale the instance up or down by allocating additional or fewer resources.

    For more information, see Scaling Db2 Big SQL.

  • Scale the instance out or in by adding or removing workers. After scaling your instance out, be sure to run a health check. For details, 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

    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.

To update the configuration of a specific Db2 Big SQL instance, complete the following steps:
  1. From the navigation menu, click Services > Instances.
  2. From the instances list, select the instance that you want to modify.
  3. Click Edit.

To restart the Db2 Big SQL instance, complete 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 a cluster 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}
  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"

Monitoring resource usage

To monitor the resource usage of a specific Db2 Big SQL instance, complete the following steps:
  1. From the navigation menu, click Administration > Platform management.
  2. From the Services page, you can gauge the overall health and resource use for your service.
  3. From the Service instances page, you can gauge the overall health and resource use for a specific instance of your service.
  4. From the Pods page, you can monitor the status of your pods.