Installing Db2 products with payload files (Linux and UNIX)

This task describes how to install Db2 database products, components, and features from Db2 payload files. This method is not recommended for Db2 product installation. It is recommended that you use the Db2 Setup wizard or the response file method. This method does not support Db2 pureScale® installation types.

To install Db2 database 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. Access the file system where the installation image is stored.
3. Locate the Db2 component that you want to install. Each Db2 database product provides a file that lists the components available for installation. The component list is in a file that is called ComponentList.htm and is located at /db2/platform directory, where platform is the platform that you are installing on.
4. Uncompress the payload file.
   Note: For Db2 database 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 database 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 does not work.

   When you extract the tar.gz files, do not extract the following files that are related to Db2 pureScale environment:

   • For AIX®:
     • PURESCALE_10.5.0.3_aix64_ppc.tar.gz
     • CF_10.5.0.3_aix64_ppc.tar.gz
   • For Linux®:
     • PURESCALE_10.5.0.3_linuxamd64_x86_64.tar.gz
     • CF_10.5.0.3_linuxamd64_x86_64.tar.gz

   Do not extract any tar.gz files with file names that start with "GSKNOINST". These files are only for installations without encryption support.

   To extract the payload file, run the appropriate command:

   • For AIX:

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

   • For Linux:

     cd DB2DIR 
     tar xzvf /image/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 as follows:
       • /opt/IBM/db2/11.1 for AIX
       • /opt/ibm/db2/11.1 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 characters that are other than English characters
       • The path name cannot be a subdirectory of an existing Db2 installation.
       • The installation paths cannot be symbolic links.
   • image represents the Db2 download installation media.
   • 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 now create a Db2 instance using the db2icrt command.
   If you do not want to create an instance, you must at least run the db2ilist command. You must now run either the db2icrt command or the db2ilist command, 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 displays:

      S,DB2,10.1.0.0,/opt/ibm/copy1,-,,0,,,1159464765,0 
      S,DB2,10.1.0.1,/opt/ibm/copy2,,,1,0,,1159466596,0

      In the sample output, 10.1.0.1 in the second line indicates that copy2 is at a higher level than copy1, which is at 10.1.0.0.
   2. Check /usr/local/bin to see whether 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 that 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 database product is installed, you must open a new login session to use the non-root Db2 instance. Alternatively, you can use the same login session if you set up the Db2 instance environment with $HOME/sqllib/db2profile (for Bourne shell and Korn shell users) or $HOME/sqllib/db2chsrc (for C shell users), where $HOME is the non-root user's home directory.