78 DB2 Deployment Guide

Deployment method

Various methods are available for a fix pack deployment, as summarized here:
򐂰UNIX and Linux:
– Install the fix pack as a new DB2 database product.
– Update an existing DB2 database product.
򐂰Windows:
On a Windows platform, only the db2setup installation command is available.
The installation method differs according to the number of DB2 database
products involved and whether DB2 is configured to use Microsoft Cluster
Server (MSCS):
– Install fix pack for a single DB2 database product.
– Install fix pack for multiple DB2 database products.
– Install fix pack using response file.
– Install fix pack in an MSCS environment.
For details, visit the DB2 Information Center:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/
com.ibm.db2.luw.qb.server.doc/doc/c0025016.html

Tasks after fix pack deployment

Prior to DB2 9.5, on UNIX and Linux platforms, there are manual tasks required
after fix pack installation, for example, updating the DB2 instance and DAS, and
binding files to databases. Beginning with DB2 9.5, all these tasks are performed
automatically by the fix pack installer.
Refer to the following URL for performing post installation steps manually:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/
com.ibm.db2.luw.qb.server.doc/doc/c0025015.html
2.4.2 Mass deployment of DB2 fix pack with a script
In this section, we introduce a script, db2fp_install, for automatic mass
deployment of DB2 fix packs. This script is based on the DB2 server deployment
script db2srv_install, discussed in 2.3.3, “Creating the deployment script” on
page 64.

Environment

We continue using the environment used in 2.3, “Mass deployment of DB2 server
using a script” on page 58. The environment is almost the same, except for the
directory on the filer server on Zaire, where the shared fix pack installation image