Response file considerations for a Db2 pureScale environment

In addition to general response file considerations, a Db2 pureScale environment has additional considerations.

A response file installation might also be referred to as a silent installation or an unattended installation. The response file can be used to:
  • Install the Db2 pureScale Feature and create the Db2 pureScale instance in the same run across all hosts, or
  • Install the Db2 pureScale Feature across all hosts, then run the db2icrt, db2iupdt, or db2isetup commands to manually create and extend a Db2 pureScale instance.
A response file can be created in either of the following ways:
  • Using the Db2 Setup wizard,
  • using the sample response file, or
  • using the db2isetup command.
The Db2 pureScale Feature sample response file, db2dsf.rsp, is located in /opt/IBM/db2/V10.5/install/db2/platform/samples directory, where platform refers to the appropriate operating system.
You must consider the following before proceeding with a response file installation in a Db2 pureScale environment:
  • A clean system is recommended. In a clean system, neither of the following products is already installed:
    • IBM® General Parallel File System (GPFS), nor
    • IBM Tivoli® System Automation for Multiplatforms
  • The response file includes information about all the participating hosts. When using a response file, the db2setup or db2isetup command can be run from any of the hosts. For additional usage notes, see the specific command.
  • Any keyword with incorrect syntax results in the entire response file being invalid.
  • Keywords available for a Db2 pureScale Feature installation. Some keywords are mandatory, some are optional depending on the state of your system. For keyword details, see the Response file keywords topic.
    • HOST
    • host_identifier.HOSTNAME
    • Instance creation settings:
      • instance_identifier.PREFERRED_PRIMARY_CF
      • instance_identifier.PREFERRED_SECONDARY_CF
      • instance_identifier.MEMBER
      • instance_identifier.DB2CF_PORT_NUMBER
      • instance_identifier.DB2CF_MGMT_PORT_NUMBER
  • The following keyword interdependencies must be adhered to when using the keywords:
    • The recommended Db2 pureScale environment setup for the Db2 pureScale Feature is four hosts: two cluster caching facilities and two members. For example:
      * Product Installation
      FILE = /opt/IBM/db2/V10.5
      * ----------------------------------------------
      * Instance properties
      * ----------------------------------------------
      INSTANCE = inst1
      inst1.PREFERRED_PRIMARY_CF = host1
      inst1.PREFERRED_SECONDARY_CF = host2
      inst1.MEMBER = host3
      inst1.MEMBER = host4
      inst1.TYPE = dsf
      * Instance-owning user
      inst1.NAME = db2sdin1
      inst1.GROUP_NAME = db2iadm1
      inst1.HOME_DIRECTORY = /home/db2sdin1
      inst1.PASSWORD = 937436363038076535953807826033486554358563633346043342
      inst1.SVCENAME = db2c_db2sdin1
      inst1.PORT_NUMBER = 50000
      inst1.FCM_PORT_NUMBER = 60000
      inst1.MAX_LOGICAL_NODES = 1
      inst1.DB2CF_MGMT_PORT_NUMBER = 56000
      inst1.DB2CF_PORT_NUMBER = 56001
      * Fenced user
      inst1.FENCED_USERNAME = db2sdfe1
      inst1.FENCED_GROUP_NAME = db2fadm1
      inst1.FENCED_HOME_DIRECTORY = /home/db2sdfe1
      inst1.FENCED_PASSWORD = 786359555684387445670627543570638933213376259440013362
      * Installed Languages
      LANG = EN
      * Host Information
      HOST = host1
      host1.HOSTNAME = coralpibinstall05
      host1.CLUSTER_INTERCONNECT_NETNAME = coralpibinstall05-ib0
      HOST = host2
      host2.HOSTNAME = coralpibinstall06
      host2.CLUSTER_INTERCONNECT_NETNAME = coralpibinstall06-ib0
      HOST = host3
      host3.HOSTNAME = coralpibinstall07
      host3.CLUSTER_INTERCONNECT_NETNAME = coralpibinstall07-ib0
      HOST = host4
      host4.HOSTNAME = coralpibinstall08
      host4.CLUSTER_INTERCONNECT_NETNAME = coralpibinstall08-ib0
      * ----------------------------------------------
      * Shared file system settings
      * ----------------------------------------------
      INSTANCE_SHARED_DEVICE_PATH = /dev/hdisk10
      * ----------------------------------------------
      * Tiebreaker settings
      * ----------------------------------------------
      • instance_identifier.PREFERRED_PRIMARY_CF - identifies the host designated as the preferred primary cluster caching facility for the instance. One host must be specified as the preferred primary cluster caching facility.
      • instance_identifier.PREFERRED_SECONDARY_CF - identifies the host designated as the secondary cluster caching facility for the instance.
      • instance_identifier.MEMBER - identifies the host designated as a member for the instance.
    • File system keywords. When the Db2 pureScale instance is created, one of the cluster file system related keywords must be specified. The keyword chosen indicates whether an existing User-Managed GPFS file system, or a created GPFS file system is used:
      • INSTANCE_SHARED_DEVICE_PATH - indicates a Db2 Managed clustered file system method is used. This is the recommended keyword. This keyword identifies the device path used to create a file system for shared files. There can be no file system already on the disk.
      • INSTANCE_SHARED_DIR - indicates a User-Managed file system method is used. This keyword identifies the path to an existing GPFS file system for storing shared files.
      Only one of the file system keywords should be specified, not both. If both keywords are specified, INSTANCE_SHARED_DIR is ignored. However, if the global registry record DEFAULT_INSTPROF contains a value, this means there is an existing file system. (This can happen if a Db2 pureScale instance was created and then dropped. For details see the db2idrop command.) If the global registry record DEFAULT_INSTPROF contains a value, neither keyword needs to be specified.
    • The DB2_CLUSTER_SERVICES_TIEBREAKER_DEVICE_PATH keyword is the RSCT tiebreaker setting. It identifies the device path to setup a cluster services tiebreaker. The tiebreaker is required for cluster recovery purposes when a Db2 pureScale instance is split in half because of a communication failure. The tiebreaker determines which half of the Db2 pureScale instance remains online. The path specified for this keyword should be dedicated, and not used for anything else. It should be at least 25 MBs in size, and accessible by all hosts. The path specified for this keyword must be different from the INSTANCE_SHARED_DEVICE_PATH keyword.


The following example installs the Db2 pureScale Feature using response file db2dsf.rsp:
db2setup -r /mydir/db2dsf.rsp -l /tmp/db2setup.log -t /tmp/db2setup.trc 
where mydir represent the directory where you saved the db2dsf.rsp file.