SET_MIRROR_CLUSTER procedure

Edit online

The SET_MIRROR_CLUSTER procedure defines the cluster configuration of the primary and secondary nodes.

This procedure can only be called on the primary node and the replication state for SYSBAS must be NOT MIRRORED.

Providing the cluster information on the procedure call is optional. If all parameters are omitted and the primary node is not already part of a cluster, this procedure will create a cluster named DB2MCLU and a device domain named DB2MDOMAIN using system-generated node names and IP addresses.
  • Specify the cluster name if the primary node is not already part of a cluster and you want the cluster to be created using the specified name.
  • Specify the device domain name if the primary node is not already a member of a device domain and you want the device domain to be created using the specified name.
  • Specify the primary node detail if the primary node is not already part of a cluster and you want the cluster to be created using the specified node name and IP addresses.
  • Specify the secondary node detail if you want the secondary node to be added to the cluster using the specified node name and IP addresses.
A cluster is a required component of Db2® Mirror for the following reasons:
  • To allow database IASPs to be cloned so that the IASP name space and number are identical between the node pair.
  • To manage IFS IASPs.
  • To enable IBM® PowerHA® SystemMirror® for i to manage objects in the Administrative Domain.
  • To allow integration with a PowerHA disaster recovery solution.
  • To integrate with an existing cluster.

Authorization: For the authority needed to use this procedure, see Authorization.

Read syntax diagramSkip visual syntax diagram SET_MIRROR_CLUSTER ( CLUSTER_NAME => cluster-name ,DEVICE_DOMAIN_NAME => device-domain-name ,PRIMARY_NODE_NAME => primary-node-name ,PRIMARY_NODE_PRIMARY_IP => primary-node-primary-ip ,PRIMARY_NODE_SECONDARY_IP => primary-node-secondary-ip ,SECONDARY_NODE_NAME => secondary-node-name ,SECONDARY_NODE_PRIMARY_IP => secondary-node-primary-ip ,SECONDARY_NODE_SECONDARY_IP => secondary-node-secondary-ip )

The schema is QSYS2.

cluster-name
A character or graphic string that specifies the name of the cluster to which the nodes are being added. If this parameter is omitted and the primary node is not already part of a cluster, DB2MCLU will be used.
device-domain-name
A character or graphic string that specifies the device domain to which the nodes are being added. If this parameter is omitted and the primary node is not already part of a device domain, DB2MDOMAIN will be used.
primary-node-name
Specifies the cluster node id of the primary node in the cluster and device domain. If this parameter is omitted and the primary node is not already part of a cluster, the system name will be used.
primary-node-primary-ip
Specifies the preferred IP address in either IPv4 or IPv6 format for the primary node that can be used by Cluster Resource Services to communicate between the node pair in the cluster. If not provided, Db2 Mirror will choose an IP address.
primary-node-secondary-ip
Specifies a second IP address in either IPv4 or IPv6 format for the primary node that can be used by Cluster Resource Services to communicate between the node pair in the cluster. If not provided, a second IP address will not be configured.
secondary-node-name
Specifies the cluster node id of the secondary node in the cluster and device domain. If this parameter is omitted and the primary node is not already part of a cluster, the secondary node name will be used.
secondary-node-primary-ip
Specifies the preferred IP address in either IPv4 or IPv6 format for the secondary node that can be used by Cluster Resource Services to communicate between the nodes in the cluster. If this parameter is omitted and the primary node is not already part of a cluster, Db2 Mirror will choose an IP address.
secondary-node-secondary-ip
Specifies a second IP address in either IPv4 or IPv6 format for the secondary node that can be used by Cluster Resource Services to communicate between the nodes in the cluster. If this parameter is omitted and the primary node is not already part of a cluster, a second IP address will not be configured.

Example

  • Create a cluster using default cluster name DB2MCLU and default device domain name DB2MDOMAIN containing PROD1 and PROD2.
       CALL QSYS2.SET_MIRROR_CLUSTER(PRIMARY_NODE_NAME => 'PROD1',  
                                 PRIMARY_NODE_PRIMARY_IP => '1.1.1.1',
                                 SECONDARY_NODE_NAME => 'PROD2',
                                 SECONDARY_NODE_PRIMARY_IP => '1.1.1.2');