              DB2 Getting Started Guide for Linux and UNIX

Contents

System prerequisites
   Installation requirements for DB2 servers and IBM data server clients 
   (AIX)
   Installation requirements for DB2 servers and IBM data server clients 
   (HP-UX)
   Installation requirements for DB2 servers and IBM data server clients 
   (Linux)
   Installation requirements for DB2 servers and IBM data server clients 
   (Solaris Operating System)
Disk and memory requirements
DB2 installation methods
Non-root installation
   Non-root installation overview (Linux and UNIX)
   Differences between root installations and non-root installations
   Limitations of non-root installations
Installing DB2 servers using the DB2 Setup wizard (Linux and UNIX)
Response file installation
   Creating a response file using the sample response file (Linux and 
   UNIX)
   Installing a DB2 product using a response file (Linux and UNIX)
Installing a DB2 product using the db2_install or doce_install command 
(Linux and UNIX)
Applying fix packs
Installation of more tools can be launched from the DB2 installation

System prerequisites

Installation requirements for DB2 servers and IBM data server clients 
(AIX)



To install a DB2(R) product, the following operating system, hardware,
and communications prerequisites must be met:

Table 1. AIX installation prerequisites
+----------------------------------+----------------------------------+
| Operating System                 | Hardware                         |
+----------------------------------+----------------------------------+
| AIX(R) Version 5.3               | One of:                          |
|  * 64-bit AIX kernel is required |  * eServer(TM) pSeries(R)        |
|  * TL5 SP3 (minimum)             |  * IBM(R) System p(TM)           |
|  * Minimum C++ runtime level is  |  * IBM System p5(TM)             |
| xlC.rte 8.0.0.8 and              |                                  |
| xlC.aix50.rte 8.0.0.8            |                                  |
+----------------------------------+----------------------------------+



Software considerations
*  (Clients only) If you plan to use Kerberos Authentication, you
   require IBM Network Authentication Service client v1.4 or later. The
   NAS client can be downloaded from
   https://www6.software.ibm.com/dl/dm/dm-nas-p.
*  Use the bosboot command to switch to the 64-bit kernel. 

   To switch to a 64-bit kernel, you require root authority and should
   enter the following commands:

    

      ln -sf /usr/lib/boot/unix_64 /unix
      ln -sf /usr/lib/boot/unix_64 /usr/lib/boot/unix
      bosboot -a
      shutdown -Fr

*  DB2 Version 9.5 requires the "IBM C++ Runtime Environment Components
   for AIX" which includes xlC.rte 8.0.0.8. This is available from the
   IBM AIX support web site.
*  One of the following browsers is required to view online help and to
   run First Steps (db2fs): 
   *  Mozilla 1.4 and up
   *  Firefox 1.0 and up
   *  Netscape 7.0 and up



DB2 product installation on NFS (Network File System)

The installation of DB2 products on NFS (Network File System) is not
recommended. Running DB2 products on NFS (for example, NFS mounting
/opt/IBM/db2/V9.5 and then running off code that was physically
installed on a remote system) requires several manual setup steps. There
are also a number of potential issues with setting up NFS for a DB2
server. These include possible problems that involve: 
*  Performance (impacted by network performance)
*  Availability (you are allowing a single point of failure)
*  Licensing (there is no checking done across machines)
*  Diagnosing NFS errors can be difficult

As mentioned, the setup for NFS will require several manual actions
including: 
*  Ensuring that the mount point preserve the install path
*  Permission must be controlled (for example, write permission should
   not be given to the mounting machine)
*  DB2 registries have to be set up manually and maintained across all
   mounting machines
*  The db2ls command, which lists installed DB2 products and features,
   must be set up and maintained properly if you need to detect DB2
   products and features
*  More care is required when updating your DB2 product environment
*  More steps are required when cleaning up on the exporting machine and
   the mounting machine

For detailed instructions, see the "Setting up DB2 for UNIX and Linux on
NFS mounted file systems" white paper in
http://www.ibm.com/developerworks/db2/library/long/dm-0609lee.

Installation requirements for DB2 servers and IBM data server clients 
(HP-UX)



To install a DB2 product, the following operating system, hardware, and
communications prerequisites must be met:

Table 2. HP-UX installation prerequisites
+-----------------------------------------+---------------------------+
| Operating System                        | Hardware                  |
+-----------------------------------------+---------------------------+
|                                         | Itanium(R) based HP       |
| DB2 products are supported on:          | Integrity Series Systems  |
|  * HP-UX 11iv2 (11.23.0505) with:       |                           |
|   * May 2005 Base Quality (QPKBASE)     |                           |
| bundle                                  |                           |
|   * May 2005 Applications Quality       |                           |
| (QPAPPS) bundle                         |                           |
|  * HP-UX 11iv3 (11.31)                  |                           |
+-----------------------------------------+---------------------------+



Kernel configuration considerations

A system restart is required if you update the kernel configuration
parameters. The kernel configuration parameters are set in /etc/system.
Depending on the values of your kernel configuration parameters, you
might need to modify some of them before you install the Version 9
client or DB2 server products. If the kernel parameter being modified is
not listed as dynamic, a system reboot is required to make the changes
to /etc/system take effect.



Software considerations
*  If you are installing the IBM Data Server Client, you must have a C
   compiler to build SQL Stored Procedures.
*  One of the following browsers is required to view online help and to
   run First Steps (db2fs): 
   *  Mozilla 1.4 and up
   *  Firefox 1.0 and up
   *  Netscape 7.0 and up



DB2 product installation on NFS (Network File System)

The installation of DB2 products on NFS (Network File System) is not
recommended. Running DB2 products on NFS (for example, NFS mounting
/opt/IBM/db2/V9.5 and then running off code that was physically
installed on a remote system) requires several manual setup steps. There
are also a number of potential issues with setting up NFS for DB2. These
include possible problems that involve:

*  Performance (impacted by network performance)
*  Availability (you are allowing a single point of failure)
*  Licensing (there is no checking done across machines)
*  Diagnosing NFS errors can be difficult

As mentioned, the setup for NFS will require several manual actions
including:

*  Ensuring that the mount point preserve the install path
*  Permission must be controlled (for example, write permission should
   not be given to the mounting machine)
*  DB2 registries have to be set up manually and maintained across all
   mounting machines
