Monitoring Db2 Warehouse startup after rebooting a node

When a node is restarted, confirm that Db2 Warehouse successfully starts up by monitoring the startup progress.

About this task

Db2 Warehouse should automatically start up after a Kubernetes worker node is started and the kubelet starts all the pods on the node. You can run a series of commands to monitor the startup progress.

Procedure

  1. Run the command kubectl get nodes and check the output to verify the following:
    • The Kubernetes worker nodes that were rebooted are in a ready state.
    • All nodes with the etcd operator role are in a ready state.
  2. Monitor the Db2 Warehouse pod startup progress: 
    kubectl -n ${PROJECT_CPD_INSTANCE} get po | grep db2u
  3. Check that all Db2 Warehouse database services pods are in a running state: 
    kubectl -n ${PROJECT_CPD_INSTANCE} get po --selector type=engine
  4. Confirm that the Db2® instance is healthy.
    1. Exec into the Db2 Warehouse pod with catalog partition.
    2. Become the Db2 instance owner: 
      su - ${DB2INSTANCE}
    3. Run the following commands to validate the health of the Db2 instance: 
      db2gcf -s   # Should show 'Active'
      db2pd - -member all | grep Member   # Should show an entry for each Db2 partition
      db2pd -db bludb - -member all | grep Member   # Should show an entry for each Db2 partition
      db2 list active databases   # Should show BLUDB database active
      db2 connect to BLUDB; db2 connect reset # Confirm you can connect to the database