installFixPack - Update installed DB2 database products command

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 a partitioned database environment, every database partition) 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 partitioned database environment instance, install the fix pack on all the database partitions, while the instance update is only needed on the instance owning database partition. To keep the instance fully functional after the update, it is recommended to install all the products and features on all the database partitions, at least on the instance owning database partition.

If you are applying the fix pack to a dsf instance type (that is, a DB2 pureScale® instance associated with the DB2 copy in a DB2 pureScale environment), you must install the fix pack to a new path. You cannot apply the fix pack to the original installation path. The path where the fix pack is installed must be different than the existing installation. In addition, this new path must be the same on all hosts. When installing a fix pack to a new location, the DB2 pureScale instance does not need to be stopped before installing the fix pack.

If you are applying the fix pack to an ese instance type, you can either apply the fix pack on top of the original installation path or you can install the fix pack to a new path. If you install the fix pack on top of the original installation path, the instance must be stopped before applying the fix pack. For details, see: "Installing a fix pack to update a Version 9.8 ese or dsf instance type"

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-----------------+-'   
          +-db2lib----------------+     
          +-NOTSAMP---------------+     
          +-+-install-----------+-+     
          | +-update------------+ |     
          | '-ha_standby_ignore-' |     
          +-noWPAR----------------+     
          +-nobackup--------------+     
          +-TSAMP-----------------+     
          +-GPFS------------------+     
          '-RSCT------------------'     

>--+-+-----------------------------------------+-+--+-----+----->
   | |                                     (2) | |  '- -L-'   
   | '-+-------------+-- -I--instance-list-----' |            
   |   '- -p--FPPath-'                           |            
   '-| DB2 pureScale options |-------------------'            

>--+---------------+--+-----------------+--+-----+-------------><
   '- -l--log-file-'  '- -t--trace-file-'  +- -h-+   
                                           '- -?-'   

DB2 pureScale options

|--+-------------------------------------------------------------------------------------------+--|
   +- -show_level_info-------------------------------------------------------------------------+   
   +- -commit_level--+-------------+-- -I--pureScale-instance----------------------------------+   
   |                 '- -p--FPPath-'                                                           |   
   +- -check_commit--+-------------+-- -I--pureScale-instance----------------------------------+   
   |                 '- -p--FPPath-'                                                           |   
   '- -p--FPPath--+--------------------------------------------------------------------------+-'   
                  +- -H--hostsListFile-------------------------------------------------------+     
                  |                              .- -online--.                               |     
                  '-+-------------------------+--+-----------+--+--------------------------+-'     
                    '- -I--pureScale-instance-'  '- -offline-'  '- -quiesce_time_out--mins-'       

1. If you omit this option, you will be prompted for the required information without an error message halt.
2. Use for instances that have a type other than pureScale instance and have the same base install path.

Command parameters

-n

Specifies non-interactive mode. When specified, you must also specify -b, -p, and -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 base path where the DB2 database product has been 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 HOME/sqllib 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 HOME/sqllib 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 following force arguments 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.

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:

1. Drop the instance.
2. Uninstall DB2 including TSA/GPFS.
3. Reinstall DB2 PureScale with the TSA/GPFS level required.

-f db2lib

This parameter is ignored in a DB2 pureScale environment. 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 database partitions for the related partitioned database environment instances), and all DB2 libraries related to the installation path must be unloaded.

-f NOTSAMP

This parameter is ignored in a DB2 pureScale environment. Specifies that the SA MP should not be updated (applicable only to root installation).

-f install

Force the installFixPack command to bypass all checking on DB2 library loading and checking that the instance and DAS are stopped. To ensure that the instances or applications work properly after the installation, the DBM must be stopped for all the related instances (including all database partitions for the related partitioned database environment instances), and all DB2 libraries related to the installation path must be unloaded. If this option is specified, neither the instance nor DAS are updated. After the installation, you need to manually update the instance and DAS. Also, note that the options update, install, and ha_standby_ignore are mutually exclusive and cannot be specified in the same installation.

-f update

Force the installFixPack command to bypass all the checking on DB2 library loading, and checking that the instance and DAS are stopped. To ensure that the instances or applications work properly after the installation, the DBM must be stopped for all the related instances (including all database partitions for the related partitioned database environment instances), and all DB2 libraries related to the installation path must be unloaded. If this option is specified, both the instance and DAS are updated. Also, note that the options update, install, and ha_standby_ignore are mutually exclusive and cannot be specified in the same installation.

-f ha_standby_ignore