*  The db2ls command, which lists installed DB2 products and features,
   must be set up and maintained properly if you need to detect DB2
   products and features
*  More care is required when updating your DB2 product environment
*  More steps are required when cleaning up on the exporting machine and
   the mounting machine

For detailed instructions, see the "Setting up DB2 for UNIX and Linux on
NFS mounted file systems" white paper in
http://www.ibm.com/developerworks/db2/library/long/dm-0609lee.

Installation requirements for DB2 servers and IBM data server clients 
(Linux)



For the latest information on supported Linux(R) distributions, point
your browser to http://www.ibm.com/software/data/db2/linux/validate/.

To install DB2 products, the distribution requirements, hardware, and
communications prerequisites must be met.

DB2 products are supported on the following hardware: 
*  x86 (Intel(R) Pentium(R), Intel Xeon(R), and AMD) 32-bit Intel and
   AMD processors
*  x64 (64-bit AMD64 and Intel EM64T processors)
*  POWER(TM) (IBM eServer OpenPower(TM), System i(TM) or pSeries systems
   that support Linux)
*  eServer System z(TM) or System z9(TM)

The supported operating systems for Linux include: 
*  Red Hat Enterprise Linux (RHEL) 4 Update 4
*  Red Hat Enterprise Linux (RHEL) 5
*  SUSE Linux Enterprise Server (SLES) 9 Service Pack 3
*  SUSE Linux Enterprise Server (SLES) 10 Service Pack 1

Note: POWER requires a minimum of SLES 10 Service Pack 1 or RHEL 5



Multithreaded architecture limitations

If you are installing a DB2 Version 9.5 32-bit database product on a
Linux operating system, consider upgrading to a 64-bit operating system
and installing the DB2 Version 9.5 64-bit database product instead. The
multithreaded architecture generally simplifies memory configuration.
However, this could affect the memory configuration of 32-bit DB2
servers. For example: 
*  Private memory for agent threads is allocated within a single
   process. The aggregate of all private memory allocations for database
   agents might not fit in a single process memory space.
*  Support for multiple databases is limited because all database shared
   memory segments for all databases are allocated in a single process.
   You might need to reduce the memory usage for some databases in order
   to activate all databases successfully at the same time. However, the
   database manager performance might be impacted. Another alternative
   is to create multiple instances and catalog the databases across the
   instances. However, sufficient system resources is required to
   support this configuration. 



Distribution Requirements

You should update your kernel configuration parameters in preparation
for your Linux distribution. The default values for particular kernel
parameters might not be sufficient when running a DB2 database system.

You might also have other products or applications that require Linux
system resources. You should modify the kernel configuration parameters
based on the needs of your Linux system working environment.

The kernel configuration parameters are set in /etc/sysctl.conf.

Refer to your operating system manual for information on setting and
activating these parameters using the sysctl command.



Package requirements (server only)

The following tables list the package requirements for SLES and RHEL
distributions for DB2 Version 9.5: 
*  libaio.so.1 is required for asynchronous i/o
*  libstdc++so.5 is required for the DB2 server

Package requirements for SLES
+------------------+--------------------------------------------------+
| Package name     | Description                                      |
+------------------+--------------------------------------------------+
| libaio           | contains the asynchronous library required for   |
|                  | DB2 servers.                                     |
+------------------+--------------------------------------------------+
| compat-libstdc++ | contains libstdc++so.5                           |
+------------------+--------------------------------------------------+

Package requirements for RHEL
+-----------------------+-------------+-------------------------------+
| Directory             | Package     | Description                   |
|                       | name        |                               |
+-----------------------+-------------+-------------------------------+
| /System               | libaio      | contains the asynchronous     |
| Environment/Libraries |             | library required for DB2      |
|                       |             | servers.                      |
+-----------------------+-------------+-------------------------------+
| /System               | compat-libs | contains libstdc++so.5        |
| Environment/Libraries | tdc++       |                               |
+-----------------------+-------------+-------------------------------+

The following tables list the package requirements for SUSE Linux and
Red Hat distributions for DB2 Version 9.5 partitioned servers.

*  The pdksh Korn Shell package is required for all DB2 systems.
*  A remote shell utility is required for partitioned database systems.
   DB2 supports the following remote shell utilities: 
   *  rsh
   *  ssh

   By default, DB2 uses rsh when executing commands on remote DB2 nodes,
   for example, when starting a remote DB2 database partition. To use
   the DB2 default, the rsh-server package must be installed (see table
   below). More information on rsh and ssh is available in the DB2
   Information Center. 

   If you choose to use the rsh remote shell utility, inetd (or xinetd)
   must be installed and running as well. If you choose to use the ssh
   remote shell utility, you need to set the DB2RSHCMD communication
   variable immediately after the DB2 installation is complete. If this
   registry variable is not set, rsh is used.

*  The nfs-utils Network File System support package is required for
   partitioned database systems.

All required packages should be installed and configured before
continuing with the DB2 setup. For general Linux information, see your
Linux distribution documentation.

Package requirements for SUSE Linux
+------------------+--------------------------------------------------+
| Package name     | Description                                      |
+------------------+--------------------------------------------------+
| pdksh            | Korn Shell. This package is required for         |
|                  | partitioned database environments.               |
+------------------+--------------------------------------------------+
| openssh          | This package contains a set of server programs   |
|                  | which allow users to run commands on (and from)  |
|                  | remote computers via a secure shell. This        |
|                  | package is not required if you use the default   |
|                  | configuration of DB2 with rsh.                   |
+------------------+--------------------------------------------------+
| rsh-server       | This package contains a set of server programs   |
|                  | which allow users to run commands on remote      |
|                  | computers, login in to other computers, and copy |
|                  | files between computers (rsh, rexec, rlogin, and |
|                  | rcp). This package is not required if you        |
|                  | configure DB2 to use ssh.                        |
+------------------+--------------------------------------------------+
| nfs-utils        | Network File System support package. It allows   |
|                  | access to local files from remote computers.     |
+------------------+--------------------------------------------------+

