SQL pods fail to start

Db2 Data Management Console runsql pods fail to start after you restart the pods.

Resolving the problem

To resolve the problem, complete the following steps:
  1. Check the status of the runsql pod. Run the following command:
    oc get pods -n ${PROJECT_CPD_INST_OPERANDS} | grep -i dmc | grep -i runsql
  2. If the runsql pod is not running, then use one of the following workarounds:

    Workaround 1

    Add more resources to the runsql pod. Run the following command:
    oc patch -n ${PROJECT_CPD_INST_OPERANDS} dmc/data-management-console --type=merge --patch '{"spec":{"custom_resources":{"runsql": {"limits":{"cpu": "400m", "memory": "768Mi", "ephemeral-storage": "275Mi"}, "requests":{"cpu": "300m", "memory": "656Mi", "ephemeral-storage": "25Mi"} }}}}'

    Workaround 2

    Change the scaleConfig from small to medium. Run the following command:
    oc patch dmc data-management-console \
--namespace ${PROJECT_CPD_INST_OPERANDS} \
--patch '{"spec":{"scaleConfig":"medium"}}' \
--type=merge
  3. Wait for all the pods to restart and check the status of the dmc instance in the console.