To install a DB2(R) product, the following operating system, hardware, and communications prerequisites must be met:
| Operating System | Hardware |
|---|---|
AIX(R) Version 5.3
|
One of:
|
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
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:
As mentioned, the setup for NFS will require several manual actions including:
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.
To install a DB2 product, the following operating system, hardware, and communications prerequisites must be met:
| Operating System | Hardware |
|---|---|
|
DB2 products are supported on:
|
Itanium(R) based HP Integrity Series Systems |
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.
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:
As mentioned, the setup for NFS will require several manual actions including:
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.
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:
The supported operating systems for Linux include:
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:
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.
The following tables list the package requirements for SLES and RHEL distributions for DB2 Version 9.5:
| Package name | Description |
|---|---|
| libaio | contains the asynchronous library required for DB2 servers. |
| compat-libstdc++ | contains libstdc++so.5 |
| Directory | Package name | Description |
|---|---|---|
| /System Environment/Libraries | libaio | contains the asynchronous library required for DB2 servers. |
| /System Environment/Libraries | compat-libstdc++ | contains libstdc++so.5 |
The following tables list the package requirements for SUSE Linux and Red Hat distributions for DB2 Version 9.5 partitioned servers.
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.
All required packages should be installed and configured before continuing with the DB2 setup. For general Linux information, see your Linux distribution documentation.
| 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. |
| Directory | Package name | Description |
|---|---|---|
| /System Environment/Shell | pdksh | Korn Shell. This package is required for partitioned database environments. |
| /Applications/Internet | openssh | This package contains a set 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 Environment/Daemons | openssh-server | This package contains a set 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 Environment/Daemons | rsh-server | This package contains a set 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 Environment/Daemons | nfs-utils | Network File System support package. It allows access to local files from remote computers. |
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:
As mentioned, the setup for NFS will require several manual actions including:
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.
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:
To disable SELinux, you can do one of the following:
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.
To install a DB2 product, the following operating system, hardware, and communications prerequisites must be met:
| Operating System | Hardware |
|---|---|
Solaris 9
|
UltraSPARC |
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.
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:
The Fujitsu PRIMEPOWER patches for the Solaris Operating System can be downloaded from FTSI at: http://download.ftsi.fujitsu.com/.
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:
As mentioned, the setup for NFS will require several manual actions including:
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.
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.
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:
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.
This topic provides information about DB2 installation methods. The following table shows the installation methods that are available by operating system.
| Installation method | Windows(R) | LinuxLinux or UNIX |
|---|---|---|
| DB2 Setup wizard | Yes | Yes |
| Response file installation | Yes | Yes |
| db2_install command | No | Yes |
| Payload file deployment | No | Yes |
The following list describes DB2 installation methods.
The DB2 Setup wizard can also create DB2 instances and response files that can be used to duplicate this installation on other machines.
On Linux and UNIXLinux platforms, an X server is required to display the DB2 Setup wizard.
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:
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.
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.
This installation methods requires manual configuration after the product files are deployed.
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:
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.
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.
| Criteria | Root installations | Non-root installations |
|---|---|---|
| User can select installation directory | Yes | No. DB2 products are installed under the user's home directory. |
| Number of DB2 instances allowed | Multiple | One |
| Files deployed during installation | Program files only. Instances must be created after installation. | Program files and instance files. The DB2 product is ready for use immediately after installation. |
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.
A DB2 instance created by a user with root privilege can be updated or dropped only by a user with root privilege.
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:
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.
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:
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:
To start the DB2 Setup wizard:
cd /dvdromwhere /dvdrom represents mount point of the DB2 product DVD.gzip -d product.tar.gzwhere product is the name of the product
that you downloaded.tar -xvf product.tar
gnutar -xvf product.tar
cd ./productwhere product is
the name of the product that you downloaded.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:
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:
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:
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.
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.
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:
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:
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.
Before you begin the installation, ensure that:
To perform a response file installation:
dvd/db2setup -r responsefile_directory/response_filewhere:
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.
Before you install DB2 products and features or the DB2 Information Center:
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:
gzip -d product.tar.gzFor example,
gzip -d ese.tar.gztar -xvf product.tarFor
example,
tar -xvf ese.tar
gnutar -xvf product.tarFor
example,
gnutar -xvf ese.tar
cd productFor
example,
cd ese./db2_install -b DB2DIR -p productShortName -c NLPackLocation -L language... -nwhere:
If you provide your own path, you must specify the full path name.
DB2 installation paths have the following rules:
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.
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.
After installation, you must manually configure your DB2 server. Tasks include user and instance creation and configuration.
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:
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.
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.
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.
For details on the override option, see the installFixPack command.
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:
Check the log file for any post-installation steps, or error messages and recommended actions.
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.