Requirements for IBM Db2 staging and target environments
This section elaborates on the various host requirements for the staging host where the dSource is linked and the target where the VDB is provisioned based on the type of ingestion method being used.
Requirements | Explanation | |
---|---|---|
Single Partition (Non-DPF) | Multi Partitions (DPF) | |
Access to database backups | The staging environment must have access to a full online backup of the source database on disk to create the first full copy. Delphix Continuous Data Engine recommends using compressed backups as that will reduce storage needs and speed up ingestion. It is recommended to test the integrity of the backup before using it for ingestion using the utility db2ckbkp. Once this first fill backup is ingested into the staging database, representing the Db2 dSource, subsequent synchronizations can be accomplished via HADR or Archive Logs. | Same as non-DPF |
HADR Ingestion - port specific | The configuration values for | NA |
Db2 instance | The staging and target Db2 instances that you wish to use must already exist on the host. We can use the same instance for the dSource and VDB creation and can also have multiple VDBs on the same instance. | Same as non-DPF |
Db2 instance configuration parameters | Instance level configuration values such as the bufferpool value will need to be managed by the end users independent of Delphix Continuous Data Engine. | Same as non-DPF |
Db2 instance compatibility | The IBM Db2 instance binaries and versions for staging and target environments must be compatible with the source Db2 instance. | Same as non-DPF |
Db2 version | Db2 versions on staging and target should be identical i.e., major, minor, modpack and fixpack should be the same on both staging and target instances for smoother provision. | Same as non-DPF |
No of partitions (Logical) | NA | The staging and target hosts must be configured with the same number of logical partition nodes as the source. |
Logical partition configuration | NA | The logical partition configuration must be added in the Example:
|
/etc/services entry | NA |
CODE
|
Registry variable setting | Registry variables
CODE
| Same as non-DPF |
db2_all utility test | NA | After the environment is configured on staging and target, execute |
Archive logs | Instance users should have permission to read logs. | The backup files (or log directory if using Archive Logs) should be consistent with the partitions configured on staging. |
SSH configuration parameters | NA | When configuring staging and target environments for multiple partitions (dpf), the |
Primary user permissions | There must be an operating system user (delphix_os) with these privileges:
| Same as non-DPF |
Toolkit directory and its permissions | There must be a directory on the staging and target environment where you can install the IBM Db2 connector. For example,
| Same as non-DPF |
Common group between primary and instance users | The primary environment user should share its primary group with the instance user. For example, if the delphix_os is the primary environment user which is used for environment addition and its primary group is also delphix_os then instance users (responsible for the Delphix Continuous Data Engine operations such as linking and provisioning) should share group delphix_os as their secondary group | Same as non-DPF |
Instance user requirement |
| Same as non-DPF |
DB2_RESTORE_GRANT_ADMIN_AUTHORITIES | If the instance user doesn’t have access to the source database and the staging host uses a different instance user to ingest the dSource, the user can set the DB2 registry variable | Same as non-DPF |
Database level requirement |
| Same as non-DPF |
For connector versions < 4.2.0, Banners are not supported For connector versions >= 4.2.0, Note: Print/echo statements in | Same as non-DPF |
It is highly recommended that the Database Partitioning Feature (DPF) for IBM Db2 staging and target should be configured on separate hosts due to the reason that the DPF instances in staging or target environments consume a lot of resources.