162 DB2 Integrated Cluster Environment Deployment Guide
# rsh db2rb02 /mnt/cdrom/db2setup -r /root/db2ese.rsp
In this example, we assume that:
db2rb02 is the hostname of the computer to install DB2.
The installation medium is accessible under /mnt/cdrom.
The response file is saved as /root/db2ese.rsp.
If you are managing computers with CSM, installation can be done more easily
with dcp and dsh commands. In this case you just create a response file on one
of the computers, possibly on the management server, without actually installing,
and distribute it to all managed computers with dcp. Then you can invoke
db2setup on all managed computers at once with dsh, as below.
# dcp -a db2ese.rsp /root
# dsh -a /mnt/cdrom/db2setup -r /root/db2ese.rsp
Apply the latest FixPak if available
At the time of writing, no fixpak is available for DB2 UDB V8.2. But you should
always check fixpak availability prior to installation. Check the URL below for
FixPak availability.
http://www.ibm.com/software/data/db2/udb/suppolrt.html
If any fixpak is available, we strongly recommend that you apply the fixpak before
you create instances.
4.3.4 Preparation for instance creation
Before creating an instance, a few preparations are needed.
1. Prepare user IDs and group IDs.
Before you create an instance, you must have the instance owner user and
fenced user prepared, along with their groups. They must have identical ID
across all computers. See “Create groups and users” on page 151.
2. Prepare instance owner's home directory.
All participating computers must share the instance owner's home directory.
Typically the home directory is created in a dedicated file system. This file
system is mounted on one of the participants and exported to the others via
NFS. See “Ensure NFS is running” on page 147.

Get DB2 Integrated Cluster Environment Deployment Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.