Package requirements for Red Hat
+-----------------------+-------------+-------------------------------+
| Directory             | Package     | Description                   |
|                       | name        |                               |
+-----------------------+-------------+-------------------------------+
| /System               | pdksh       | Korn Shell. This package is   |
| Environment/Shell     |             | required for partitioned      |
|                       |             | database environments.        |
+-----------------------+-------------+-------------------------------+
| /Applications/Interne | openssh     | This package contains a set   |
| t                     |             | of client programs which      |
|                       |             | allow users to run commands   |
|                       |             | on a remote computer via a    |
|                       |             | secure shell. This package is |
|                       |             | not required if you use the   |
|                       |             | default configuration of DB2  |
|                       |             | with rsh.                     |
+-----------------------+-------------+-------------------------------+
| /System               | openssh-ser | This package contains a set   |
| Environment/Daemons   | ver         | of server programs which      |
|                       |             | allow users to run commands   |
|                       |             | from a remote computer via a  |
|                       |             | secure shell. This package is |
|                       |             | not required if you use the   |
|                       |             | default configuration of DB2  |
|                       |             | with rsh.                     |
+-----------------------+-------------+-------------------------------+
| /System               | rsh-server  | This package contains a set   |
| Environment/Daemons   |             | of programs which allow users |
|                       |             | to run commands on a remote   |
|                       |             | computer. Required for        |
|                       |             | partitioned database          |
|                       |             | environments. This package is |
|                       |             | not required if you configure |
|                       |             | DB2 to use ssh.               |
+-----------------------+-------------+-------------------------------+
| /System               | nfs-utils   | Network File System support   |
| Environment/Daemons   |             | package. It allows access to  |
|                       |             | local files from remote       |
|                       |             | computers.                    |
+-----------------------+-------------+-------------------------------+



Software considerations
*  (Clients only) If you plan to use Kerberos Authentication, you
   require IBM Network Authentication Service client v1.4 or later. The
   NAS client can be downloaded from
   https://www6.software.ibm.com/dl/dm/dm-nas-p.
*  One of the following browsers is required to view online help and to
   run First Steps (db2fs): 
   *  Mozilla 1.4 and up
   *  Firefox 1.0 and up
   *  Netscape 7.0 and up

*  An X Window System software capable of rendering a graphical user
   interface is required if: 
   *  you want to use the DB2 Setup wizard to install a DB2 product on
      Linux or UNIX(R) operating systems, or
   *  you want to use any DB2 graphical tools on Linux for x86 and Linux
      on AMD 64/EM64T.



DB2 product installation on NFS (Network File System)

The installation of DB2 products on NFS (Network File System) is not
recommended. Running DB2 products on NFS (for example, NFS mounting
/opt/IBM/db2/V9.5 and then running off code that was physically
installed on a remote system) requires several manual setup steps. There
are also a number of potential issues with setting up NFS for DB2. These
include possible problems that involve:

*  Performance (impacted by network performance)
*  Availability (you are allowing a single point of failure)
*  Licensing (there is no checking done across machines)
*  Diagnosing NFS errors can be difficult

As mentioned, the setup for NFS will require several manual actions
including:

*  Ensuring that the mount point preserve the install path
*  Permission must be controlled (for example, write permission should
   not be given to the mounting machine)
*  DB2 registries have to be set up manually and maintained across all
   mounting machines
*  The db2ls command, which lists installed DB2 products and features,
   must be set up and maintained properly if you need to detect DB2
   products and features
*  More care is required when updating your DB2 product environment
*  More steps are required when cleaning up on the exporting machine and
   the mounting machine

For detailed instructions, see the "Setting up DB2 for UNIX and Linux on
NFS mounted file systems" white paper in
http://www.ibm.com/developerworks/db2/library/long/dm-0609lee.



Security-enhanced Linux considerations

On RHEL 4 and RHEL 5 systems, if Security-enhanced Linux (SELinux) is
enabled and in enforcing mode, the installer might fail due to SELinux
restrictions.

To determine if SELinux is installed and in enforcing mode, you can do
one of the following: 
*  check the /etc/sysconfig/selinux file
*  run the sestatus command
*  check the /var/log/messages file for SELinux notices (Notice format
   might differ between RHEL 4 and RHEL 5.)

To disable SELinux, you can do one of the following: 
*  set it in permissive mode and run the setenforce 0 command as a
   superuser
*  modify /etc/sysconfig/selinux and reboot the machine.

If your DB2 product installs successfully on a RHEL 4 or RHEL 5 system,
DB2 processes will run in the unconfined domain. To assign DB2 processes
to their own domains, modify the policy. A sample SELinux policy is
provided in the sqllib/samples directory.

Installation requirements for DB2 servers and IBM data server clients 
(Solaris Operating System)



To install a DB2 product, the following operating system, hardware, and
communications prerequisites must be met:

Table 3. Solaris Operating System installation prerequisites
+-----------------------------------------+---------------------------+
| Operating System                        | Hardware                  |
+-----------------------------------------+---------------------------+
| Solaris 9                               | UltraSPARC                |
|  * 64- bit kernel                       |                           |
|  * Patches 111711-12 and 111712-12      |                           |
|  * If raw devices are used, patch       |                           |
| 122300-11 on Solaris 9 or 125100-07 on  |                           |
| Solaris 10                              |                           |
|  * 64-bit Fujitsu PRIMEPOWER and        |                           |
| Solaris 9 Kernel Update Patch 112233-01 |                           |
| or later to get the fix for patch       |                           |
| 912041-01                               |                           |
| Solaris 10                              |                           |
|  * 64- bit kernel                       |                           |
|  * If raw devices are used, patch       |                           |
| 125101-07                               |                           |
+-----------------------------------------+---------------------------+



Kernel configuration considerations

The kernel configuration parameters are set in /etc/system. If the
kernel parameter being modified is not listed as dynamic, a system
reboot is required to make the changes to /etc/system take effect. These
parameters must be set before you install an IBM data server client.



Software considerations
*  (Clients only) If you plan to use Kerberos Authentication, you
   require Solaris Operating System 9 or higher with IBM Network
   Authentication Service (NAS) client v1.4 or higher. The NAS client
   can be downloaded from Web site:
   https://www6.software.ibm.com/dl/dm/dm-nas-p.
*  If you are installing the IBM Data Server Client, you must have a C
   compiler to build SQL Stored Procedures.
*  One of the following browsers is required to view online help and to
   run First Steps (db2fs): 
   *  Mozilla 1.4 and up
   *  Firefox 1.0 and up
   *  Netscape 7.0 and up

