DB2 10.5 for Linux, UNIX, and Windows

Installing DB2 servers using the DB2 Setup wizard (Linux and UNIX)

This task describes how to start the DB2 Setup wizard on Linux and UNIX operating systems. The DB2 Setup wizard is used to define your installation preferences and to install your DB2® database product on your system. If you are installing the DB2 pureScale® Feature, see topic Installing a DB2 pureScale environment.

Before you begin

Before you start the DB2 Setup wizard:
  • If you are planning on setting up a partitioned database environment, see how to do this by consulting the task in the related links at the end of this topic.
  • Ensure that your system meets installation, memory, and disk requirements.
  • Ensure you have a supported browser installed.
  • You can install a DB2 database server using either root or non-root authority. For more information about non-root installation, see the related links.
  • The DB2 database product image must be available. You can obtain a DB2 installation image either by purchasing a physical DB2 database product DVD, or by downloading an installation image from Passport Advantage®.
  • If you are installing a non-English version of a DB2 database product, you must have the appropriate National Language Packages.
  • The DB2 Setup wizard is a graphical installer. To install a DB2 product using the DB2 Setup wizard, you require an X Window System (X11) to display the graphical user interface (GUI). To display the GUI on your local workstation, the X Window System software must be installed and running, and you must set the DISPLAY variable to the IP address of the workstation you use to install the DB2 product (export DISPLAY=<ip-address>:0.0). For example, export DISPLAY=192.168.1.2:0.0. For details, see this developerWorks® article: http://www.ibm.com/developerworks/community/blogs/paixperiences/entry/remotex11aix?lang=en.
  • If you are using security software in your environment, you must manually create required DB2 users before you start the DB2 Setup wizard.

Restrictions

Procedure

To start the DB2 Setup wizard:

  1. If you have a physical DB2 database product DVD, change to the directory where the DB2 database product DVD is mounted by entering the following command:
       cd /dvdrom
    where /dvdrom represents the mount point of the DB2 database product DVD.
  2. If you downloaded the DB2 database product image, you must extract and untar the product file.
    1. Extract the product file:
      gzip -d product.tar.gz
      where product is the name of the product that you downloaded.
    2. Untar the product file:
      On Linux operating systems
      tar -xvf product.tar
      On AIX®, HP-UX, and Solaris operating systems
      gnutar -xvf product.tar
      where product is the name of the product that you downloaded.
    3. Change directory:
      cd ./product
      where product is the name of the product that you downloaded.
    Note: If you downloaded a National Language Package, untar it into the same directory. This will create the subdirectories (for example ./nlpack) in the same directory, and allows the installer to automatically find the installation images without prompting.
  3. Enter the ./db2setup command from the directory where the database product image resides to start the DB2 Setup wizard.
  4. The IBM DB2 Setup Launchpad opens. From this window, you can view installation prerequisites and the release notes, or you can proceed directly to the installation. You can also review the installation prerequisites and release notes for late-breaking information.
  5. Click Install a Product and the Install a Product window will display the products available for installation.

    Launch the installation by clicking Install New. Proceed through the installation following the DB2 Setup wizard's prompts.

  6. Sample panels when using the DB2 setup wizard will lead you to the installation process. See the related links.

    After you have initiated the installation, proceed through the DB2 Setup wizard installation panels and make your selections. Installation help is available to guide you through the remaining steps. To invoke the installation help, click Help or press F1. You can click Cancel at any time to end the installation.

Results

For non-root installations, DB2 database products are always installed in the $HOME/sqllib directory, where $HOME represents the non-root user's home directory.

For root installations, DB2 database products are installed, by default, in one of the following directories:
AIX, HP-UX, and Solaris
/opt/IBM/db2/V10.5
Linux
/opt/ibm/db2/V10.5

If you are installing on a system where this directory is already being used, the DB2 database product installation path will have _xx added to it, where _xx are digits, starting at 01 and increasing depending on how many DB2 copies you have installed.

You can also specify your own DB2 database product 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
  • The path name cannot be a subdirectory of an existing DB2 installation.
  • The installation paths cannot be symbolic links.
The installation log files are:
  • The DB2 setup log file. This file captures all DB2 installation information including errors.
    • For root installations, the DB2 setup log file name is db2setup.log.
    • For non-root installations, the DB2 setup log file name is db2setup_username.log, where username is the non-root user ID under which the installation was performed.
  • The DB2 error log file. This file captures any error output that is returned by Java™ (for example, exceptions and trap information).
    • For root installations, the DB2 error log file name is db2setup.err.
    • For non-root installations, the DB2 error log file name is db2setup_username.err, where username is the non-root user ID under which the installation was performed.

By default, these log files are located in the /tmp directory. You can specify the location of the log files.

There is no longer a db2setup.his file. Instead, the DB2 installer saves a copy of the DB2 setup log file in the DB2_DIR/install/logs/ directory, and renames it db2install.history. If the name already exists, then the DB2 installer renames it db2install.history.xxxx, where xxxx is 0000-9999, depending on the number of installations you have on that machine.

Each installation copy has a separate list of history files. If an installation copy is removed, the history files under this install path will be removed as well. This copying action is done near the end of the installation and if the program is stopped or aborted before completion, then the history file will not be created.

What to do next

IBM® Data Studio can be installed by running the the DB2 Setup wizard

National Language Packs can also be installed by running the ./db2setup command from the directory where the National Language Pack resides, after a DB2 database product has been installed.

On Linux x86, if you want your DB2 database product to have access to DB2 documentation either on your local computer or on another computer on your network, then you must install the DB2 Information Center. The DB2 Information Center contains documentation for the DB2 database system and DB2 related products.

DB2 Express® Server Edition and DB2 Workgroup Server Edition memory limits
If you are installing DB2 Express Server Edition, the maximum allowed memory for the instance is 4 GB.

If you are installing DB2 Workgroup Server Edition, the maximum allowed memory for the instance is 64 GB.

The amount of memory allocated to the instance is determined by the INSTANCE_MEMORY database manager configuration parameter.
Important notes when upgrading from V9.7, V9.8, or V10.1:
  • If the memory configuration for your Important notes when upgrading from V9.7, V9.8, or V10.1 DB2 database product exceeds the allowed limit, the DB2 database product might not start after upgrading to the current version.
  • The self tuning memory manager will not increase your overall instance memory limit beyond the license limits.