This topic describes how to link a DB2 staging dSource.

Prerequisites

• Be sure that the source and staging instances meet the host requirements and the databases meet the container requirements described in Requirements for DB2 Hosts and Databases.

Source Database Preparation

• Instance Owner Permissions

  Delphix uses the DB2 instance owner account on the dSource for many things, including verifying the data inside the databases. For ingesting database on the staging server with different instance we need permissions on the source database to do restore on the staging server. For example in the source if we have an instance named auto1051 and database name delphix and  if we want to create a dSource on the auto1052 instance on staging server then you must explicitly grant DBADM and SECADM to the dSource instance auto1052 on the source instance using the following steps:

  1. Connect to the source databases as the source instance owner.
     1. connect to <DB_NAME> user <INSTANCE_OWNER>
  2. Issue database grant command
     1. grant DBADM, SECADM on database to user <DSOURCE_INSTANCE_OWNER>
  3. Repeat step 2 for every database to be included in the dSource, on the corresponding source database.

Determine if your dSource will be a non-HADR instance, an HADR single standby instance, or an HADR multiple standby instance. Non-HADR dSources can only be updated via a full dSource resync from a newer backup file

Non-HADR Database

• 1. See "Instance Owner Permissions" section above. 

  2. Ensure that the source database has the necessary user permissions for the provisioned VDBs as described in Database Permissions for Provisioned DB2 VDBs

HADR Single Standby Database

• 1. All items in Non-HADR Database section above.
  2. The following database configuration settings must be set:
     1. update db cfg for <DB_NAME> using HADR_LOCAL_HOST <PRIMARY_IP> HADR_LOCAL_SVC <PRIMARY_PORT > immediate
     2. update db cfg for <DB_NAME> using HADR_REMOTE_HOST <STANDBY_IP> HADR_REMOTE_SVC <STANDBY_PORT> immediate
     3. update db cfg for <DB_NAME> using HADR_REMOTE_INST <STANDBY_INSTANCE_NAME> immediate
     4. update db cfg for <DB_NAME> using HADR_SYNCMODE SUPERASYNC immediate
  3. If database configuration parameter LOGINDEXBUILD is set to OFF, do the following:
     1. 1. update db cfg for <DB_NAME> using LOGINDEXBUILD ON
        2. Force off all connections to the database and reactivate the database
  4. If database configuration parameter LOGARCHMETH1 is set to OFF, do the following:
     
     1. update db cfg for <DB_NAME> using LOGARCHMETH1 XXXX (must be a valid log archiving method)
     2. Take an offline backup
        
  5. If LOGARCHMETH1 points to a third-party backup server (i.e. TSM or Netbackup) define LOGARCHMETH2 to disk
     1. update db cfg for <DB_NAME> using LOGARCHMETH2 DISK:<full path to archive log directory>
        1. Log files in the directory must be available from the time of the backup until the restore has successfully completed on the dSource.
  6. db2 start hadr on db <DB_NAME> as primary by force
  7. Take a full online backup as defined in the "Backup Source Database" section below.
  8. Record the following information, as it must be entered on the Delphix Engine while creating the dSource.
     1. HADR Primary hostname
     2. HADR Primary SVC
     3. HADR Standby SVC (auxiliary standby port)

HADR Multiple Standby Databases

This assumes a single standby database HADR setup already exists. The existing standby will be referred to as the main standby. The new delphix standby will be referred to as the auxiliary standby.