Security Patches can be obtained from the http://sunsolve.sun.com Web
site. From the SunSolve Online Web site, click on the "Patches" menu
item in the left panel.

The Java2 Standard Edition (J2SE) Solaris Operating System Patch
Clusters and the SUNWlibC software are also required and can be obtained
from the http://sunsolve.sun.com Web site.

For DB2 on 64-bit Fujitsu PRIMEPOWER systems, you require the following:

*  Solaris 9 Kernel Update Patch 112233-01 or later to get the fix for
   patch 912041-01.

 The Fujitsu PRIMEPOWER patches for the Solaris Operating System can be
downloaded from FTSI at: http://download.ftsi.fujitsu.com/.



DB2 product installation on NFS (Network File System)

The installation of DB2 products on NFS (Network File System) is not
recommended. Running DB2 products on NFS (for example, NFS mounting
/opt/IBM/db2/V9.5 and then running off code that was physically
installed on a remote system) requires several manual setup steps. There
are also a number of potential issues with setting up NFS for DB2. These
include possible problems that involve:

*  Performance (impacted by network performance)
*  Availability (you are allowing a single point of failure)
*  Licensing (there is no checking done across machines)
*  Diagnosing NFS errors can be difficult

As mentioned, the setup for NFS will require several manual actions
including:

*  Ensuring that the mount point preserve the install path
*  Permission must be controlled (for example, write permission should
   not be given to the mounting machine)
*  DB2 registries have to be set up manually and maintained across all
   mounting machines
*  The db2ls command, which lists installed DB2 products and features,
   must be set up and maintained properly if you need to detect DB2
   products and features
*  More care is required when updating your DB2 product environment
*  More steps are required when cleaning up on the exporting machine and
   the mounting machine

For detailed instructions, see the "Setting up DB2 for UNIX and Linux on
NFS mounted file systems" white paper in
http://www.ibm.com/developerworks/db2/library/long/dm-0609lee.

Disk and memory requirements



Disk requirements

The disk space required for your product depends on the type of
installation you choose and the type of file system you have. The DB2
Setup wizard provides dynamic size estimates based on the components
selected during a typical, compact, or custom installation.

Remember to include disk space for required databases, software and
communication products.

On Linux and UNIX operating systems, 2 GB of free space in the /tmp
directory is recommended.



Memory requirements

At a minimum, a DB2 database system requires 256 MB of RAM. For a system
running just a DB2 product and the DB2 GUI tools, a minimum of 512 MB of
RAM is required. However, 1 GB of RAM is recommended for improved
performance. These requirements do not include any additional memory
requirements for other software that is running on your system.

When determining memory requirements, be aware of the following: 
*  DB2 products that run on HP-UX Version 11i for Itanium-based systems
   require 512 MB of RAM at a minimum.
*  For IBM data server client support, these memory requirements are for
   a base of five concurrent client connections. You will need an
   additional 16 MB of RAM per five client connections.
*  Memory requirements are affected by the size and complexity of your
   database system, as well as by the extent of database activity and
   the number of clients accessing your system. 

   For DB2 server products, the self-tuning memory feature simplifies
   the task of memory configuration by automatically setting values for
   several memory configuration parameters. When enabled, the memory
   tuner dynamically distributes available memory resources among
   several memory consumers including sort, the package cache, the lock
   list and buffer pools.

*  On Linux operating system, SWAP space at least twice as large as RAM
   is recommended.

DB2 installation methods

 This topic provides information about DB2 installation methods. The
following table shows the installation methods that are available by
operating system.

Table 4. Installation method by operating system.
+-----------------------+----------------------+----------------------+
| Installation method   | Windows(R)           | LinuxLinux or UNIX   |
+-----------------------+----------------------+----------------------+
| DB2 Setup wizard      | Yes                  | Yes                  |
+-----------------------+----------------------+----------------------+
| Response file         | Yes                  | Yes                  |
| installation          |                      |                      |
+-----------------------+----------------------+----------------------+
| db2_install command   | No                   | Yes                  |
+-----------------------+----------------------+----------------------+
| Payload file          | No                   | Yes                  |
| deployment            |                      |                      |
+-----------------------+----------------------+----------------------+

The following list describes DB2 installation methods.

DB2 Setup wizard
         The DB2 Setup wizard is a GUI installer available on Linux,
         UNIX, and Windows operating systemsLinux. The DB2 Setup wizard
         provides an easy-to-use interface for installing DB2 products
         and for performing initial setup and configuration tasks. 

         The DB2 Setup wizard can also create DB2 instances and response
         files that can be used to duplicate this installation on other
         machines.

         Note: For non-root installations on Linux and UNIXLinux
               platforms, only one DB2 instance can exist. The DB2 Setup
               wizard automatically creates the non-root instance.

          

         On Linux and UNIXLinux platforms, an X server is required to
         display the DB2 Setup wizard.


Response file installation
         A response file is a text file that contains setup and
         configuration values. The file is read by the DB2 setup program
         and the installation is performed according to the values that
         have been specified. 

         A response file installation is also referred to as a silent
         installation.

          

         One benefit of this installation method is that you can create
         a response file without performing an installation. This
         feature can be useful to capture the options required to
         install the DB2 product. The response file can be used at a
         later time to install the DB2 product according to the exact
         options you specified.

          

         Another advantage to response files is that they provide access
         to parameters that cannot be set using the DB2 Setup wizard.

          

         On Linux and UNIX operating systems, if you embed the DB2
         installation image in your own application, it is possible for
         your application to receive installation progress information
         and prompts from the installer in computer-readable form. This
         behavior is controlled by the INTERACTIVE response file
         keyword.

          

         There are a number of ways to create a response file: 

         Using the response file generator (Windows platforms)
                  On Windows, you can use the response file generator to
                  create a response file that replicates an existing
                  installation. For example, you might install an IBM
                  data server client, fully configure the client, then
                  generate a response file to replicate the installation
                  and configuration of the client to other computers.

         Using the DB2 Setup wizard
                  The DB2 Setup wizard can create a response file based
                  on the selections you make as you proceed through the
                  DB2 Setup wizard. Your selections are recorded in a
                  response file that you can save to a location on your
                  system. If you select a partitioned database
                  installation, two response files will be generated,
                  one for the instance-owning computer and one for
                  participating computers. 

                  You can export a client or server profile with the
                  db2cfexp command to save your client or server
                  configuration, and then easily import the profile
                  using the db2cfimp command. A client or server profile
                  exported with the db2cfexp command can also be
                  imported during a response file installation using the
                  CLIENT_IMPORT_PROFILE keyword.

                   

                  You should export the client or server profile after
                  performing the installation and cataloging any data
                  sources.


         Customizing the sample response files that are provided for 
         each DB2 product
                  An alternative to using the response file generator or
                  the DB2 Setup wizard to create a response file is to
                  manually modify a sample response file. Sample
                  response files are provided on the DB2 product DVD.
                  The sample response files provide details about all
                  the valid keywords for each product.


