|
Contents
Installation requirements for DB2 servers and IBM data server clients
(Windows)
Disk and memory requirements
DB2 installation methods
Installing DB2 servers (Windows)
Editing a response file (Windows)
Applying fix packs
Installation of more tools can be launched from the DB2 installation
Installation requirements for DB2 servers and IBM data server clients
(Windows)
To install a DB2(R) product, the following operating system, software,
and hardware prerequisites must be met:
Table 1. Windows workstation platforms
+------------------+------------+------------------+------------------+
| Operating System | Prerequisi | Hardware | Notes |
| | tes | | |
+------------------+------------+------------------+------------------+
| Windows(R) XP | Windows XP | All Intel(R) and | |
| Professional | Service | AMD processors | |
| (32-bit and x64) | Pack 2 or | capable of | |
| Windows Vista | later | running the | |
| Ultimate (32-bit | IBM(R) | supported | |
| and x64) | Data | Windows | |
| | Server | operating | |
| Windows Vista | Provider | systems (32-bit | |
| Business (32-bit | for .NET | and x64 based | |
| | applicatio | | |
| Windows Vista | ns and CLR | | |
| Enterprise | server-sid | | |
| (32-bit and x64) | e | | |
| | procedures | | |
| | require | | |
| | SP1 or | | |
| | .NET 2.0 | | |
| | framework | | |
| | runtime | | |
| | | | |
| | data | | |
| | server | | |
| | provider | | |
| | for .NET | | |
| | applicatio | | |
| | ns are | | |
| | supported | | |
+------------------+------------+------------------+------------------+
Table 2. Windows server platforms
+------------------+------------------+------------+------------------+
| Operating System | Prerequisites | Hardware | Notes |
+------------------+------------------+------------+------------------+
| Windows 2003 | Service Pack 1 | All Intel | |
| Standard Edition | or later. | and AMD | |
| (32-bit and x64) | R2 is also | processors | |
| Windows 2003 | supported | capable of | |
| Enterprise | | running | |
| Edition (32-bit | IBM data server | the | |
| and x64) | provider for | supported | |
| | .NET client | Windows | |
| Windows 2003 | applications and | operating | |
| Datacenter | CLR server-side | systems | |
| Edition (32-bit | procedures | | |
| and x64) | require .NET 1.1 | | |
| | SP1 or .NET 2.0 | | |
| | framework | | |
| | runtime | | |
| | | | |
| | 64-bit IBM data | | |
| | server provider | | |
| | for .NET | | |
| | supported | | |
+------------------+------------------+------------+------------------+
Additional software considerations
* Windows Installer 3.0 is required. It will be installed by
the installer if is it not detected.
* IBM Data Server Provider for .NET client applications and
CLR server-side procedures require .NET 1.1 SP1 or .NET 2.0
framework runtime. In an x64 environment, 32-bit IBM data
server provider for .NET applications will run in the WOW64
emulation mode.
* MDAC 2.8 is required. The DB2 Setup wizard will install MDAC
Note: If a previous version of MDAC (for example, 2.7) is
already installed, DB2 install will upgrade MDAC to
2.8. For a typical install, MDAC 2.8 is installed. For
a custom install, MDAC 2.8 is installed but only if
you have not deselected the default which is to
install it. If you deselect MDAC as part of a custom
install, it will not be installed.
* If you plan to use LDAP (Lightweight Directory Access
Protocol), you should use either a Microsoft(R) LDAP client
or the IBM Tivoli(R) Directory Server v6 client (also known
as the IBM LDAP client which is included with DB2 products).
Prior to installation of the Microsoft Active Directory, you
will need to extend your directory schema using the db2schex
utility, which can be found on the installation media under
the db2\Windows\utilities directory.
The Microsoft LDAP client is included with the operating
system for Windows XP, and Windows Server 2003.
* TCP/IP support must be enabled to view online help.
* One of the following browsers is required to view online
help, run the DB2 install launchpad (setup.exe), and to run
First Steps (db2fs):
* Internet Explorer 6 and up
* Firefox 1.0 and up
* Netscape 7.0 and up
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(R) and UNIX(R) 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:
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.
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 3. Installation method by operating system.
+-----------------------+----------------------+----------------------+
| Installation method | Windows | LinuxLinux or UNIX |
+-----------------------+----------------------+----------------------+
| DB2 Setup wizard | Yes | Yes |
+-----------------------+----------------------+----------------------+
| installation | | |
+-----------------------+----------------------+----------------------+
| db2_install command | No | Yes |
+-----------------------+----------------------+----------------------+
| Payload file | No | Yes |
| deployment | | |
The following list describes DB2 installation methods.
DB2 Setup wizard
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
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,
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
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.
Installing DB2 servers (Windows)
This task describes how to start the DB2 Setup wizard on Windows. You
will use the DB2 Setup wizard to define your installation and install
your DB2 product on your system.
Prerequisites
Before you start the DB2 Setup wizard:
* If you are planning on setting up a partitioned database
environment, see the "Setting up a partitioned database
environment" topic.
* Ensure that your system meets installation, memory, and disk
requirements.
* If you are planning to use LDAP on Windows to register the
DB2 server in Active Directory, you should extend the
directory schema before you install.
* You must have a local Administrator user account with the
recommended user rights to perform the installation. In DB2
servers where LocalSystem can be used as the DAS and DB2
partitioning feature, a non-administrator user with elevated
privileges can perform the installation.
* Although not mandatory, it is recommended that you close all
programs so that the installation program can update any
files on the computer without requiring a reboot.
Restrictions
* The DB2 copy name and the instance name cannot start with a
numeric value.
* The DB2 copy name and the instance name must be unique among
all DB2 copies.
* The use of XML features is restricted to a database that has
only one database partition.
one of the following is already installed:
* IBM Data Server Runtime Client
* IBM Data Server Driver for ODBC, CLI, and .NET
* DB2 Information Center.
* The DB2 Setup wizard fields do not accept non-English
To start the DB2 Setup wizard:
1. Log on to the system with the local Administrator account that you
have defined for the DB2 installation.
2. If you the DB2 product DVD, insert it into the drive. If enabled, the
auto-run feature automatically starts the DB2 Setup Launchpad. If the
auto-run does not work, use Windows Explorer to browse the DB2
Launchpad.
3. If you downloaded the DB2 product from passport advantage, run the
executable file to extract the DB2 product installation files. Use
Windows Explorer to browse the DB2 installation files and
double-click on the setup icon to start the DB2 Setup Launchpad.
4. From the DB2 Setup Launchpad, 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.
If you have no existing DB2 products installed on your computer,
launch the installation by clicking Install New. Proceed through the
installation following the DB2 Setup wizard's prompts.
If you have at least one existing DB2 product installed on your
computer, you can:
* Click Work with Existing to upgrade an existing DB2 copy, to add
functionality to an existing DB2 copy, migrate an existing DB2
Version 8 or Version 9.1 copy, or to install an add-on product.
6. The DB2 Setup wizard will determine the system language, and launch
the setup program for that language. Online help is available to
guide you through the remaining steps. To invoke the online help,
click Help or press F1. You can click Cancel at any time to end the
installation.
Your DB2 product will be installed, by default, in the <Program
Files>\IBM\sqllib directory, where <Program Files> represents the
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.
For information on errors encountered during installation, review the
installation log file located in the My Documents\DB2LOG\ directory. The
log file uses the following format: DB2-ProductAbrrev-DateTime.log, for
example, DB2-ESE-Tue Apr 04 17_04_45 2006.log.
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. By default, DB2 information will be accessed from the web if
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
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.
Editing a response file (Windows)
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\Windows\samples).
* You created a response file using the DB2 Setup wizard (based on your
installation) and want to make changes to it.
* You have already set up and configured your DB2 product and you want
to distribute this exact configuration across your network using the
response file generated by the response file generator. If you are
using the response file generator after generating the response file,
you might need to input user names and passwords .
You should install DB2 products only on a drive which is local to the
target workstation. Installing on a non-local drive can cause
performance and availability problems.
To edit a response file:
1. If you are using the sample response file, make a copy of it and open
the DB2 Setup wizard, open it in a text editor.
2. Customize the response file.
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 the shared network drive so that it is available to
the installation server. If you have made any changes, save the file
under a new file name to preserve the original sample response file.
If you are installing directly from the product DVD, you should store
the renamed response file on another drive.
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. | 
