DB2 10.5 for Linux, UNIX, and Windows

Canceling online fix pack updates

Canceling an online fix pack update on a member or cluster caching facility (CF) requires that you reinstall the fix pack software with the same code level as the current effective code level.

Before you begin

Ensure that the fix pack or special build image with the same code level as the current effective code level is available in a directory that is accessible to all members and CF hosts, by issuing the db2pd -ruStatus command.
Ensure that no other fix pack updates are in progress.

About this task

You can cancel an online fix pack update that was applied on a member or cluster caching facility (CF) to fall back to the same release as the current effective code level.

Important: The Tivoli® System Automation (TSA) and the IBM General Parallel File System (GPFS™) cannot be downgraded with the -f level parameter. To downgrade these systems you must complete the following steps:

Drop the instance.
Uninstall DB2® including TSA/GPFS.
Reinstall DB2 PureScale with the TSA/GPFS level required.

Procedure

To cancel an online fix pack update:

Uncompress the fix pack or special build image to a directory that is accessible to all members and CF hosts.
Cancel an online fix pack update on each of the members that were updated by performing the following actions:
1. Log on to the member server with root user authority.
2. Issue the installFixPack command as follows:
```
media-dir/installFixPack -p FP-installed-path -f level -I instance-name -online -l log-file-name -t trace-file-name
```
  Where FP-installed-path is the directory where you installed the fix pack with the same code level as the current effective code level and media-dir is the directory where you uncompressed the fix pack image with the same code level as the current effective code level.
Cancel an online fix pack update on the secondary CF by performing the following actions:
1. Log on to the secondary CF server with root user authority.
2. Issue the installFixPack command as follows:
```
media-dir/installFixPack -p FP-installed-path -f level -I instance-name -online -l log-file-name -t trace-file-name
```
  Where FP-installed-path is the directory where you installed the fix pack with the same code level as the current effective code level and media-dir is the directory where you uncompressed the fix pack image with the same code level as the current effective code level.
Cancel an online fix pack update on the primary CF by performing the following actions:
1. 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.
2. Log on to the primary CF server with root user authority.
3. Issue the installFixPack command as follows:
```
media-dir/installFixPack -p FP-installed-path -f level -I instance-name -online -l log-file-name -t trace-file-name
```
  Where FP-installed-path is the directory where you installed the fix pack with the same code level as the current effective code level and media-dir is the directory where you uncompressed the fix pack image with the same code level as the current effective code level.
Verify that your instance, members, and CFs show the same code level and architectural level by issuing the following command
```
db2pd -ruStatus
```

Example

Assume that you have a DB2 pureScale instance running on Version 10.5 Fix Pack X with three members and 2 CFs. The install directory is FPX-install-dir.

You apply an online fix pack update to Version 10.5 Fix Pack Y on member1 and member2 specifying FPY-install-dir as the install directory.

To cancel the update and fall back to Version 10.5 Fix Pack X, you reapply Version 10.5 Fix Pack X on member1 and member2:

FPX-media-dir/installFixPack -p FPX-install-dir -f level -I instance-name -online -l log-file-name -t trace-file-name

where FPX-mediadir is the directory with the fix pack image with Version 10.5 Fix Pack X and FPX-install-dir is the installation directory with Version 10.5 Fix Pack X.

Because the CFs were not updated, they are still running on Version 10.5 Fix Pack X.

Verify that all the members and CFs are running at Version 10.5 Fix Pack X by issuing the following command:

db2pd -ruStatus