db2_install command (Linux and UNIX platforms only)
         The db2_install command installs all components for the DB2
         product you specify with the English interface support. You can
         select additional languages to support with the -L parameter.
         You cannot select or deselect components. 

         Although the db2_install command installs all components for
         the DB2 product you specify, it does not perform user and group
         creation, instance creation, or configuration. This method of
         installation might be preferred in cases where configuration is
         to be done after installation. If you would rather configure
         your DB2 product while installing it, consider using the DB2
         Setup wizard.

          

         On Linux and UNIX operating systems, if you embed the DB2
         installation image in your own application, it is possible for
         your application to receive installation progress information
         and prompts from the installer in computer-readable form.

          

         This installation methods requires manual configuration after
         the product files are deployed.


Payload file deployment (Linux and UNIX only)
         This method is an advanced installation method that is not
         recommended for most users. It requires the user to physically
         install payload files. A payload file is a compressed tarball
         that contains all of the files and metadata for an installable
         component. 

         This installation methods requires manual configuration after
         the product files are deployed.

Note: DB2 product installations are no longer operating system packages
      on Linux and UNIX platforms. As a result, you can no longer use
      operating system commands for installation. Any existing scripts
      that you use to interface and query with DB2 installations will
      need to change.

Non-root installation

Non-root installation overview (Linux and UNIX)

Before Version 9.5, you could install products, apply and roll back fix
packs, configure instances, add features, or uninstall products only if
you had root privileges. Now, if you are a non-root user, you can
perform these tasks on Linux and UNIX platforms.

The DB2 installer automatically creates and configures a non-root
instance during a non-root installation. As a non-root user, you can
customize the configuration of the non-root instance during the
installation. You can also use and maintain the installed DB2 product
without root privileges.

The non-root installation of a DB2 product has one DB2 instance with
most features enabled by default.

A non-root installation can be attractive for many groups, such as the
following ones: 
*  Enterprises that have thousands of workstations and users who want to
   install a DB2 product without consuming a system administrator's time
*  Application developers who are not typically system administrators
   but use DB2 products to develop applications
*  Independent Software Vendors (ISVs) who develop software that does
   not require root authority yet embeds a DB2 product

Although non-root installations have most of the functionality of root
installations, there are some differences and limitations. You can lift
some of the limitations by having a root user run the db2rfe command.

Differences between root installations and non-root installations

In addition to a few limitations, the directory structure of a non-root
installation is slightly different than the directory structure of a
root installation.

During a root installation, subdirectories and files for the DB2 product
are created in a directory of the root user's choosing.

Unlike root users, non-root users cannot choose where DB2 products are
installed. Non-root installations are always placed in the $HOME/sqllib
directory, where $HOME represents the non-root user's home directory.
The layout of the subdirectories within the sqllib directory of a
non-root is similar to that of a root installation.

For root installations, multiple instances can be created. Instance
ownership is associated with the user ID under which the instance was
created.

Non-root installations can have only one DB2 instance. The non-root
installation directory contains all of the DB2 product files and
instance files with no soft links.

The following table summarizes the differences between root
installations and non-root installations. 

Table 5. Differences between root installations and non-root 
installations
+-----------------------+----------------------+----------------------+
| Criteria              | Root installations   | Non-root             |
|                       |                      | installations        |
+-----------------------+----------------------+----------------------+
| User can select       | Yes                  | No. DB2 products are |
| installation          |                      | installed under the  |
| directory             |                      | user's home          |
|                       |                      | directory.           |
+-----------------------+----------------------+----------------------+
| Number of DB2         | Multiple             | One                  |
| instances allowed     |                      |                      |
+-----------------------+----------------------+----------------------+
| Files deployed during | Program files only.  | Program files and    |
| installation          | Instances must be    | instance files. The  |
|                       | created after        | DB2 product is ready |
|                       | installation.        | for use immediately  |
|                       |                      | after installation.  |
+-----------------------+----------------------+----------------------+

Limitations of non-root installations

In addition to the differences between root installations and non-root
installations, there are several limitations on non-root installations.
This topic discusses the limitations to help you decide if you want to
use a non-root installation.

Product limitations
         Some DB2 products are not supported in non-root installations: 
         *  data server developer tool
         *  DB2 Embedded Application Server (DB2 EAS)
         *  DB2 Query Patroller
         *  DB2 Net Search Extender
         *   Locally installed DB2 Information Center

            Note: The locally installed DB2 Information Center is not
                  supported in non-root installations because it
                  requires root authority to start the daemon. However,
                  a non-root-installation DB2 instance can be configured
                  to use a locally installed DB2 Information Center if
                  it is installed on the same computer.


Features and tools limitations
         The following features and tools are not available in non-root
         installations: 
         *  The DB2 Administration Server (DAS) and its associated
            commands: dascrt, dasdrop, daslist, dasmigr, and dasupdt
         *  The Configuration Assistant
         *  The Control Center
         *  The ability for the db2governor to increase priority is not
            supported
         *  In the Work Load Manager (WLM), attempts to set agent
            priority in a DB2 service class in a non-root DB2 instance
            are allowed. However, the agent priority will not be
            respected, and no SQLCODE error is returned.
         *  Automatic starting of non-root DB2 instances at system
            reboot is not supported


Health monitor limitations 
         The following health monitor features are not supported in
         non-root installations: 
         *  Running script or task actions on alert occurrences
         *  Sending alert notifications


Partitioned database limitation
         Only single-partition databases are supported in non-root
         installations. You cannot add additional database partitions.

