Scaling up the target database

Since the initial Data Gate setup, Data Gate and your target database have become interconnected entities. Therefore, you cannot change the configuration of your target database independently of your Data Gate configuration. Follow the recommended process after this if you want to enlarge or otherwise change the capacity of your Db2 or Db2 Warehouse target database for higher workloads.

Procedure

From the dashboard of your Data Gate instance, stop the synchronization process by clicking the toggle button.
From the command-line of the OpenShift® cluster where Data Gate is installed, identify the Data Gate instance identifier, and assign the value to the variable DG_INSTANCE_ID by issuing the oc get dginstance command. For example:
```
oc get dginstance -n ${PROJECT_CPD_INST_OPERANDS}
NAME                 VERSION   BUILD      STATUS      RECONCILED   AGE
dg1699914520773847   5.0.0     5.0.0.82   Completed   5.0.0        6h58m
```
In this example, the instance ID is dg1699914520773847.
From the command-line of the IBM Cloud Pak CLI (cpd-cli), set the variable DG_INSTANCE_ID to the instance ID found in step 2.
From the command-line of the IBM Cloud Pak CLI (cpd-cli), shut down your Data Gate instance:
```
export DATAGATE_INSTANCE_ID=<instance-id> \
cpd-cli manage shutdown --components=datagate_instance --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--extra-vars=cr_name=${DATAGATE_INSTANCE_ID}
```
Where <instance-id> is the ID of your instance. For more information, see Shutting down and restarting services.
To scale up a Db2 target database, access the db2u container and unset the DB2_WORKLOAD registry variable. This step is not required for Db2 Warehouse databases.
```
oc -n ${PROJECT_CPD_INST_OPERANDS} exec -it ${db2_podname} su - db2inst1
db2set DB2_WORKLOAD=
```
Where db2_podname is the name of the Db2 server pod. For more information, see Exec into the Db2 pod.
Configure your Db2 or Db2 Warehouse instance for higher workloads.
See Scaling up Db2.
Verify that all your configuration changes are preserved. This is important because some parameters are changed automatically by Data Gate, while others must be changed manually, such as:
- logarchmeth1
- logfilsiz
- logprimary.
Access the db2u container and set the DB2_WORKLOAD registry variable to the value ANALYTICS_ACCELERATOR. This time, the step is required for both, Db2 and Db2 Warehouse target databases.
Example:
```
oc -n ${PROJECT_CPD_INST_OPERANDS} exec -it ${db2_podname}  su - db2inst1 
db2set DB2_WORKLOAD=ANALYTICS_ACCELERATOR 
db2stop force 
db2start
```

Restart the Data Gate instance:

export DATAGATE_INSTANCE_ID=<instance-id> \
cpd-cli manage restart --components=datagate_instance --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--extra-vars=cr_name=${DATAGATE_INSTANCE_ID}

See Shutting down and restarting services for more information.

From the dashboard of your Data Gate instance, click the toggle button to restart the synchronization process.