Troubleshooting
This section explains some of the problem scenarios that you might encounter while working with the DB2 HADR toolkit in an HP Serviceguard Cluster.
Problem Scenario
If the package log contains an error message:
Host key verification failed. Lost connection.
If the package log contains an error message:
Failed to assign IP to primary package.
Possible Cause
The SSH connection without password is not configured properly.
To verify the possible cause:
1.Get the Interconnect traffic IP of the Remote host. For example, consider that the database name is a sample on which HADR is configured. Run the f# db2 get db cfg for sample grep HADR command.
This returns the following result:
HADR database role = STANDBY HADR local host name (HADR_LOCAL_HOST) = 10.0.0.1 HADR local service name (HADR_LOCAL_SVC) = 41005 HADR remote host name (HADR_REMOTE_HOST) =
10.0.0.2HADR remote service name (HADR_REMOTE_SVC) = 41005 HADR instance name of remote server (HADR_REMOTE_INST) = db2inst1 HADR timeout value (HADR_TIMEOUT) = 120 HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC HADR peer window duration (seconds) (HADR_PEER_WINDOW )= 0
In this example, Interconnect traffic IP of the Remote host is: “10.0.0.2”.
2.Run ssh or scp command to the Interconnect traffic IP of the remote host, if the ssh or scp prompts to enter the password, it suggests that SSH connection without password is not configured properly.
The IP assigned to the primary package is incorrect.
To understand the exact issue in the assigned IP, execute the cmmodnet command manually. Run this command with the IP address and subnet address assigned for the HADR_IP attribute in the package configuration file. If the command fails, then identify the root cause of the issue.
Recommended Action
Configure SSH connection without password properly.
Assign an appropriate IP to the primary package.
Primary package starts HADR as standby. In this case, both primary and standby packages come up with standby role.
Admin assigns an HADR_IP in package configuration file, which already exists in the network.
Perform the following steps to
44 Serviceguard toolkit for DB2 High Availability Disaster Recovery
