DB2 Version 9.7 for Linux, UNIX, and Windows

Applying fix packs

It is recommended that you keep your DB2® database environment running at the latest fix pack level to ensure problem-free operation. To update the installed DB2 database products successfully, perform all of the necessary preinstallation and post-installation tasks.

About this task

A DB2 fix pack contains updates and fixes for problems (Authorized Program Analysis Reports, or "APARs") found during testing at IBM, as well as fixes for problems reported by customers. The APARLIST.TXT file describes the fixes contained in each fix pack and it is available for download at ftp://ftp.software.ibm.com/ps/products/db2/fixes/english-us/aparlist/.

Fix packs are cumulative. This means that the latest fix pack for any given version of DB2 contains all of the updates from previous fix packs for the same version of DB2.

The fix pack images available are:

A single server image.
The single server image contains the new and updated code required for all DB2 database server products and the IBM® Data Server Client. If more than one DB2 database server product is installed in a single location, the DB2 database server fix pack applies maintenance code updates to all the installed DB2 database server products. The Data Server Client fix pack is contained within the one DB2 database server fix pack (namely the fix pack that can service any one of the following database server products: DB2 Enterprise Server Edition, DB2 Workgroup Server Edition, DB2 Express® Edition, DB2 Personal Edition, DB2 Connect™ Enterprise Edition, DB2 Connect Application Server Edition, DB2 Connect Unlimited Edition for zSeries, and DB2 Connect Unlimited Edition for i5/OS™). You can use the DB2 database server fix pack to upgrade a Data Server Client.

A single server image can also be used to install any of the DB2 database server products, at a particular fix pack level, with a DB2 try and buy license by default.

The single server f ix pack image contains DB2 try-and-buy licenses for all DB2 server products. When you select a new DB2 server product to install or a previously installed DB2 server product to update, the try-and-buy licenses are installed. The try-and-buy licenses do not affect any valid licenses already installed in the same DB2 installation path. Regarding DB2 Connect server products, if you run the db2licm -l command to query valid licenses, the try-and-buy license for DB2 Connect server product might display as an invalid license. However, if you do not need to use the DB2 Connect functionality, you can ignore the report. To remove the try-and-buy license for DB2 Connect server, use the db2licm command.
A fix pack for each of the other DB2 database products.
Use this fix pack only if you only have non-server database products or add-on products installed. For example, IBM Data Server Runtime Client or DB2 Query Patroller.

Do not use this type of fix pack if the installed DB2 database products are only DB2 database server products or a Data Server Client. Instead, use the single server image fix pack.

For Windows platforms, if you have more than one DB2 database product (which includes at least one product that is not a Data Server Client or a DB2 database server) installed in a single DB2 copy, you must download and uncompress all of the corresponding product-specific fix packs before starting the fix pack installation process.
A universal fix pack.
The universal fix pack services installations where more than one DB2 database product has been installed.

The universal fix pack is not needed if the installed DB2 database products are only DB2 database server products or a Data Server Client. In this case, the single server image fix pack should be used.

On Linux or UNIX operating systems, if national languages have been installed, you also require a separate national language fix pack. The national language fix pack can not be installed alone. A universal or product-specific fix pack must be applied at the same time and they must both be at the same fix pack level. For example, if you are applying a universal fix pack to non-English DB2 database products on Linux or UNIX, you must apply both the universal fix pack and the national language fix pack to update the DB2 database products.

Restrictions

A DB2 Version 9.7 fix pack can only be applied to DB2 Version 9.7 general availability (GA) or DB2 Version 9.7 fix pack copies.
All DB2 instances, DAS, and applications related to the DB2 copy being updated must be stopped before installing a fix pack.
In a partitioned database environment, before installing the fix pack, you must stop the database manager on all database partition servers. You must install the fix pack on the instance-owning database partition server and all other database partition servers. All computers participating in the instance must be updated to the same fix pack level.
On Linux or UNIX operating systems:
- If you have DB2 database products on a Network File System (NFS), you must ensure the following are stopped completely before installing the fix pack: all instances, the DB2 administration server (DAS), interprocess communications (IPC), and applications on other machines using the same NFS mounted installation.
- If the system commands fuser or lsof are not available, the installFixPack command cannot detect loaded DB2 files. You must ensure no DB2 files are loaded and provide an override option to install the fix pack. On UNIX, the fuser command is required to check for loaded files. On Linux, either the fuser command or lsof command is required.
  For details on the override option, see the installFixPack command.
On client applications, after a fix pack has been applied, to perform autobind of applications, the user must have bind authority.
Logically detached data partitions are not supported in releases earlier than DB2 V9.7 Fix Pack 1. A data partition is temporarily placed in the logically detached state while it is being detached from a data partitioned table. A partition is in the logically detached state when, in SYSCAT.DATAPARTITIONS, the STATUS of the partition is set to 'L' (SYSCAT.DATAPARTITIONS.STATUS='L'). If you are reverting to a release earlier than DB2 V9.7 Fix Pack 1, ensure that data partitions are not logically detached before reverting to the release.
For tables that use multidimensional clustering (MDC) and data partitioning, the system-created partitioned block indexes are not supported in releases earlier than DB2 V9.7 Fix Pack 1. When reverting to a release earlier than DB2 V9.7 Fix Pack 1, data-partitioned MDC tables that use partitioned block indexes must be dropped before reverting to the release and recreated after reverting to the release.
Distribution statistics for XML data are not supported in releases earlier than DB2 V9.7 Fix Pack 1. After you revert to a release earlier than DB2 V9.7 Fix Pack 1, issue the RUNSTATS command on tables where XML distribution statistics were collected to refresh the statistics for the tables.
Installation of a DB2 fix pack will not service IBM Data Studio Administration Console or IBM Data Studio.
Partitioned indexes over XML data are not supported in releases earlier than DB2 Version 9.7 Fix Pack 1. If you are reverting partitioned indexes over XML data to a release earlier than DB2 Version 9.7 Fix Pack 1, before reverting to the release, you must drop the partitioned indexes and re-create them as nonpartitioned indexes.

Procedure

To install a fix pack:

Check fix pack prerequisites.
Perform the necessary tasks before installing a fix pack.
Choose a fix pack installation method and install the fix pack.
Perform the necessary tasks after installing the fix pack.
Apply the appropriate DB2 database product license.
If a previously licensed copy of a DB2 database server product does not already exist on the machine, a single server fix pack image can be used to install any of the DB2 database server products. In this case, the DB2 database product installed is treated as a try and buy license, and will stop working after a 90 day trial period unless you upgrade the try and buy license.

What to do next

Check the log file for any post-installation steps, or error messages and recommended actions.

For non-root installations on Linux or UNIX, root-based features (such as High Availability and operating system-based authentication) can be enabled using the db2rfe command. If root-based features were enabled after installing your DB2 database product, you must rerun the db2rfe command each time a fix pack is applied in order to re-enable those features. For details, see the non-root related links below.

If you have multiple DB2 copies on the same system, those copies can be at different version and fix pack levels. If you want to apply a fix pack to one or more DB2 copies, you must install the fix pack on those DB2 copies one by one.