Revert an existing Db2 database product to a previous fix pack level (Linux and Unix)
After installing a mod pack or fix pack, you can revert to a previous fix pack or the GA level of the Db2 database product.
About this task
On Linux® and UNIX operating systems, you can go back to an earlier fix pack or the GA level.
On Windows operating systems, you cannot go back to a previous fix pack or the GA level unless you uninstall the current fix pack, then install the previous level.
Note: After reverting your current Db2 database to the previous mod pack or fix pack, static
packages must be rebound. If you ran
db2updv115 on the current level, you must run
db2dupv115 -a after moving to a lower level.If you plan to run
db2updv115, ensure that your back up your privileges before running the utility.
For more information, see the description for the -a option in db2updv115 - Update
database to version 11.5 mod pack or fix pack command.
Procedure
- Log on to the server as the root user.
- Extract the fix pack image to which you want to revert.
- Install the fix pack image using the installFixPack command with the
-f levelto force a level check bypass. Specify a different directory than the currently installed image you want to update using the-poption.For example, if you currently have a Db2version 11.5.5 image on /opt/ibm/db2/V11.5.5 and are trying to revert back to version 11.5.4, run the following command:
Where FP-image is the fix pack image extracted, current-installation-dir is /opt/ibm/db2/V11.5.5, and install-FP-dir is /opt/ibm/db2/v11.5.4 in the example.<FP-image>./installFixPack -f level -b <current-installation-dir> -p <install-FP-dir> - Update each instance by issuing the db2iupdt command with the
-f leveloption to force a level check bypass. For example:
Where install-FP-dir is /opt/ibm/db2/v11.5.4 in the example.<install-FP-dir>/instance ./db2iupdt -d -f level [-u fenced-ID] instance-name - Verify that the instances are running the updated fix pack code by issuing the db2level command as the instance owner.