DB2 Version 9.7 for Linux, UNIX, and Windows

Installing DB2 products with payload files (Linux and UNIX®)

Prerequisites

Before you deploy DB2 payload files:

• Review the installation prerequisites and ensure the requirements are met.
• Ensure that DB2 dependencies are met. While reviewing the installation prerequisites, make note of any DB2 products that must be installed with each other. Then be sure to deploy the tar.gz file for a product, as well as any of the tar.gz files for required products.
• Get the payload files, which are contained on the DB2 product DVD or can be downloaded from IBM® Passport Advantage®: http://www-306.ibm.com/software/howtobuy/passportadvantage/.

Restrictions

You cannot manually install a DB2 product, component, or feature using an operating system's native installation utility such as rpm, SMIT, swinstall or pkgadd.

To install DB2 products, components, and features from DB2 payload files:

1. For root installations, log on as a root user. For non-root installations, log on with the user ID that is to own the DB2 installation.
2. Insert and mount the appropriate DVD or access the file system where the installation image is stored.
3. Locate the DB2 component you want to install. Each DB2 product DVD provides a file that lists the components available for installation. The component list is in a file called ComponentList.htm and is located in the /db2/platform directory on your DVD, where platform is the platform that you are installing on.
4. Uncompress the payload file.
   Note:
   For DB2 products and components to work together, they must be installed to a single path. This is not to be confused with the ability to install DB2 products to multiple paths. But, for products and components to work together, they must be installed to the same path, and must be at the same release level. If a component has prerequisites, look in the DB2DIR/.metadata/COMPONENT/prereqs file inside each payload to see what the prerequisites are. If any required components are missing, that functionality will not work.

   To uncompress the payload file, run the appropriate command:

   • For AIX®, HP-UX or Solaris:

     cd DB2DIR
     gunzip -c /dvd/db2/platform/FILES/filename.tar.gz | tar -xvf -

   • For Linux®:

     cd DB2DIR 
     tar xzvf /dvd/db2/platform/FILES/filename.tar.gz

   where
   • DB2DIR is the full path name where you are installing:
     • For non-root installations, DB2DIR must be $HOME/sqllib. This directory must be empty
     • For root installations, the default path is:
       • /opt/IBM/db2/V9.7 for AIX, HP-UX or Solaris
       • /opt/ibm/db2/V9.7 for Linux

       If you choose not to use the default path, you can specify a different installation path.

       DB2 installation paths have the following rules:

       • Can include lowercase letters (a-z), uppercase letters (A-Z), and the underscore character ( _ )
       • Cannot exceed 128 characters
       • Cannot contain spaces
       • Cannot contain non-English characters
   • dvd represents the mount point of the DB2 DVD.
   • filename is the name of the DB2 component you are installing.
5. To ensure the embedded library search path on each DB2 executable and library file uses the installation path, run the following command:

   DB2DIR/install/db2chgpath

   where DB2DIR is the full path name where you are installing.

   Important notes:

   • After you run the db2chgpath command, program files cannot be moved.
   • If you install additional features to the same path at a subsequent time, you must run the db2stop command, and rerun the db2chgpath command.

6. For root installations, you can create a DB2 instance at this time using the db2icrt command. If there is no need to create an instance, you should at least run the db2ilist command. Either the db2icrt command or the db2ilist command must be run at this time, because a side-effect of running either command is that the installation is registered with the global registry.
7. For non-root installations, run $HOME/sqllib/db2nrcfg to configure the non-root instance.
8. Set up the db2ls utility. The db2ls utility allows you to query information about installed DB2 copies. To set up the db2ls utility:
   1. Determine which DB2 copy is the most updated copy by running the following command:

      db2greg -dump

      Output such as the following will display:

      S,DB2,9.5.0.0,/opt/ibm/copy1,-,,0,,,1159464765,0 
      S,DB2,9.5.0.1,/opt/ibm/copy2,,,1,0,,1159466596,0

      In the sample output, 9.5.0.1 in the second line indicates that copy2 is at a higher level than copy1, which is at 9.5.0.0.
   2. Check /usr/local/bin to see if a link to db2ls exists. If it exists, check which DB2 copy it points to.
   3. If either of the following conditions are true, create a link to /opt/ibm/<latest_copy>/install/db2ls in the /usr/local/bin directory (where <latest_copy> is the DB2 copy with the highest level):
      • /usr/local/bin/db2ls does not exist
      • /usr/local/bin/db2ls exists, but points to an installed DB2 copy which is not the most updated copy on the system
9. Set up the DB2 fault monitor in /etc/inittab by running the db2fmcu command, which is available in a server installation. For example:

   DB2DIR/bin/db2fmcu -u -p /etc/inittab

   where DB2DIR is the full path name where you are installing.
10. For non-root installations, after the DB2 product is installed, you need to open a new login session to use the non-root DB2 instance. Alternatively, you can use the same login session if you source the DB2 instance environment with $HOME/sqllib/db2profile (for Bourne shell and Korn shell users) or $HOME/sqllib/db2chsrc (for non C shell users), where $HOME is the non-root user's home directory.

After payload deployment, there are further manual configuration tasks which must be performed. Refer to the Related tasks for details.