Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX Release README: B.06.00

located at
http://publib.boulder.ibm.com/infocenter/db2luw/v9/
topic/com.ibm.db2.udb.admin.doc/doc/c0008221.htm
NOTE:
The above steps from 1 to 12 have to be repeated on all nodes in the
cluster.
Above steps 5 to 10 are applicable for multi-partition database setup.
Single
partition users need not defer the instance creation while
installing as
mentioned in step 4. After the installation they can continue from
step 11
onwards
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Multiple Instance Configurations
If multiple instances run in the same cluster, repeat the
preceding steps
for each instance. For example, if a second instance (employee)
is to be
included in the configuration, you would create a second
volume group
(e.g., /dev/vg_employee), logical volume and filesystem with
mount point
(/mnt/employee) for the second instance. This configuration makes it
possible
to run several DB2 instances on one node, facilitating
failover/failback
of DB2 packages between nodes in the cluster.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Set up additional database logical volumes.
Commonly, the database will probably reside on several volume
groups and
logical volumes, which all need to be shared among the nodes
that are
able to run the DB2 instances. Again, using a naming convention
for the
VG(s) that includes the instance name could be used to associate a VG
with a
unique instance.
EXAMPLE:
Raw disk access for DB2 data:
/dev/vg01_payroll/rlvol1 #Raw logical volume DB2 data
/dev/vg02_payroll/rlvol1 #Raw logical volume DB2 data
/dev/vg03_payroll/rlvol2 #Raw logical volume DB2 data