Requirements for IBM Db2 source databases

IBM Db2 connector is based on the zero touch production concept, meaning the production environment and staging environments are mutually exclusive except for HADR (High Availability Disaster Recovery) where the staging environment acts as a standby for the production. Source Db2 hosts are considered primary/production servers that have Db2 binaries installed and have Db2 instances created on them. The hosts that contain the data that you wish to ingest are referred to as the source environment. This topic describes the requirements for creating connections between the Delphix Continuous Data Engine and Db2 hosts and instances.

Requirements	Explanation
Requirements	Single Partition (Non-DPF)	Multi Partitions(DPF)
HADR Ports	The configuration values for HADR_LOCAL_SVC and HADR_REMOTE_SVC should be set. These ports are used at the end user's discretion and need to be specified during the linking process. It is highly recommended that these ports also be defined in the `/etc/services` file to ensure that they are only used by Db2 for the specified databases.	N/A
SSL certificate	For encrypted HADR transmission, SSL certificate should be made available on source host.	N/A
HADR source state	Source instance and database must be in active state to create HADR connection.	N/A
dbadm and secadm privileges for database	The database instance users must have dbadm and secadm permissions to enable cross instance restore. Delphix Continuous Data Engine uses the Db2 instance owner account on the dSource for multiple operations, including querying data inside the databases. In order to ingest a database on the staging server with different instances, you need permissions on the source database in order to perform a restore on the staging server. For example, if you have an instance named "auto1051" at the source with a database name "delphix" and you want to create a dSource on the "auto1052" instance on the staging server, then you must explicitly grant DBADM and SECADM to the dSource instance "auto1052" on the source instance using the following steps: Connect to the source database as the source instance owner. `connect to <DB_NAME> user <SOURCE_INSTANCE_OWNER>`. Issue database grant command, `grant DBADM, SECADM on the database to user <DSOURCE_INSTANCE_OWNER>` `grant DBADM, SECADM on the database to user <VDB_INSTANCE_OWNER>` Repeat step 2 for every database to be included in the dSource, on the corresponding source database.	Same as non-DPF
Database container requirement	It is recommended not to use special characters for source database container paths as this may create problems while parsing such container paths and may also result in failures during dSource and VDB creation.	Same as non-DPF
Banners	For connector versions < 4.2.0, Banners are not supported For connector versions >= 4.2.0, `.profile`, `MOTD`, and `ssh` banners are supported. Note: Print/echo statements in `.bashrc` are not supported by the connector.	Same as non-DPF