Db2+hadr+tsa High Availability Test--DB2HAICU Configure TSA for automatic failover of faults
- Must be configured on the standby node first
[Root@db2-node02 ~]# Su-db2inst2
[Db2inst2@db2-node02 ~]$ DB2 "Get snapshot for database on GHAN"
HADR status
Role = Standby
Status = Peer
Synchronous mode = Synchronous
Connection status = Connected, 2015-12-24 08:32:52.872408
Peer window end = 2015-12-24 09:04:59.000000 (1450965899)
Peer window (seconds) = 120
Loss of pulsating signal = 0
Local host = 10.0.0.2
Local Service = Db2_hadr_ghan2
Remote host = 10.0.0.1
Remote Service = Db2_hadr_ghan1
Remote Instance = Db2inst2
Timeout (seconds) = 120
Primary log location (file, page, LSN) = S0000014. LOG, 3, 000000000972b8db
Alternate log location (file, page, LSN) = S0000014. LOG, 3, 000000000972b8db
Log interval run average (in bytes) = 0
Memory usage of the database:
---------------------
[Db2inst2@db2-node02 ~]$ Db2haicu
Welcome to the DB2 High Availability Instance Configuration Utility (DB2HAICU).
You can find detailed diagnostic information in the DB2 Server diagnostic log file Db2diag.log. You can also use the DB2PD utility to query the status of the cluster domain that you created.
For more information about using DB2HAICU to configure a clustered environment, see the "DB2 High Availability Instance Configuration Utility (DB2HAICU)" topic in the DB2 Information Center.
Db2haicu has determined that the current DB2 Database Manager instance is db2inst2. The cluster configuration that appears immediately applies to this instance.
DB2HAICU is collecting information about the current settings. It may take some time to complete this step because DB2HAICU needs to activate all the databases so that the instance discovers all the paths ...
When you use DB2HAICU to configure a clustered environment, the cluster domain is created. For more information, see the "Create a cluster domain using DB2HAICU" topic in the DB2 Information Center. DB2HAICU is searching for an existing active cluster domain on the current machine ...
DB2HAICU the cluster domain was not found on this machine. DB2HAICU will now query the system to get information about the cluster nodes in order to create a new cluster domain ...
DB2HAICU the cluster domain was not found on this machine. To continue configuring the cluster environment for high availability, you must create a cluster domain or DB2HAICU will exit.
Do you want to create a domain and continue? [1]
1. Yes
2. No
1
Create a unique name for the new domain:
Db2ha
You must now add the nodes to the new domain.
How many cluster nodes will the domain db2ha contain?
2
Enter the host name of the machine you want to add to the domain:
Db2-node01
Enter the host name of the machine you want to add to the domain:
Db2-node02
Now, DB2HAICU can create a new domain that contains the 2 machines you specify. If you choose not to create a domain now, then DB2HAICU will exit.
Do you want to create a domain now? [1]
1. Yes
2. No
1
Creating domain db2ha in cluster ...
The domain db2ha was successfully created in the cluster.
You can now configure the quorum device for the domain. For more information, see the "Quota Devices" topic in the DB2 Information Center. If you do not configure a quorum device for a domain, the operator must manually intervene when some machines in the cluster lose connectivity.
Do you want to configure a quorum device for a domain called db2ha? [1]
1. Yes
2. No
1
The following is a list of supported fixed device types:
1. Network quotas
Enter the number that corresponds to the type of fixed device you want to use: [1]
1
Specify the network address of the quota device:
108.88.3.254
Configuring quota devices for domain db2ha ...
A quota device was successfully configured for domain db2ha.
Cluster Manager found 4 network interface cards in each machine within the domain. You can use DB2HAICU to create networks for these network interface cards. For more information, see the "Create a network using DB2HAICU" topic in the DB2 Information Center
Do you want to create a network for these network interface cards? [1]
1. Yes
2. No
1
Enter the network name of the network interface card eth0 on the cluster node DB2-NODE01:
1. Create a new public network for this network interface card.
2. Create a new private network for this network interface card.
Enter the choices you made:
1
Are you sure you want to add the network interface card eth0 on the cluster node db2-node01 to the network db2_public_network_0? [1]
1. Yes
2. No
1
Adding the network interface card eth0 on the cluster node db2-node01 to the network db2_public_network_0 ...
Successfully added the network interface card eth0 on the cluster node db2-node01 to the network db2_public_network_0.
Enter the network name of the network interface card eth0 on the cluster node DB2-NODE02:
1. Db2_public_network_0
2. Create a new public network for this network interface card.
3. Create a new private network for this network interface card.
Enter the choices you made:
1
Are you sure you want to add the network interface card eth0 on the cluster node DB2-NODE02 to the network db2_public_network_0? [1]
1. Yes
2. No
1
Adding the network interface card eth0 on the cluster node DB2-NODE02 to the network db2_public_network_0 ...
Successfully added the network interface card eth0 on the cluster node DB2-NODE02 to the network db2_public_network_0.
Enter the network name of the network interface card eth1 on the cluster node DB2-NODE02:
1. Db2_public_network_0
2. Create a new public network for this network interface card.
3. Create a new private network for this network interface card.
Enter the choices you made:
3
Are you sure you want to add the network interface card eth1 on the cluster node DB2-NODE02 to the network db2_private_network_0? [1]
1. Yes
2. No
1
Adding the network interface card eth1 on the cluster node DB2-NODE02 to the network db2_private_network_0 ...
Successfully added the network interface card eth1 on the cluster node DB2-NODE02 to the network db2_private_network_0.
Enter the network name of the network interface card eth1 on the cluster node DB2-NODE01:
1. Db2_private_network_0
2. Db2_public_network_0
3. Create a new public network for this network interface card.
4. Create a new private network for this network interface card.
Enter the choices you made:
1
Are you sure you want to add the network interface card eth1 on the cluster node db2-node01 to the network db2_private_network_0? [1]
1. Yes
2. No
1
Adding the network interface card eth1 on the cluster node db2-node01 to the network db2_private_network_0 ...
Successfully added the network interface card eth1 on the cluster node db2-node01 to the network db2_private_network_0.
Retrieving high availability configuration parameters for instance Db2inst2 ...
The cluster Manager name configuration parameter (high availability configuration parameter) is not set. For more information, see the "cluster_mgr-Cluster Manager name configuration Parameters" topic in the DB2 Information Center. Do you want to set the high availability configuration parameters?
The following are valid settings for high availability configuration parameters:
1.TSA
2. Suppliers
Enter a value for the high availability configuration parameter: [1]
1
Setting the High availability configuration parameter for instance Db2inst2 to TSA.
Adding DB2 database partition 0 to the cluster ...
Successfully added DB2 database partition 0 to the cluster.
Do you want to validate and automate Hadr failover for the HADR database GHAN? [1]
1. Yes
2. No
1
Adding HADR database GHAN to domain ...
The cluster node 10.0.0.1 could not be found in the domain. Please re-enter the host name.
Db2-node01
The cluster node 10.0.0.2 could not be found in the domain. Please re-enter the host name.
Db2-node02
Adding HADR database GHAN to domain ...
The HADR database GHAN has been determined to be highly available. However, this database cannot be added to the cluster in this node because DB2HAICU detects that this node is an alternative node for the HADR database GHAN. In the HADR database
Run Db2haicu on the primary node of the GHAN to configure the database to be automatically failed over.
All cluster configurations have been successfully completed. Db2haicu is exiting ...
[Db2inst2@db2-node02 ~]$
- Configuring on the Master node
[Db2inst2@db2-node01 ~]$ Db2haicu
Welcome to the DB2 High Availability Instance Configuration Utility (DB2HAICU).
You can find detailed diagnostic information in the DB2 Server diagnostic log file Db2diag.log. You can also use the DB2PD utility to query the status of the cluster domain that you created.
For more information about using DB2HAICU to configure a clustered environment, see the "DB2 High Availability Instance Configuration Utility (DB2HAICU)" topic in the DB2 Information Center.
Db2haicu has determined that the current DB2 Database Manager instance is db2inst2. The cluster configuration that appears immediately applies to this instance.
DB2HAICU is collecting information about the current settings. It may take some time to complete this step because DB2HAICU needs to activate all the databases so that the instance discovers all the paths ...
When you use DB2HAICU to configure a clustered environment, the cluster domain is created. For more information, see the "Create a cluster domain using DB2HAICU" topic in the DB2 Information Center. DB2HAICU is searching for an existing active cluster domain on the current machine ...
Db2haicu found a cluster called db2ha on this machine. The cluster configuration that appears immediately applies to this domain.
Retrieving high availability configuration parameters for instance Db2inst2 ...
The cluster Manager name configuration parameter (high availability configuration parameter) is not set. For more information, see the "cluster_mgr-Cluster Manager name configuration Parameters" topic in the DB2 Information Center. Do you want to set the high availability configuration parameters?
The following are valid settings for high availability configuration parameters:
1.TSA
2. Suppliers
Enter a value for the high availability configuration parameter: [1]
1
Setting the High availability configuration parameter for instance Db2inst2 to TSA.
Adding DB2 database partition 0 to the cluster ...
Successfully added DB2 database partition 0 to the cluster.
Do you want to validate and automate Hadr failover for the HADR database GHAN? [1]
1. Yes
2. No
1
Adding HADR database GHAN to domain ...
The cluster node 10.0.0.2 could not be found in the domain. Please re-enter the host name.
Db2-node02
The cluster node 10.0.0.1 could not be found in the domain. Please re-enter the host name.
Db2-node01
Adding HADR database GHAN to domain ...
The HADR database GHAN was successfully added to the domain.
Do you want to configure the virtual IP address for the HADR database GHAN? [1]
1. Yes
2. No
1
Enter the virtual IP address:
108.88.3.107
Enter the subnet mask for the virtual IP address 108.88.3.107: [255.255.255.0]
255.255.255.0
Select the network for the virtual IP address 108.88.3.107:
1. Db2_private_network_0
2. Db2_public_network_0
Enter the choices you made:
2
Adding virtual IP address 108.88.3.107 to domain ...
The virtual IP address 108.88.3.107 was successfully added to the domain.
All cluster configurations have been successfully completed. Db2haicu is exiting ...
[Db2inst2@db2-node01 ~]$
[Root@db2-node02 ~]# Lssam
Online IBM. Resourcegroup:db2_db2inst2_db2-node01_0-rg Nominal=online
'-Online IBM. Application:db2_db2inst2_db2-node01_0-rs
'-Online IBM. Application:db2_db2inst2_db2-node01_0-rs:db2-node01
Online IBM. Resourcegroup:db2_db2inst2_db2-node02_0-rg Nominal=online
'-Online IBM. Application:db2_db2inst2_db2-node02_0-rs
'-Online IBM. Application:db2_db2inst2_db2-node02_0-rs:db2-node02
Online IBM. Resourcegroup:db2_db2inst2_db2inst2_ghan-rg Nominal=online
|-Online IBM. Application:db2_db2inst2_db2inst2_ghan-rs
|-Online IBM. Application:db2_db2inst2_db2inst2_ghan-rs:db2-node01
'-Offline IBM. Application:db2_db2inst2_db2inst2_ghan-rs:db2-node02
'-Online IBM. Serviceip:db2ip_108_88_3_107-rs
|-Online IBM. Serviceip:db2ip_108_88_3_107-rs:db2-node01
'-Offline IBM. Serviceip:db2ip_108_88_3_107-rs:db2-node02
Online IBM. Equivalency:db2_db2inst2_db2-node01_0-rg_group-equ
'-Online IBM. Peernode:db2-node01:db2-node01
Online IBM. Equivalency:db2_db2inst2_db2-node02_0-rg_group-equ
'-Online IBM. Peernode:db2-node02:db2-node02
Online IBM. Equivalency:db2_db2inst2_db2inst2_ghan-rg_group-equ
|-Online IBM. Peernode:db2-node01:db2-node01
'-Online IBM. Peernode:db2-node02:db2-node02
Online IBM. Equivalency:db2_private_network_0
|-Online IBM.NETWORKINTERFACE:ETH1:DB2-NODE02
'-Online ibm.networkinterface:eth1:db2-node01
Online IBM. Equivalency:db2_public_network_0
|-Online IBM.NETWORKINTERFACE:ETH0:DB2-NODE01
'-Online IBM.NETWORKINTERFACE:ETH0:DB2-NODE02
(LSRSRC-API)/usr/sbin/rsct/bin/lsrsrc-api:2612-023 resource not found.
Lssam: An unexpected RMC error occurred. The RMC return code is 1.
[Root@db2-node02 ~]#
http://www.bkjia.com/PHPjc/1084018.html www.bkjia.com true http://www.bkjia.com/PHPjc/1084018.html techarticle Db2+hadr+tsa High Availability test--DB2HAICU Configuring the TSA to implement a failover network architecture must first be configured on the standby node [root@db2-node02 ~]# Su-db2inst2 [db2inst2@db2-node02 ~]$...
