Scaling up Q Replication for Db2

You can add more memory and CPU to the replication add-on for Db2 to support high-availability or increase processing capacity.

1. From your Db2 terminal, get the deployment identifier for the source or target database.
   1. From the home page of the web client, click Quick navigation > Databases.
   2. Open the actions menu for the database and select Details.
   3. Under About this database, look for Deployment ID.
   In the following examples, the deployment ID is db2-1634282498405551.
2. Get the identifier for the replication pod by appending -qrep to the deployment identifier in the oc get pod|grep command:

   oc get pod|grep db2-1634282498405551-qrep
   c-db2-1634282498405551-qrep-79996c44c8-7gz7b     1/1     Running     0          5d1h

3. Get the deployment identifier for replication:

   oc get deployment|grep db2-1634282498405551-qrep
   c-db2-1634282498405551-qrep   1/1     1            1           51d

4. Check the original memory size:

   oc describe deployment c-db2-1634282498405551-qrep
   ...
       Limits:
         cpu:     8
         memory:  16Gi
   ...

5. Edit the deployment:

   oc edit deployment c-db2-1634282498405551-qrep

6. Increase the memory and CPU values in the resources.limits section:

   resources:
             limits:
               cpu: "16"
               memory: 64Gi

7. Use the :wq command to save the configuration changes.
   The change might take about a minute to finish. As a result of the change, the replication pod is recreated.
8. Verify that the status of the new replication pod is Running:

   oc get pod|grep db2-1634282498405551-qrep
   c-db2-1634282498405551-qrep-6d96bc795-9lp7t        1/1     Running     0          12s