Set up multiple DB2 systems on Linux or UNIX machines

One Linux or UNIX Machine Sets multiple DB2 systems before DB2 for Linux, UNIX, and Windows Version 8, SAP customers can only install one copy of each DB2 Version on one physical machine, the installation path is hard-coded. Although DB2 Version 8 provides a replacement revision package image, these images are only used for testing and SAP does not support them in a production environment.

For DB2 9, you can install multiple copies of DB2 software on a physical machine. Database installation is independent of each other. They can be of different levels and can be installed on any valid path. Each copy can be updated independently without affecting each other. All SAPR/3 3.1I environments with DB2 9 support this feature. In addition, since SAP NetWeaver 7.1, the SAP installer makes full use of this feature to install the DB2 software in the home directory of the Instance owner.

This article explains how to set up multiple DB2 systems on a Linux or UNIX machine and run SAP applications with different installed database software.

Install Multiple DB2 copies on one system

The benefits of copying and coexistence between multiple DB29 instances: for DB2 9, you can install DB2 software multiple times on the host and assign different DB2 installations to an SAP DB2 instance. Each installed DB2 software instance runs independently. In addition, each revision package is provided in the form of a complete installation image, so that you can choose whether to install it on a previous image or install it separately as a new image.

With this improvement, customers can run different SAP applications on different levels of DB2 on the same host. For example, you can use a new revision package to deploy and test the SAP application, and then move the production system to the new installation. It also provides a way to easily return to the previous patch level. Each instance can be updated independently. You do not need to apply the revision package to previous versions and to all instances, but the old method is still supported.

For example, assume that the customer has instances I1, I2, and I3. It installs the original version of DB2 9 and updates all instances accordingly. Then install DB2 9 Fix Pack1. You can choose to install it on the first installed version or on another path. Then, point the instances I1 and I2 to the new path for update. Then, install DB2 9 Fix Pack 2 in the new path. In this case, you can also update all instances including I3 To Fix Pack 2 by pointing to the new path.

You can install Version 8 and Version 9 on the same physical machine at the same time, or Install Version 9's multiple levels of revision packages.

Differences from earlier DB2 versions

This new feature has caused many changes in DB2: you cannot use an operating system utility (such as paged, rpm, smit, or sisal) to query DB2 products. Instead, you need to use a new command db2ls to track the DB2 software installed on the machine. It provides information about the DB2 product installed, including the version and installation time.

Example:

%/Opt/ibm/db2/V9.1 _ 01/install/db2ls

Install Path Level FixPack Special Install Number Install Date

---------------------------------------------------------------

/Opt/ibm/db2/V9.1 _ 01 9.1.0.0 0 Tue Jul 11 14:28:33 2006 EDT

/Opt/ibm/db2/V9.1 _ 02 9.1.0.1 1 Thu Sep 7 16:52:14 2006 EDT

You cannot use a local operating system utility (such as ramp or smit) to uninstall DB2 software. To uninstall DB2, run the db2_deinstall command, which is located in the installation directory.

Example:

%/Opt/ibm/db2/V9.1 _ 01/install/db2_deinstall-

The preceding command can delete DB2 from the/opt/ibm/db2/V9.1 _ 01 directory.

Each DB2 system can have any number of DB2 instances. However, the Instance name must be unique throughout the system. The command db2ilist only lists the instances created in the path where the command is run. Similarly, the db2ilistdb2icrt and db2idrop commands are used to create and delete instances associated with the DB2 path where the command is run.

The DB2 9 revision package image is a complete installation image. You can use the image to run the all-new database installation, or apply the revision package to the existing installation. The installation procedure described below applies to the original version of the DB2 9 image and the revised package image. The only difference is that if you use the revised package image to run a new installation, the trial license will be installed. Then, run db2licm afilename to manually add the license.

Install

Before starting installation, ensure that the operating system meets all the prerequisites required for installing DB2 9. For the latest list of System Requirements, see the System Requirements page.

1 2 Next Page