Stopping and starting a Db2 Warehouse instance

Important: IBM Cloud Pak for Data Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

Stop and start a Db2 Warehouse instance inside a container to perform maintenance tasks.

About this task

Db2 Warehouse comes with a built-in High Availability (HA) solution that monitors and triggers recovery actions if there is a problem with Db2 Warehouse database services. The built-in HA monitoring must be temporarily disabled before you stop and start Db2 Warehouse.

Procedure

  1. Exec into the Db2 Warehouse pod with catalog partition.
  2. Temporarily disable the built-in HA: 
    wvcli system disable -m "Disable HA before Db2 maintenance"
  3. Become the Db2 Warehouse instance owner: 
    su - ${DB2INSTANCE}
  4. Run the db2stop command and perform the maintenance tasks that you want.
  5. When the maintenance tasks are completed, restart Db2 Warehouse with the db2start command, and activate the database (for example, with the command db2 activate db BLUDB).
  6. Re-enable the built-in HA monitoring: 
    wvcli system enable -m "Enable HA after Db2 maintenance"
  7. Confirm that the built-in HA monitoring is active: 
    wvcli system status
    Tip: You might have to run these commands several times before the HA status is shown as active.