installFixPack - Update installed DB2 database products command

Update the installed DB2? database products in a given location, on all UNIX? and Linux? platforms, to the level same as the image. If there are multi-copy DB2 database products installed, the installFixPack command updates one copy at a time according to the path specified.

This command can be found at the top directory in the image.

Fix pack installation will proceed when the database manager (DBM) of every instance (and in DPF, every node) related to the installation path is stopped, and all DB2 libraries are unloaded. If all the preconditions are satisfied, installFixPack will update those instances and DAS related to the installation path. An additional manual update is not required. For all UNIX and Linux operating systems, the djxlink bind command will be launched automatically when the database is reconnected or when applications are restarted.

In some cases, you may specify different force options to continue the fix pack installation, for example, when not all DBMs are stopped, or DB2 libraries remain loaded. installFixPack will continue, but you may need to manually update the instances and DAS, as well as restart the applications.
For a DPF instance, install the fix pack on all the nodes, while the instance update is only needed on the instance owning node. To keep the instance fully functional after the update, it is recommended to install all the products and features on all the nodes, at least on the instance owning node.
Authorization
Root installations require root user authority. For non-root installations, you must log on with the user ID that owns the non-root installation.
Required Connection
None

Command syntax
-installFixPack--+--------------------------------------------------+--
(1)
+- -b--base-install-path---------------------------+
+- -c--image-location------------------------------+
+- -b--base-install-path-- -c--image-location------+
'- -n-- -b--base-install-path-- -c--image-location-'
--+----------------------+--+---------------+------------------
'- -f--+-level-------+-' '- -l--log-file-'
+-db2lib------+
+-NOTSAMP-----+
'-+-install-+-'
'-update--'
--+-----------------+--+-----+--------------------------------
'- -t--trace-file-' +- -h-+
'- --'
Notes
If you omit this option, you will be prompted for the required information without an error message halt.
Command parameters

-n
Specifies non-interactive mode. When specified, you must also specify -b, andor -c. This mode can be used for applications to provide all the required information at the command line in an unattended mode.

-b base-install-path
Specifies the path where the DB2 database product will be installed. Mandatory when -n is specified. The length of the path is limited to 128 characters and is a full path name.
The -b option is not required for a non-root installation of DB2, but it is still mandatory for a root installation. If -b is used in a non-root install, the value of base-install-path must be the user's HOMEsqllib directory, or else the path is considered invalid. If -b is not provided in a non-root install, the DB2 installer will use the user's HOMEsqllib as the install path and continue. But, if -b is used and the provided install path has a DB2 copy installed by a root user, the path is considered invalid since the DB2 copy can only be updated by the user who installed it.

-c NLPACK_location
Specifies the location of the related DB2 National Language Pack (NLPACK). This parameter is mandatory when -n is specified. The DB2 NLPACK location needs to be provided explicitly if all of the following conditions are met
The -n option is specified.
The installation requires National Language (non-English) support.
The DB2 NLPACK is neither on the DB2 DVD nor in the same subdirectory as the DB2 database product being installed.

-f
Force option. -f with no argument is not supported. The force arguments below can be combined. For example, -f level -f db2lib.

-f level
Force a down level or same level fix pack install. If the fix pack image is at a higher level than the installed DB2 database product, this option is ignored.

-f db2lib
Force installFixPack to bypass the checking on DB2 library loading. To ensure that the instances or applications work properly after the installation, the DBM must be stopped for all the related instances (including all nodes for the related DPF instances), and all DB2 libraries related to the installation path must be unloaded.

-f NOTSAMP
Specifies that the SA MP Base Component should not be updated (applicable only to root installation).

-f install
Force installFixPack to bypass all the checking on DB2 library loading, instance and DAS properly stopped or not. To ensure that the instances or applications work properly after the installation, the DBM must be stopped for all the related instances (including all nodes for the related DPF instances), and all DB2 libraries related to the installation path must be unloaded. If this option is specified, instanceDAS will not be updated. User needs to do the instanceDAS update manually after the installation. Also, note that the options update and install are mutually exclusive and cannot be specified in the same installation.

-f update
Force installFixPack to bypass all the checking on DB2 library loading, instance and DAS properly stopped or not. To ensure that the instances or applications work properly after the installation, the DBM must be stopped for all the related instances (including all nodes for the related DPF instances), and all DB2 libraries related to the installation path must be unloaded. If this option is specified, instanceDAS will be updated. Also, note that the options update and install are mutually exclusive and cannot be specified in the same installation.

-l log-file
Specifies the log file. For root installations, the default log file is tmpinstallFixPack.log$$, where $$ represents the process ID. For non-root installations, the default log file is tmpinstallFixPack_userID.log, where userID represents the user ID that owns the non-root installation. If the IBM? Tivoli? System Automation for Multiplatforms Base Component (SA MP Base Component) is being installed or updated with the installFixPack command, the corresponding log file will be located in the same directory as DB2 log files.

-t trace-file
Turns on the debug mode. The debug information is written to the file name specified.

-h -
Displays help information.
Examples
To perform. an interactive update from GA to Fix Pack 1 when DB2 Enterprise Server Edition German is installed on optibmdb2COPY1, from the Fix Pack 1 image, issue
.installFixPack -b optibmdb2COPY1
To perform. a silent update from GA to Fix Pack 1 when DB2 Enterprise Server Edition German is installed on optibmdb2COPY1, from the Fix Pack 1 image, issue
.installFixPack -b optibmdb2COPY1 -c full_path_to_NLPACK_image -n
If for any reason the installed DB2 database product files get corrupted, instead of uninstalling and installing again to refresh the installation, issue
.installFixPack -f level -b full_path_where_DB2_product_installed
Related tasks