Configuring Db2 Big SQL components

You can tune Db2 Big SQL by updating configuration parameters for different Db2 Big SQL components.

About this task

Use the bigsql config utility to set configuration parameters that are defined in the bigsql-conf.xml file or the bigsql-default.xml file. These parameters are logically grouped for different Db2 Big SQL components, commands, and statements. The following table shows what you can configure with the bigsql config utility.

Component, command, or statement Db2 Big SQL on-premises documentation link for details
Db2 Big SQL scheduler Db2 Big SQL scheduler
Db2 Big SQL ANALYZE command The ANALYZE command
LOCATION clause in various statements Authorization properties for the LOCATION clause
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.

Procedure

  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 IBM® Software Hub 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. Set the configuration parameter that you want by using the db2uctl adm bigsql config command.
    Tip: The db2uctl adm bigsql config command is equivalent to the bigsql-config -set command in Db2 Big SQL 7.1.
    For example, to increase the scheduler.client.request.timeout property from the default value of 2 minutes (120000 milliseconds) to 1 hour (3600000), run the following command:
    oc exec -i $head_pod -- bash -c 'db2uctl adm bigsql config --key scheduler.client.request.timeout --value 3600000'
  6. Restart Db2 Big SQL:
    oc exec -i $head_pod -- sudo su - db2inst1 -c "bigsql stop; bigsql start"