IBM Support

Restarting the operating system on the master servers of a Multi-Master cluster

How To


Summary

Use the steps in this document if you are planning to restart the operating system on the master servers of an IBM Security Key Lifecycle Manager Multi-Master cluster, or if you want to check the high availability disaster recovery (HADR) configuration after an unplanned restart of the operating system on the master servers.

Objective

The document contains the procedures for the following scenarios:
Scenario 1: To maintain the HADR configuration when you plan to restart the operating system on the primary, standby, or all master servers

Scenario 2: To check and update the HADR configuration after an unplanned restart of the operating system on the primary or standby master servers

Environment



Steps

Scenario 1: To maintain the HADR configuration when you plan to restart the operating system on the primary, standby, or all master servers


Step 1. Stop the HADR operations.
Substep CLI command
   a. Stop the HADR operations on the primary master server.
db2 stop hadr on database <Primary database name>

   b. Deactivate the standby database on the standby master server.

   Perform this step on each standby master server.

db2 deactivate db <Standby database name>

   c. Stop HADR operations on the standby master.

  Perform this step on each standby master server.

db2 stop hadr on database <Standby database name>
Step 2. Restart the operating systems.

Restart the operating system on the master servers in the following order:

a. Primary master server
b. Standby master servers
c. Other master servers 
Step 3. Start the HADR operations.
Substep CLI command

  a. Start the HADR operations on the standby master server.

  Perform this step on each standby master server.
  Note: If the following message is displayed, ignore the message and proceed to the next step: "SQL1777N  HADR is already started."

db2 start hadr on database <Standby database name> as standby
  b. Start the HADR operations on the primary master server.
db2 start hadr on database <Primary database name> as primary 


  

Scenario 2: To check and update the HADR configuration after an unplanned restart of the operating system on the master servers

1. Check the status of the HADR configuration on the primary and standby master servers.
CLI commands:
db2pd -d <Primary database name> -hadr


db2pd -d <Standby database name> -hadr
Perform this step on all standby master servers.
 
2. Based on the HADR configuration status, complete the steps as given in the following table:
HADR configuration status
Primary master server Standby master servers Steps
Connected  Connected No action required. 

Disconnected

Disconnected  1. Start the HADR operations on the standby master server:
    db2 start hadr on database <Standby database name> as standby

 Perform this step on each standby master server.


 Note: If the following message is displayed, ignore the message and proceed to the next step:     "SQL1777N  HADR is already started."

 2. Start the HADR operations on the primary master server.

    CLI command: db2 start hadr on database <Primary database name> as primary 
Connected Disconnected

Start the HADR operations on the standby master server.

  db2 start hadr on database <Standby database name> as standby

Perform this step on each standby master server.

Note: If the following message is displayed, ignore the message because no further action is required: "SQL1777N  HADR is already started."

Disconnected Connected
Start the HADR operations on the primary master server.
db2 start hadr on database <Primary database name> as primary 



 

Document information

More support for: IBM Security Key Lifecycle Manager

Software version: 3.0, 3.0.1

Operating system(s): Platform Independent

Reference #: 0870928

Modified date: 12 February 2019