Listing DB2 products
         The output produced by the db2ls command, when run as a
         non-root user, is different than the output produced when run
         as a root user. For details, refer to the db2ls command topic.

DB2 copies
         Each non-root user can have only one copy of a DB2 product
         installed.

DB2 instance limitation
         In non-root installations, one DB2 instance is created during
         installation. Additional instances cannot be created.

DB2 instance actions can be performed only by the instance owner
         Root installations and non-root installations can coexist on
         the same computer in different installation paths. However, a
         non-root instance can be updated, or dropped (using the
         db2_deinstall command), only by the non-root user who owns the
         non-root instance. 

         A DB2 instance created by a user with root privilege can be
         updated or dropped only by a user with root privilege.


DB2 instance commands
         The following DB2 instance commands are unavailable in non-root
         installations: 

         db2icrt  When installing a DB2 product as a non-root user, a
                  single instance is automatically created and
                  configured. Further instances cannot be created in
                  non-root installations. However, if the automatically
                  created instance needs to be configured, you can use
                  the non-root install configuration command, db2nrcfg.

         db2iupdt The db2iupdt command cannot be used for non-root
                  instances. Instead, use the non-root install
                  configuration command (db2nrcfg) to update the
                  non-root DB2 instance. However, updating the non-root
                  instance is normally not required because it gets
                  updated automatically when updating your DB2 product.

         db2idrop The instance that gets automatically created during
                  non-root installations cannot be dropped. The DB2
                  product must be uninstalled to drop the DB2 instance.

         db2imigr Migration is not supported for non-root installations.

Migration limitation
         Root instances cannot be migrated to a non-root instance.

Post-installation actions can be performed only by the DB2 instance 
owner
         Root installations and non-root installations can coexist on
         the same computer. However, only the original non-root user who
         installed the DB2 product can perform subsequent actions such
         as: 
         *  Applying fix packs
         *  Adding features
         *  Installing add-on products


Adjusting ulimit values
         The ulimit command on UNIX and Linux sets or reports user
         resource limits, such as data and stack limits. For root
         instances, the database server dynamically updates required
         ulimit settings without changing the permanent settings.
         However, for non-root instances, the ulimit settings can only
         be checked during installation. A warning message is displayed
         if the settings are inadequate. Root authority is required to
         change the ulimit settings.



Limitations that can be overcome by running db2rfe

There are further limitations on non-root installations which can be
overcome by running the db2rfe command. The following features and
abilities are initially unavailable in non-root installations: 
*  Operating system-based authentication
*  High Availability (HA) feature
*  The ability to reserve service names in the /etc/services file
*  The ability to increase user data limits (ulimits). This ability
   applies only to AIX. On other platforms, user data limits must be
   increased manually.

Run the Enable root features for non-root install command (db2rfe) to
enable these features and abilities. Running the db2rfe command is
optional, and must be run by a user with root authority.



Authentication type in non-root installations

Operating system-based authentication is the default authentication type
for DB2 products. Since non-root installations do not support operating
system-based authentication, if you choose not to run the db2rfe command
after installing your DB2 product as a non-root user, then you must
manually set the authentication type. You can do so by updating the
following parameters in the database manager configuration (dbm cfg)
file: 
*  clnt_pw_plugin (Client userid-password plug-in configuration
   parameter)
*  group_plugin (Group plug-in configuration parameter)
*  srvcon_pw_plugin (Userid-password plug-in for incoming connections at
   the server configuration parameter)



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
systemsLinux systems. The DB2 Setup wizard is used to define your
installation preferences and to install your DB2 product on your system.



Before you start the DB2 Setup wizard: 
*  If you are planning on setting up a partitioned database environment,
   see how to do this by following the related link at the bottom of
   this topic.
*  Ensure that your system meets installation, memory, and disk
   requirements.
*  You can install a DB2 server using either root or non-root authority.
   For more information on non-root installation, see the related links.
*  The DB2 product image must be available. You can obtain a DB2
   installation image either by purchasing a physical DB2 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. You must have X
   windows software capable of rendering a graphical user interface for
   the DB2 Setup wizard to run on your machine. Ensure that the X
   windows server is running. Ensure that you have properly exported
   your display. For example, export DISPLAY=9.26.163.144:0.
*  If you are using security software in your environment, you must
   manually create required DB2 users before you start the DB2 Setup
   wizard.

Note: 
      *  The use of XML features is restricted to a database that is
         defined with the code set UTF-8 and has only one database
         partition.
      *  The DB2 Setup wizard fields do not accept non-English
         characters.



To start the DB2 Setup wizard:

1. If you have a physical DB2 product DVD, change to the directory where
   the DB2 product DVD is mounted by entering the following command:  
      cd /dvdrom

   where /dvdrom represents mount point of the DB2 product DVD.