• 1. The following database configuration settings must be set on the primary database:
     1. update db cfg for <DB_NAME> using HADR_SYNCMODE <SYNC MODE> immediate – set whichever sync mode you wish to use on your main standby.
     2. update db cfg for <DB_NAME> using HADR_TARGET_LIST "<MAIN_STANDBY_IP:MAIN_STANDBY_PORT|AUXILIARY_STANDBY_IP:AUXILIARY_STANDBY_PORT>" immediate
        1. You may have up to two auxiliary standbys defined separated by a '|'; one of which must be the delphix dSource.

  2. stop hadr on db <DB_NAME>

  3. start hadr on db <DB_NAME> as primary by force
  4. Take a full online backup as defined in the "Backup Source Database" section below. While this backup is running, you may continue with step 5.
  5. The following database configuration settings must be set on the existing main standby database:
     1. update db cfg for <DB_NAME> using HADR_SYNCMODE <same mode as defined in 1.a above.> – It must be the same value used for primary database.
     2. update db cfg for <DB_NAME> using HADR_TARGET_LIST "<PRIMARY_IP:PRIMARY_PORT|MAIN_STANDBY_IP:MAIN_STANDBY_PORT>"
  6. stop hadr on db <DB_NAME>
  7. start hadr on db <DB_NAME> as standby
  8. Record the following information, as it must be entered on the Delphix Engine while creating the dSource (the auxiliary standby database):
     1. HADR Primary hostname
     2. HADR Primary SVC
     3. HADR Standby SVC (auxiliary standby port)
     4. HADR_TARGET_LIST <PRIMARY_IP:PRIMARY_PORT|MAIN_STANDBY_IP:MAIN_STANDBY_PORT>

Backup Source Database

In order to complete the linking process, the Standby dSource must have access to a full backup of the source DB2 databases on disk. This should be a compressed online DB2 backup and must be accessible to the dSource instance owner on disk. Delphix is currently not set up to accept DB2 backups taken using third-party sources such as Netbackup or TSM. Both HADR and Non-HADR backups must also include logs.

Example backup command: db2 backup database <DB_NAME> online compress include logs

Procedure

1. Login to the Delphix Management Application.
2. On the Databases tab of the Environment Management screen, add a source config against discovered staging instance.

3. Then, click Manage.

4. Select Datasets.

5. Click the Plus (+) icon and select Add dSource, you’ll get a list of available source configs using which you can go for dsource creation.

6. In the Add dSource wizard, select the required source configuration.  

7. If you are working with an HADR setup, please leave the HADR checkbox checked.

8. The database name is mandatory and must be unique for a given instance. This is the name that the database was on the instance it was restored from. 

9. Enter the complete Backup Path where the database backup file resides. If no value is entered, the default value used is the instance home directory. If there are multiple backup files for a database on the backup path, the most current one will be used.

10. Enter the Log Archive Method1 you wish to use for the database. If no value is entered, the default value used is DISK:/mountpoint/dbname/arch.

11. Optionally, users can set the database configuration parameters during the linking operation in the Config Settings section.

12. Optionally, users can provide a bash script as a toolkit defined hook.
    This hook will be executed after data ingestion but before snapshot operation.

13. If the dSource is to use HADR please enter the following fields. If it will not use HADR skip ahead to step 13.
    For more information about HADR please view Linking a dSource from a DB2 Database: An Overview.

    a. Enter a fully qualified HADR Primary Hostname. This is a required field for HADR and must match the value set for HADR_LOCAL_HOST on the master.

    b. Enter the port or /etc/services name for the HADR Primary SVC. This is a required field for HADR and uses the value set for HADR_LOCAL_SVC on the master.

    c. Enter the port or /etc/services name for the HADR Standby SVC. This is a required field for HADR and uses the value set for HADR_REMOTE_SVC on the master.

14. Click Next.

15. Enter a dSource name and select a group for your dSource. Adding a dSource to a dataset group lets you set Delphix Domain user permissions for that database and its objects, such as snapshots. 

16. Click Next.

    You will get the Data Management section where you need to specify staging environment and user which will be used for dsource creation.

17. Set the Staging Environment to be the same as the dSource host.

18. Select the Staging Environment User to be the same as the instance owner of the dSource instance.

    Changing the Environment User

    If you need to change or add an environment user for the dSource instance, see Managing DB2 Users and Instance Owners.

19. Then, click Next and you’ll get the Policies section. Set the desired Snapsync Policy for the dSource. For more information on policies see Advanced Data Management Settings for DB2 dSources.

20. Click Next.

21. Specify any desired pre- and post-scripts. For details on pre- and post-scripts, refer to Customizing DB2 Management with Hook Operations.

22. Click Next.

23. Review the dSource Configuration and Data Management information in the Summary section.

24. Click Submit.
    

The Delphix Engine will initiate two jobs to create the dSource: DB_Link and DB_Sync. You can monitor these jobs by clicking Active Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the database icon will change to a dSource icon on the Environments > Host > Databases screen, and the dSource will also appear in the list of Datasets under its assigned group.