You can use the db2iupdt or the db2isetup command
to add new DB2® members
or an additional cluster caching facility (CF)
to your IBM® DB2 pureScale® instance.
Before you begin
When you issue the db2iupdt or
the db2isetup command to add a member or a CF,
ensure that you review the prerequisites and the preinstallation checklist
so that your instance and hosts are compliant.
You can alternatively
issue the db2isetup command to extend the DB2 pureScale instance
to multiple hosts (as opposed to the db2iupdt -add command
that can extend the instance only one member or one CF at
a time).
About this task
Restrictions
Procedure
- If you are adding a member to a
CF host, you must stop the CF by using the db2stop command.
The db2stop command must be targeted to the CF
that is running on the host where your are adding a member.
- You can use either the db2iupdt command
or the db2isetup command:
- Using the db2isetup command:
- Issue the db2isetup command to start the DB2 Instance
Setup wizard.
- Proceed to the "Setup a DB2 instance" panel. Select the Configure
new function for an existing DB2 instance option and click Next.
- On the Host List panel, add the hosts that
will be part of the DB2 pureScale instance.
Hosts are validated as they are added to the list. The existing hosts
for the instance are automatically loaded into the host list, but
you cannot perform any action on them. After you add the hosts you
want, click Next.
- Click Finish to perform the action.
- Using the db2iupdt command:
Run
the following command from a host that is already part of the DB2 pureScale instance:
DB2DIR/instance/db2iupdt
-add [-m <member_host> -mnet <netname>] | [-cf <cf_host> -cfnet <netname>]
-i <db2sshid>
-mid <MemberId>
instname
- DB2DIR is the directory where
the DB2 pureScale software
is installed.
- 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.
- If
you are adding a member to a host with an existing member, the new
member must have the exact same netname (or set of netnames) as the
existing member.
- (optional)
For DB2 managed GPFS™, db2sshid is the non-root
user ID required to SSH between hosts in the GPFS domain.
- (optional)
If you are adding a member, use the –mid option
to indicate the member identifier for the new member.
- For the host name, you need to use the same
host name format as the return value of the hostname command.
Use the –m option for a member or the –cf option
for a cluster caching facility to
specify which type of host you want to add. You must select one, but
not both. If you want to add multiple hosts to the existing instance
at one time, use the db2isetup command.
Example
For example, the following
db2iupdt command
adds the host named
member1 with the
cluster interconnect netname member1-ib0 as
a member to the
DB2 pureScale instance:
db2iupdt -add -m member1 -mnet member1-ib0 -i db2ssh1 db2sdin1
The
following
db2iupdt command adds the host named
cf2 as
secondary
cluster caching facility with
four
cluster interconnect netnames
to the
DB2 pureScale instance
db2sdin1:
db2iupdt -add -cf cf2 -cfnet cf2-ib0,cf2-ib1,cf2-ib2,cf2-ib3 -i db2ssh1 db2sdin1
The
four
cluster interconnect netnames
are
cf2-ib0,
cf2-ib1,
cf2-ib2,
and
cf2-ib3.
The
following
db2iupdt command adds a member host with
a specific member identifier without stopping the instance:
db2iupdt -add -m member2 -mnet member2-ib0 -mid 100 db2sdin1
Start
the new member:
db2start member 100 db2sdin1
The
following example adds a member to an existing CF host. You must first
stop the CF on the host where you want to add the member. This example
adds a member to cf2
db2stop CF 128
db2iupdt -add -m cf2 -mnet cf2-ib0 db2sdin1
Start
the CF and the new member:
db2start CF 128
db2start member 101
What to do next
If you are converting your existing DB2
environment to a DB2 pureScale environment,
perform the post-conversion tasks for a DB2 pureScale environment.