2. If you downloaded the DB2 product image, you must decompress and
   untar the product file.  
   a. Decompress the product file: 
      gzip -d product.tar.gz

      where product is the name of the product that you downloaded.
   b. 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.
   c. 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/disk1) 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 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 may want to 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.

    

   Once 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.

    

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

    

   For root installations, DB2 products are installed, by default, in
   one of the following directoriesthe following directory: 

   AIX, HP-UX, and Solaris
            /opt/IBM/db2/V9.5

   Linux    /opt/ibm/db2/V9.5

    

   If you are installing on a system where this directory is already
   being used, the DB2 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 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







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.

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(TM) (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.

On Linux x86, if you want your DB2 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 and DB2 Workgroup Server Edition memory limits
         If you are installing DB2 Express Edition, the maximum allowed
         memory for the instance is 4GB. 

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

          

         The amount of memory allocated to the instance is determined by
         the INSTANCE_MEMORY database manager configuration parameter. 

         Important notes when migrating from Version 9.1:
                  
                  *  If the memory configuration for your Version 9.1
                     DB2 product exceeds the allowed limit, the DB2
                     product might not start after migrating to the
                     current version.
                  *  The self tuning memory manager will not increase
                     your overall instance memory limit beyond the
                     license limits.

Response file installation

Creating a response file using the sample response file (Linux and UNIX)



 After creating a response file, you might need to make changes to the
response file to activate or deactivate keywords.

One of the following scenarios should apply: 
*  You want to create a response file based on a sample response file
   (located in db2/platform/samples where platform refers to the
   appropriate hardware platform.)
*  You created a response file using the DB2 Setup wizard (based on your
   installation) and want to make changes to it.

If you are installing directly from the DVD, you must store the renamed
response file on another filesystem.

You can specify the name of the instance owner in the response file. If
this user does not already exist, DB2 will create this user on your
system.

To edit a response file:

1. If you are using the sample response file, copy the sample response
   file to a local file system and edit it using the Response file
   keywords topic as a guide.
2. Customize the sample response file.  

   To activate an item in the response file, remove the asterisk (*) to
   the left of the keyword. Then, replace the current setting to the
   right of the value with the new setting. The possible settings are
   listed to the right of the equal sign.

    

   Some product response files have mandatory keywords that you must
   provide values for. The mandatory keywords are documented in the
   comments of each response file.

    

   Keywords that are unique to installation are only specified in a
   response file during a response file installation.

3. Save the file on an exported file system available to everyone on the
   network.

Installing a DB2 product using a response file (Linux and UNIX)





 Before you begin the installation, ensure that:

*  For root installations, log on with the user ID that has root
   privileges. For non-root installations, log on with the user ID that
   is to own the DB2 installation.
*  Your system meets all of the memory, hardware, and software
   requirements to install your DB2 product.
*  You can install a DB2 product using a response file with either root
   or non-root authority. For more information on non-root installation,
   see the related links.
*  All DB2 processes associated with the copy of DB2 you are working
   with are stopped.



To perform a response file installation:

1. Enter the db2setup command as follows: 
      dvd/db2setup -r responsefile_directory/response_file

   where: 
   *  dvd represents the location of the DB2 installable image;
   *  responsefile_directory represents the directory where the
      customized response file is located; and
   *  response_file represents the name of the response file.

2. Check the messages in the log file when the installation finishes. 
   The installation logs are located, by default, in the /tmp directory:
   
   *  db2setup.log (db2setup_username.log for non-root installations,
      where username is the non-root user ID under which the
      installation was performed)
   *  db2setup.err (db2setup_username.err for non-root installations,
      where username is the non-root user ID under which the
      installation was performed)

   You can specify the location of the log file. An installation history
   log db2install.history is located in DB2DIR/install/logs where DB2DIR
   specifies the path where the DB2 product was installed. The default
   installation directory is: 
   *  For AIX, HP-UX or Solaris /opt/IBM/db2/V9.5
   *  For Linux/opt/ibm/db2/V9.5

    

   If more than one DB2 product is installed in the same location, you
   will see db2install.history.xxxx, where xxxx are digits, starting at
   0001 and increasing depending on how many DB2 copies you have
   installed.



If you want your DB2 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 and related products.

Installing a DB2 product using the db2_install or doce_install command 
(Linux and UNIX)



 Before you install DB2 products and features or the DB2 Information
Center:

*  You should refer to the installation documentation for the particular
   DB2 product you want to install. For example, if you want to install
   DB2 Enterprise Server Edition, then refer to the Quick Beginnings for
   DB2 Servers documentation to review installation prerequisites and
   other important setup information.
*  You can install a DB2 product using either root or non-root
   authority. However, you cannot use the doce_install to install the
   DB2 Information Center under non-root authority. For more information
   on non-root installations and limitations, see the Related Links.
*  The DB2 product image must be available. You can obtain a DB2
   installation image either by purchasing a physical DB2 product DVD,
   or by downloading an installation image from Passport Advantage.



The db2_install command installs DB2 products and features on supported
Linux and UNIX operating systems.

The doce_install command installs the DB2 Information Center on
supported Linux and UNIX operating systems.

You cannot manually install a DB2 product or feature using an operating
system's native installation utility such as rpm, SMIT, swinstall or
pkgadd. Any existing scripts containing a native installation utility
that you use to interface and query with DB2 installations will need to
change.

The db2_install command is not supported on the National Language
Package DVD.

Only one copy of the DB2 Information Center for the current release can
be installed on your system. The Information Center cannot be installed
in the same location where a DB2 product is installed. If you install
the DB2 Information Center on a system with a firewall, and you plan to
allow other systems to access the DB2 Information Center, you must open
the port in your firewall setting.

To install a DB2 product or feature using the db2_install command, or to
install the DB2 Information Center using the doce_install command:

1. If you have a physical DB2 product DVD, insert and mount the
   appropriate DVD or access the file system where the installation
   image was stored.
2. If you downloaded the DB2 product image, you must decompress and
   untar the product file.  
   a. Decompress the product file:  
      gzip -d product.tar.gz

      For example, 
      gzip -d ese.tar.gz

   b. Untar the product file:  

      On Linux operating systems
               
               tar -xvf product.tar

               For example, 
               tar -xvf ese.tar


      On AIX, HP-UX, and Solaris operating systems
               
               gnutar -xvf product.tar

               For example, 
               gnutar -xvf ese.tar

   c. Change directory into the product directory:  
      cd product

      For example, 
      cd ese

3. Enter the ./db2_install or ./doce_install command: 
   ./db2_install -b DB2DIR -p productShortName -c NLPackLocation -L language... -n 

   where: 
   *  DB2DIR specifies the path where the DB2 product will be installed.
      If the path is not specified, you are prompted to either select
      the default path or to provide the path. The default installation
      path is: 
      *  for AIX, HP-UX or Solaris operating systems: /opt/IBM/db2/V9.5
      *  for Linux operating systems: /opt/ibm/db2/V9.5

       

      If you provide your own path, you must specify the full path name.

       

      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

       

      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.

   *  productShortName specifies the DB2 product to be installed. 

      This parameter is case insensitive and is mandatory when the -n
      parameter is specified. The product short name (productShortName)
      can be found in the file ComponentList.htm (under the product full
      name) located in the /db2/plat directory on your media where plat
      is the platform name that you are installing on. You can only
      install one product at a time.

   *  NLPackLocation specifies the National Language Pack (NLPACK)
      location.
   *  language specifies national language support. You can install a
      non-English version of a DB2 product. However, you must run this
      command from the product DVD, not the National Language pack DVD. 

      By default, English is always installed, therefore, English does
      not need to be specified. When more than one language is required
      this parameter is mandatory. To indicate multiple languages,
      specify this parameter multiple times. For example, to install
      both French and German specify -L FR -L DE.

   *  n parameter indicates noninteractive installation mode. When this
      parameter is specified, both -b and -p must also be specified. You
      only need to specify -c and -L if applicable.

    When installing the DB2 Information Center, if you specify a port
   number other than the default, you might receive the error "The
   service name specified is in use". You can correct this error by
   either choosing to use the default port number or by specifying a
   different service name.



After installation, you must manually configure your DB2 server. Tasks
include user and instance creation and configuration.

Applying fix packs





It is recommended that you keep your DB2 environment running at the
latest fix pack level to ensure problem-free operation. To install a fix
pack successfully, perform all of the necessary pre-installation and
post-installation tasks.

A DB2 fix pack contains updates and fixes for problems (Authorized
Program Analysis Reports, or "APARs") found during testing at IBM, as
well as fixes for problems reported by customers. Each fix pack contains
an APARLIST.TXT file, which describes the fixes it contains.

Fix packs are cumulative. This means that the latest fix pack for any
given version of DB2 contains all of the updates from previous fix packs
for the same version of DB2.

The fix pack images available are: 
*  A single server image. 

   The single server image contains the new and updated code required
   for all DB2 server products and the IBM Data Server Client. If more
   than one DB2 server product is installed in a single location, the
   DB2 server fix pack applies maintenance code updates to all the
   installed DB2 server products. The Data Server Client fix pack is
   contained within the one DB2 server fix pack (namely the fix pack
   that can service any one of the following server products: Enterprise
   Server Edition, Workgroup Server Edition, Express Edition, Personal
   Edition, Connect Enterprise Edition, Connect Application Server
   Edition, Connect Unlimited Edition for zSeries(R), and Connect
   Unlimited Edition for i5/OS(R)). You can use the DB2 server fix pack
   to upgrade a Data Server Client.

    

   A single server image can also be used to install any of the DB2
   database server products, at a particular fix pack level, with a DB2
   try and buy license by default.

*  A fix pack for each of the other DB2 database products. 

   Use this fix pack only if you only have non-server database products
   or add-on products installed. For example, IBM Data Server Runtime
   Client or Query Patroller.

    

   Do not use this type of fix pack if the installed DB2 products are
   only DB2 server products or a Data Server Client. Instead, use the
   single server image fix pack.

    

   For Windows platforms, if you have more than one DB2 database product
   (which includes at least one product that is not a Data Server Client
   or a DB2 server) installed in a single DB2 copy, you must download
   and uncompress all of the corresponding product-specific fix packs
   before starting the fix pack installation process.

*  A universal fix pack (on Linux or UNIX platforms only). 

   The universal fix pack services installations where more than one DB2
   database product has been installed.

    

   The universal fix pack is not needed if the installed DB2 products
   are only DB2 server products or a Data Server Client. In this case,
   the single server image fix pack should used.

Restrictions
         
         *  A DB2 Version 9.5 fix pack can only be applied to DB2
            Version 9.5 general availability (GA) or fix pack level
            copies.
         *  All DB2 instances, DAS, and applications related to the DB2
            copy being updated must be stopped before installing a fix
            pack.
         *  If you are using the database partitioning feature (DPF),
            prior to installing the fix pack, you must stop the database
            manager on all nodes. You must install the fix pack on the
            instance owning node and all other partitioned nodes. All
            computers participating in the instance must be upgraded to
            the same fix pack level.
         *  On Linux or UNIX operating systems: 
            *  If you have DB2 products on a Network File System (NFS),
               you must ensure the following are stopped completely
               before installing the fix pack: all instances, the DB2
               administration server (DAS), interprocess communications
               (IPC), and applications on other machines using the same
               NFS mounted installation.
            *  If the system commands fuser or lsof are not available,
               the installFixPack command cannot detect loaded DB2
               files. You must ensure no DB2 files are loaded and
               provide an override option to install the fix pack. On
               UNIX, the fuser command is required to check for loaded
               files. On Linux, either the fuser command or lsof command
               is required. 

               For details on the override option, see the
               installFixPack command.

         *  On client applications, after a fix pack has been applied,
            to perform autobind of applications, the user must have bind
            authority.
         *  Installation of a DB2 fix pack will not service data server
            administrator tool or data server developer tool.

For non-root installations on Linux or UNIX, root-based features (such
as High Availability and operating system-based authentication) can be
enabled using the db2rfe command. If root-based features were enabled
after installing your DB2 product, you must rerun the db2rfe command
each time a fix pack is applied in order to re-enable those features.
For details, see the non-root related links below.

On Linux or UNIX operating systems, if national languages have been
installed, you also require a separate national language fix pack. The
national language fix pack can not be installed alone. A universal or
product-specific fix pack must be applied at the same time and they must
both be at the same fix pack level. For example, if you are applying a
universal fix pack to non-English DB2 database products on Linux or
UNIX, you must apply both the universal fix pack and the national
language fix pack to update the DB2 database products.

If you have multiple DB2 copies on the same system, those copies can be
at different version and fix pack levels. If you want to apply a fix
pack to one or more DB2 copies, you must install the fix pack on those
DB2 copies one by one.

To install a fix pack:

1. Access and download the latest DB2 fix pack by selecting the link for
   fix pack downloads from the DB2 Support Web site at
   http://www.ibm.com/software/data/db2/udb/support.html.
2. Check fix pack prerequisites, and perform the necessary tasks prior
   to installing a fix pack. If you already have DB2 database products
   installed, you must also stop various DB2 processes. See the fix pack
   Readme for details.
3. Choose a fix pack installation method and install the fix pack.



Check the log file for any post-installation steps, or error messages
and recommended actions.

Installation of more tools can be launched from the DB2 installation

You can choose to install the data server developer tool or the data
server administrator tool during a DB2 server product installation.

If you choose to install the data server developer tool or the data
server administrator tool during a DB2 server installation, the DB2
Setup wizard now launches a standalone installation program after it
installs your DB2 server product. You can also now install the data
server developer tool or the data server administrator tool from the DB2
Setup launchpad without installing a DB2 server product.

The data server developer tool and the data server administrator tool
have their own standalone installation program that you can launch
independently from a DB2 installation. The DB2 installation program does
not support the installation of these tool using DB2 response files.

To install the data server developer tool or the data server
administrator tool in silent mode, use the non-interactive installation
methods provided by the standalone installation program.

