Upgrading to IAS 1.0.26 or Db2 Warehouse 11.5.6 with a custom bluadmin group name

If you upgrade to Integrated Analytics System 1.0.26 or Db2® Warehouse 11.5.6 with Windows Active Directory or external LDAP with a custom bluadmin group name, you need to take extra steps before and after the upgrade to preserve the apply program's access to files that are needed for replication.

Before you upgrade

  1. On the replication target site, connect to the database:
    db2 connect to bludb
  2. Run the following statement:
    db2 "UPDATE QASN.IBMQREP_TARGETS SET ERROR_ACTION='Q'"

    This change causes the replication set to deactivate if an error occurs while applying data to a target table, giving you the opportunity to fix the problem.

After you upgrade

After you upgrade, replication automatically starts and the replication sets deactivate because of insufficient permissions. Follow these steps:

  1. Enter the Db2 common container as root.
  2. Run the following commands as root:
    chgrp -R BLUADMIN_CUSTOM_GROUP_NAME ${BLUDR_DB2_DATA_PATH}/repl
chmod -R g+s ${BLUDR_DB2_DATA_PATH}/repl

    Replace BLUADMIN_CUSTOM_GROUP_NAME with your custom bluadmin group name.

  3. Verify if the folder contents have the correct group:
    ls -la ${BLUDR_DB2_DATA_PATH}/repl

    Example output:

    -rw-r-Sr-- 1 root bluadmgrp 1 Jun 23 22:05 test.bin
drwxr-sr-x 2 root bluadmgrp 6 Jun 23 22:06 logs

    Existing files have the group owner set to the custom group. Subdirectories have the group owner set to the custom group and the setgid (s) bit set.

  4. Start the inactive replication sets from the web console.