In a geographically dispersed DB2® pureScale® cluster
(GDPC) environment, install online fix pack updates on members and
cluster caching facilities (CFs) one at a time to update a DB2 pureScale instance
to a fix pack or special build with a higher code level while the
instance remains available.
Before you begin
Note: IBM support for
a geographically dispersed DB2 pureScale cluster (GDPC) implementation
requires engagement of IBM Lab
Services for separately charged initial installation services. Contact
your IBM sales
representative for details.
About this task
In a GDPC environment, you can update one or more members
or cluster caching facilities (CFs) while the remaining members and
CFs continue to process transactions. You must update all members
and CFs, and the tiebreaker host, before you can commit the changes
and update the DB2 pureScale instance.
If the members and CFs are located on the same host, you must apply
the fix pack update only once per host.
Restrictions
Procedure
To install an online fix pack update in a GDPC environment:
- Uncompress the fix pack or special build image to a directory
that is accessible to all members and CF hosts.
- Apply the fix pack online on each of the members one at
a time:
- Log on to the member server with root user authority.
- Issue the installFixPack command
as follows:
media-dir/installFixPack -p FP-install-path -I instance-name -online -l log-file-name -t trace-file-name
Where FP-install-path is
the directory where you want to install the fix pack and media-dir is
the directory where you uncompressed the fix pack image. FP-install-path must
be the same on all hosts. The -online parameter
is the default and can be omitted.
- Apply the fix pack online on the secondary CF:
- Log on to the secondary CF server with root user authority.
- Issue the installFixPack command
as follows:
media-dir/installFixPack -p FP-install-path -I instance-name -online -l log-file-name -t trace-file-name
Where FP-install-path is
the directory where you want to install the fix pack and media-dir is
the directory where you uncompressed the fix pack image. FP-install-path must
be the same on all hosts. The -online parameter
is the default and can be omitted.
- Apply the fix pack online on the primary CF:
- Ensure that the secondary CF of your DB2 pureScale instance
is in PEER state by issuing the following command as the instance
owner:
db2instance -list
The
secondary CF must be in PEER state before updating the primary CF. If
running
db2instance -list shows that the secondary
CF is in CATCHUP state, you can check the catch up progress percent
by querying the DB2_CF administrative view. For example:
db2 "SELECT ID as CF_ID, varchar(CURRENT_HOST,21) AS HOST, varchar(STATE,14) AS CF_STATE FROM SYSIBMADM.DB2_CF"
CF_ID HOST CF_STATE
------ --------------- --------------
128 cfserver56 CATCHUP(79%)
129 cfserver54 PRIMARY
2 record(s) selected.
The CATCHUP percentage value represents
the amount to which the secondary CF is caught up to the current state
of the primary CF.
- Log on to the primary CF server with root user authority.
- Issue the installFixPack command
as follows:
media-dir/installFixPack -p FP-install-path -I instance-name -online -l log-file-name -t trace-file-name
Where FP-install-path is
the directory where you want to install the fix pack and media-dir is
the directory where you uncompressed the fix pack image. FP-install-path must
be the same on all hosts. The -online parameter
is the default and can be omitted.
- Update the tiebreaker host:
- Enter maintenance mode from the old code level. For example:
<OLD-FP-install-path>/bin/db2cluster -cm -enter -maintenance
<OLD-FP-install-path>/bin/db2cluster -cfs -enter -maintenance
- To update the tiebreaker host, run installFixPack command
from the target fix pack image.
media-dir/installFixPack -b <OLD-FP-install-path> -p <FP-install-path> -L
Where FP-install-path is
the directory where you want to install the fix pack and media-dir is
the directory where you uncompressed the fix pack image. FP-install-path must
be the same on all hosts.For example:
media-dir/installFixPack -b /opt/ibm/db2/V10.5/ -p /opt/ibm/db2/V10.5fp4 -L
- Exit maintenance mode from the new code level: For
example:
<FP-install-path>/bin/db2cluster -cm -exit -maintenance
<FP-install-path>/bin/db2cluster -cfs -exit -maintenance
- Determine whether the online fix pack update was successful
on all members and CFs by issuing the following command:
media-dir/installFixPack -check_commit -I instance-name
If
the command is successful, you can continue with the next step.
Note: If you decide to move back to the previous
version of fix pack, you can cancel the online fix pack update. For
more information, see
Canceling online fix pack updates.
- Commit the online fix pack update so that your DB2 pureScale instance
is updated to the new fix pack level by issuing the following command:
media-dir/installFixPack -commit_level -I instance-name -l log-file-name -t trace-file-name
- Verify that your instance and databases show the new committed
fix pack level by issuing the following command as an instance user:
db2pd -ruStatus
- If you want to use capabilities specific to the fix pack,
update the system catalog objects in your databases:
- Log on as the instance owner.
- For each database in the instance, issue the db2updv105 command
as follows:
db2updv105 -d db-name