Installing DB2 pureScale Feature using the db2_install command

This topic guides you through the process of installing IBM® DB2® pureScale® Feature using the db2_install command.

1. Make the DB2 installation image available. After downloading the DB2 database product image, decompress and untar the product file:
   1. Decompress and untar the product file using the gunzip -c server.tar.gz | tar -xf - command, where product represents the name of the downloaded product.
   2. Change directory using the cd ./server command
2. Log in as root.
3. On the IIH, to install the DB2 pureScale Feature, run the db2_install command. This command installs the DB2 database product, Tivoli® SA MP, and GPFS™.
   Note:
   For example:

   db2_install -b DB2DIR -p SERVER -t /tmp/db2_install.trc -l /tmp/db2_install.log

   where DB2DIR represents the location where you want to install the DB2 pureScale Feature image. This path has to be the same on all the hosts. If the DB2DIR exists, it must be empty before the installation. The default DB2DIR is /opt/IBM/db2. The -t and -l options are recommended so that trace and log files are generated.
4. Verify that your DB2 database product is installed. Run the /usr/local/bin/db2ls command.
5. Verify that Tivoli SA MP and GPFS are installed on the system.
   1. To verify the installation of Tivoli SA MP on Linux, run the rpm command. The output of this command should be similar to the following example:

      $ rpm -aq | grep -e "sam\." -e "sam\-" 
      sam.adapter-3.2.2.1-12074
      sam-3.2.2.1-12074
      sam.sappolicy-3.2.2.1-12074 

   2. To verify the installation of Tivoli SA MP on AIX®:

      lslpp -l | grep sam-*

   3. To verify the installation of GPFS on Linux, run the rpm -aq | grep gpfs command. The output of this command should be similar to the following:

      hostinst1:/opt/ibm/db2/V10.5/sd/db2/linuxamd64/gpfs # rpm -aq | grep gpfs
      gpfs.msg.en_US-3.5.0.4
      gpfs.base-3.5.0.4
      gpfs.docs-3.5.0.4
      gpfs.gpl-3.5.0.4

   4. To verify the installation of GPFS on AIX, run:

      lslpp -l | grep -i gpfs*

6. Ensure the required users and groups are created (as detailed in your installation plan).
7. Run the following command as root to set up the initial DB2 pureScale instance specifying a host as a DB2 member and another host as a cluster caching facility. You can find the db2icrt command in the DB2DIR/instance directory. You can only specify one DB2 member and one cluster caching facility during the initial setup of the DB2 pureScale instance. You can add additional DB2 members and cluster caching facilities using the db2iupdt command.
   Note:

   • The netname represents the cluster interconnect netname which corresponds to the communication adapter port used for high speed communication between DB2 members and cluster caching facilities in the DB2 instance.
   • For the host name, you need to use the same host name format as the return value of the hostname command.
   • The /etc/hosts file must have this format:<IPADDRESS> <Long name with domain> <short name>

   db2icrt -d -m member_hostname -mnet member_netname1
      -cf CF_hostname -cfnet CF_netname2
      -instance_shared_dev disk1_name -tbdev Shared_device_for_tiebreaker
      -u fencedID instname

   For example,

    db2icrt -d -m h1.domain.com -mnet h1.domain.com-ib0
      -cf h2.domain.com -cfnet h2.domain.com-ib0
      -instance_shared_dev  /dev/hdisk1 -tbdev 129.42.38.1
      -u db2fenc1 db2sdin1

   creates DB2 pureScale instance db2sdin1 with a DB2 member named h1.domain.com, a netname of h1.domain.com-ib0, and cluster caching facility h2.domain.com with a netname of h2.domain.com-ib0. It will also specify the shared file system device path as /dev/hdisk1, and set the tiebreaker disk as /dev/hdisk2.