Enabling selection of higher memory and CPU limits for Db2 Enterprise Server Edition

If you are using Db2® Enterprise Server Edition with Cloud Pak for Data, you can take manual steps to ensure that the higher memory and CPU limits for this edition can be selected in the web client.

About this task

The client does not automatically detect that the Db2 service is using Enterprise Server Edition, so these steps are required to use the client to set higher memory and CPU.

Perform these steps after you upgrade the Db2 license and before you deploy the Db2 service.

Procedure

Set the Db2 operator replica to 0 by running the following command:
```
oc patch deployment ibm-db2oltp-cp4d-operator-controller-manager --patch '{"spec": {"replicas": 0}}' -n operator_namespace
```
Where operator_namespace is the Red Hat Open Shift project (namespace) that contains the Db2 operator.
Open the db2u-json-cm ConfigMap object in edit mode:
```
oc edit cm db2u-json-cm -n=namespace
```
Type /max-cpu to locate the max-cpu section of the ConfigMap, and under the ibm-db2oltp.json data option change max-cpu to 128:
```
\"max-cpu\": 128,
```
Type /max-mem to locate the max-mem section of the ConfigMap, and under the ibm-db2oltp.json data option change max-mem to 2048:
```
\"max-mem\": 2048,
```
Save the change and exit the ConfigMap.
Delete the zen-database-core pod in order for the ConfigMap changes to be re-mounted to the volume.
```
oc delete po $(oc get po -n=namespace | grep zen-database-core | awk {'print $1'}) -n=namespace
```
Note: If you reinstall or upgrade the Db2 service, you must performed steps 1-6 again.
Deploy the Db2 service.

Set the Db2 operator replica to 1 by running the following command:

oc patch deployment ibm-db2oltp-cp4d-operator-controller-manager --patch '{"spec": {"replicas": 1}}' -n operator_namespace