This topic guides you through the process of installing IBM
Db2
pureScale Feature using
the db2_install command.
Before you begin
- Ensure you have created your Db2
pureScale Feature installation
plan, that your system meets the prerequisites, and that you have
performed the preinstallation tasks.
About this task
The
manual installation process is outlined as follows:
- Log in as root.
- Run the db2_install command to install the Db2 database product on
the installation-initiating host
(IIH)
- Run the db2icrt command on the IIH to create one member and one cluster caching facility. The
db2icrt command will copy the Db2 database product to
the second host and run the install process before creating the member and cluster caching facility.
- Run the db2iupdt to add members and cluster caching facilities. The
db2iupdt command will copy the Db2 database product to
the new host and install it before creating the member or the CF.
Procedure
-
Make the Db2 installation image available. After downloading the Db2 database product
image, decompress and untar the product file:
- 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.
- Change directory using the
cd ./server
command
- Log in as root.
-
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
IBM Storage Scale.
For
example:
db2_install -b DB2DIR -p SERVER -f PURESCALE -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.
-
Verify that your Db2 database product is
installed. Run the /usr/local/bin/db2ls command.
- Verify that Tivoli
SA MP and
IBM Storage Scale are installed on the system.
- 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
-
To verify the installation of Tivoli
SA MP on AIX®:
- To verify the installation of IBM Storage Scale 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
-
To verify the installation of IBM Storage Scale on AIX, run:
-
Ensure the required users and groups are created (as detailed
in your installation plan).
-
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 /dev/hdisk2
-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
.
What to do next
You
can add other hosts to your Db2
pureScale instance
using the db2iupdt -add command.