This parameter ignores the check for the sqllib directory by forcing the installFixPack command to bypass this check. For example, the check for sqllib directory is ignored in a clustered environment where the standby node does not have the sqllib library mounted. To ensure that the instances or applications work properly after the installation, the DBM must be stopped for all the related instances (including all database partitions for the related partitioned database environment instances), and all DB2 libraries related to the installation path must be unloaded. If this option is specified, neither the instance nor DAS are updated. After the installation, you need to manually update the instance and DAS. Also, note that the options update, install, and ha_standby_ignore are mutually exclusive and cannot be specified in the same installation.

-f noWPAR

This parameter is ignored in a DB2 pureScale environment. Applicable to AIX® 6.1 or later in a global environment. Force installFixPack not to do any checking or any actions on the AIX system workload partitions (WPARs) which share the DB2 copy being updated on the global environment. If -f noWPAR is specified, you must manually update the instances and DAS on each system WPAR that shares this DB2 copy.

-f nobackup

This parameter is ignored in a DB2 pureScale environment. Force installFixPack to not backup installation files when the components are updated. If you choose not to backup the files, the space requirement of the installation directory is reduced. However, choosing not to backup the files also means that if any errors occur, the DB2 installer will not be able to perform a rollback operation. In this case, you will need to manually clean up the files and reinstall the fix pack.

-f TSAMP

Force the installFixPack command to continue the fix pack installation process and update the current version of IBM® Tivoli System Automation for Multiplatforms (SA MP) to the latest version. Specify this parameter, if the current version of Tivoli SA MP is different from the version that was previously installed by the DB2 installer. If you cancel the fix pack installation process, Tivoli SA MP does not revert to an earlier version.

-f GPFS

Force the installFixPack command to continue the fix pack installation process and update the current version of IBM General Parallel File System ( GPFS™) to the latest version. Specify this parameter, if the current version of GPFS is different from the version that was previously installed by the DB2 installer. If you cancel the fix pack installation process, GPFS does not revert to an earlier version.

-f RSCT

Force the installFixPack command to continue the fix pack installation process and update the current version of IBM Reliable Scalable Cluster Technology (RSCT) to the latest version. Specify this parameter, if the current version of RSCT is different from the version that was previously installed by the DB2 installer. If you cancel the fix pack installation process, RSCT does not revert to an earlier version.

-p FPPath

Specify where the fix pack is to be installed. In a DB2 pureScale environment, this parameter is mandatory. Consider the following when using this parameter:

• When this parameter is specified, instances are not updated automatically. You must manually update the instances using the db2iupdt command. In addition, in a DB2 pureScale environment, if the fix pack is applied on multiple hosts, you must run the db2iupdt command on all hosts.
• If you are installing a fix pack to update a DB2 pureScale instance (dsf type instance), the path where the fix pack is installed must be different than the existing installation, and, this path must be the same on all hosts. For fix pack installations outside of a DB2 pureScale environment, the path can be different than the existing installation.

-show_level_info

Displays the following fix pack online update attributes for the current level of code.

• The architecture level.
• The code level.
• Information on whether this level of code can be installed online.
• Information on the minimum committed level required before installing online.

-commit_level

Updates the pureScale instance to a new level of code. This option is mandatory for an online fix pack update and its scope is limited to DB2 pureScale environments.

-check_commit

Verifies whether the DB2 pureScale instance is ready for a commit.

-I pureScale-instance

Specifies the pureScale instance name.

-online

Specify this option to start or continue with a fix pack online update. In a fix pack online update, the DB2 cluster can run different levels of code as long as the specified code level is same as the current effective code level (CECL) or higher. Note that during a fix pack online update, the activation of the new level of code can take place while the instance is up and running. This will be the default option when -I pureScale-instance option is used for pureScale fix pack update.

-offline

Specify this option to start or continue with an offline update. In an offline update, the DB2 cluster cannot run different levels of code. Note that during an offline update the activation of the new level of code can only take place while the whole instance is down.

-quiesce_time_out mins

Specifies how long the command waits before disconnecting applications from the given member. Once this timeout is reached, any active units of work remaining at the time are interrupted. If this parameter is not specified, default timeout value of 2 minutes is used.

-H hostsListFile

This parameter can only be specified in a DB2 pureScale environment. This parameter enables a fix pack update across multiple hosts. All hosts specified in the host list file must have the same service level. When this parameter is specified, you cannot specify the -L parameter.

Note: After running the installFixPack command with this parameter, always check the log file to ensure that there are no installation errors on any of the remote hosts.

-L

Indicates the fix pack is to be applied locally to the current host only. When this parameter is specified, you cannot specify the -H parameter.

-l log-file

Specifies the log file. For root installations, the default log file is /tmp/installFixPack.log$$, where $$ represents the process ID. For non-root installations, the default log file is /tmp/installFixPack_userID.log, where userID represents the user ID that owns the non-root installation. If the IBM Tivoli System Automation for Multiplatforms (SA MP) 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.

Usage notes