Replicating from IAS to Db2 Warehouse on Cloud

Network configuration

To configure networking between IAS and Db2 Warehouse on Cloud, open a ServiceNow ticket for special network setup.

Additional replication setup steps

In addition to the documented configuration steps for replication, you must do the following setup tasks to replication from IAS to Db2 Warehouse on Cloud.

1. To enable Db2 Warehouse on Cloud to communicate with IAS, import the IAS Db2 SSL key by running the bludr-configure-certs.sh script. Run the following command on IAS inside the dashDB container as dsadm user:

   su - dsadm
   /opt/ibm/bludr/scripts/bin/bludr-configure-certs.sh IIAS_source_hostname db2woc_target_hostname

   Where IIAS_source_hostname is the floating IP/hostname of the source system.

2. If you are using dual IP addresses on IAS:
   • Provide the IP address as ALTERNATE_SOURCE_HOSTNAME=nnn.nnn.nn.nn in the file /opt/ibm/apiserver/wlp/usr/servers/bludr/server.env inside the dashDB container on IAS. The ALTERNATE_SOURCE_HOSTNAME is the DNAT IP address that is set up through the ServiceNow ticket.
   • Set USE_ALTERNATE_SOURCE_HOSTNAME=YES in the same file.
3. Verify connectivity between IAS and Db2 Warehouse on Cloud by running the following commands:

   On IAS dashDB container

   - openssl s_client -connect {db2woc_host_name}:50001
   - openssl s_client -connect {db2woc_host_name}9444
   - openssl s_client -connect {db2woc_host_name}:1414

   On Db2 Warehouse on Cloud dashmpp-head-0 container

   - openssl s_client -connect {iias_host}:50001
   - openssl s_client -connect {iias_host}:9444
   - openssl s_client -connect {iias_host}:1414

4. Enable the source database for replication on IAS.
5. Activate replication on Db2 Warehouse on Cloud.
6. Add the Db2 Warehouse on Cloud database as a target for IAS.

For additional setup considerations, see Planning for replication.

Troubleshooting activation issues with web console

You activate replication by using the Db2 Warehouse web console. If you experience problems opening the replication home page on the console:

• Check on the nginx and DS_System_0 log files for error details.
• Ensure that the bludbhost, bludrhost, dshost2, and aspera service names do not change in the Db2 Warehouse on Cloud namespace.
• Ensure that the nginx configuration for dsserver uses bludrhost:9444 instead of 127.0.0.1:9444.

Best practices

• Row-organized table replication requires an enforced key.
• Matching table spaces must be defined on the target.
• The replication user password must not have an exclamation point (!) character.
• Predefine target tables by using the db2look utility to generate DDLs from the source database.
• To delete the target tables on the apply side, stop the table subscription from the IAS console first before deleting.
• If you stop an active table subscription, the target table must be reloaded when that table subscription is started later. If a replication set is stopped, it remembers the last sync point and can resume the replication of all table subscription so that no target table reload is required. Note that when you stop a replication set, the active table subscriptions remain active.
• If there are many tables added to a set, the added tables do not start automatically. To activate all, restart the replication set.
• By default, restarting a replication set automatically starts all of the table subscriptions. To suppress the automatic start of all table subscriptions, update all the table subcription states to inactive (STATE of I in the ASN.IBMQREP_SUBS table).
• If large tables (terabytes) will be taken down for a period of time, consider ing the db_migrate utility to load the tables to the target first.