Installation on multiple Db2 subsystems

Use product deployment

For more information, see Deploying products to other subsystems, LPARs, and sysplexes.

Perform a new product installation on each subsystem.

Perform a new product installation on each Db2 subsystem if you want to change information that the installation and configuration options do not allow you to change. For each product on each Db2 subsystem, you will need a separate set of tables. However, you can use the same Db2 table names on each subsystem. For more information, see Common utility and repository tables.

Perform a multiple subsystem (MSSID) installation.

Installation jobs for installing the product on subsequent Db2 subsystems are similar to those generated for the first subsystem. However, the subsequent jobs do not access the distribution media again. Instead, the information used to generate the first subsystem is used. The MSSID process involves creating tables and aliases, and binding plans on the additional Db2 subsystems.

If the Db2 subsystems differ in characteristics that are outside the scope of the MSSID installation process, you must use deployment or a new product installation for each subsystem, using a new installation project.

For additional information, see the following topics:

• Requirements for a MSSID installation
• Performing a MSSID installation