Installing a Db2 instance for Db2 Data Gate on Cloud Pak for Data

You must install, provision, and configure a Db2 or Db2 Warehouse instance on Cloud Pak for Data for each Db2 Data Gate instance.

About this task

A Db2 Data Gate instance requires either a Db2 or Db2 Warehouse instance depending on the type of target database you select when creating a Db2 Data Gate instance.

If you plan on using Db2 Data Gate for transactional workloads, install and configure Db2 as described in Installing Db2.
Important: After installing the basic Db2 service (Community Edition license), you must upgrade to Db2 Advanced Enterprise Server Edition.
1. Follow the instructions in:
  1. Upgrading the Db2 license after installing
  2. Upgrading the license for a deployed Db2 service
2. Scale up CPU and memory by following the steps in Scale up Db2.
If you plan on using Db2 Data Gate for analytical workloads, install and configure Db2 Warehouse as described in Installing Db2 Warehouse.

In either case, the following requirements and recommendations should be followed during Db2 installation and configuration to ensure correct operation and optimal performance of Db2 Data Gate:

Procedure

Recommended: For the best Db2 Data Gate performance, create a Db2 or Db2 Warehouse service instance on a dedicated node with its own dedicated storage and set the storage volume type to hostPath.
The hostPath storage volume type offers a lower I/O latency. Always aim for an extremely low synchronization latency and a high load throughput.
Note that each database instance needs a different dedicated hostPath location on the host machine.
For more information, see:
Recommended: For the best Db2 Data Gate performance, after the Db2 instance is created, consider to increase the total size of the Db2 log file. Otherwise, the loading of tables might fail because the log file is too small.
- For test and development systems, consider to increase the total size to about 3 GB by setting the value of the logfilsiz parameter to 50000 and the value of the logprimary parameter to 15.
- For production systems, your Db2 administrator should adjust the settings based on system capacity.
For more information, see:
- Db2 logfilsiz - Size of log files configuration parameter
- Db2 logprimary - Number of primary log files configuration parameter
Recommended: To further optimize the performance after the creation of the Db2 instance, consider increasing the values of the locklist and maxlock parameters. This is to avoid that too many row locks are replaced with a lock of the entire table while tables are being synchronized (a process called lock escalation).
- For test and development systems, keep the default value Automatic.
- For production systems, change the value of the locklist parameter to 500000 and the value of the maxlocks parameter to 13.
For more information, see:
- locklist - Maximum storage for lock list configuration parameter
- maxlocks - Maximum percent of lock list before escalation configuration parameter