IBM Integrated Analytics System 1.0.23.2 release notes (September 2020)

1. Run the command from the web console:

   rm -f /scratch/ldap_tmp/sssd.conf

   • If there is file /scratch/ldap_tmp/command.sh in web_console, run it. This resolves the issue.
   • If there is no /scratch/ldap_tmp/command.sh
     1. Copy /etc/sssd/sssd.conf from the dashDB container to web_console:/etc/sssd/sssd.conf.
     2. Run the command:

        systemctl restart sssd

To refresh the Db2 SSL certificate for IBM Data Replication for Availability:

1. On the source system, in the Db2 container, as su-dsadm:
   1. Ensure that BLUDR_SHARED_DIR is set:
      • On IAS or Db2 Warehouse on Cloud:

        BLUDR_SHARED_DIR=/head/bludr

      • On Db2 Warehouse:

        BLUDR_SHARED_DIR=/mnt/blumeta0/bludr

   2. Import local Db2 SSL certificate to the IBM Data Replication for Availability truststore:

      1. /opt/ibm/java/jre/bin/keytool -delete -keystore ${BLUDR_SHARED_DIR}/certificates/cacerts -storepass "$(base64 -d ${BLUDR_SHARED_DIR}/certificates/truststore_pwd)" -alias db2_ssl -noprompt

      2. /opt/ibm/java/jre/bin/keytool -import -trustcacerts -keystore ${BLUDR_SHARED_DIR}/certificates/cacerts -storepass "$(base64 -d ${BLUDR_SHARED_DIR}/certificates/truststore_pwd)" -alias db2_ssl -noprompt -import -file /mnt/blumeta0/db2/ssl_keystore/rootCA.pem

   3. Import the target Db2 SSL certificate to the IBM Data Replication for Availability truststore.

      The certificate is available at /mnt/blumeta0/db2/ssl_keystore/rootCA.pem inside the database container. You can extract the self-signed root CA certificate to your system. For more information, see the Procedure section.

      1. /opt/ibm/java/jre/bin/keytool -delete -keystore ${BLUDR_SHARED_DIR}/certificates/cacerts -storepass "$(base64 -d ${BLUDR_SHARED_DIR}/certificates/truststore_pwd)" -alias db2_ssl_<target_hostname> -noprompt

      2. /opt/ibm/java/jre/bin/keytool -import -trustcacerts -keystore ${BLUDR_SHARED_DIR}/certificates/cacerts -storepass "$(base64 -d ${BLUDR_SHARED_DIR}/certificates/truststore_pwd)" -alias db2_ssl_<target_hostname> -noprompt -import -file ${BLUDR_SHARED_DIR}/certificates/<target_hostname>_rootCA.pem

   4. As the root or db2inst1 user, import the remote target Db2 root certificate to the local Db2 SSL keystore for Db2CLP:

      opt/ibm/db2/V11.5.0.0/gskit/bin/gsk8capicmd_64 -cert -add -db /mnt/blumeta0/db2/ssl_keystore/bludb_ssl.kdb -stashed -label db2_ssl_rootCA_<target_hostname> -file ${BLUDR_SHARED_DIR}/certificates/<target_hostname>_rootCA.pem -format ascii -trust enable -fips

   5. Verify the Db2 certificate aliases in the IBM Data Replication for Availability truststore :

      keytool -v -list -keystore ${BLUDR_SHARED_DIR}/certificates/cacerts  -storepass "$(base64 -d ${BLUDR_SHARED_DIR}/certificates/truststore_pwd)"  | grep Alias -A10 | grep db2 -A10

   6. Restart the IBM Data Replication for Availability server and web console.

      Run the restart commands as the dsadm user:

      1. The IBM Data Replication for Availability server:

         /opt/ibm/bludr/scripts/bin/bludr-restart.sh

      2. The web console:
         • On Db2 Warehouse:

           /opt/ibm/dsserver/bin/restart.sh 

         • On IAS:
           • Restart the API server:

             systemctl restart apiserver

           • From the IAS console, on the platform

             ap apps disable webconsole
             ap apps enable webconsole 

2. On the target system, do the same steps as for the source system. Import the source Db2 SSL certificate and local Db2 SSL certificate to the IBM Data Replication for Availability truststore, and import the remote source Db2 root certificate for Db2CLP.

If a restore is in progress, the example output for each MLN is:

Restore percentage output:
ID = 1
Type = RESTORE
Database Name = BLUDB
Member Number = 1
Description = db
Start Time = 09/02/2020 09:57:33.923808
State = Executing
Invocation Type = User
Progress Monitoring:
Completed Work = 922976256 bytes
Start Time = 09/02/2020 09:57:33.923813

ID = 1
Type = RESTORE
Database Name = BLUDB
Member Number = 2
Description = db
Start Time = 09/02/2020 09:57:33.904257
State = Executing
Invocation Type = User
Progress Monitoring:
Completed Work = 922976256 bytes
Start Time = 09/02/2020 09:57:33.904264

You can find a log file associated with this restore operation in the /opt/ibm/appliance/storage/scratch/bluadmin_BNR/logs directory directory. Review the logs in the most recent restore log and tracelog for progress details.