Installs all features of a DB2® database
product to the given path. This command is available only on Linux and UNIX operating systems.
Authorization
Root installations require
root user authority. For non-root installations, you must log on with
the user ID that owns the non-root installation.
Command syntax
>>-db2_install--+-------------------+--+-------------+---------->
'- -b--install-path-' '- -f NOTSAMP-'
>--+---------------+--+------------------+---------------------->
'- -f--nobackup-' '- -f--ignoreType1-'
>--+-----------------------+--+----------------------+---------->
'- -p--productShortName-' '- -c--NLPACK_location-'
>--+-----+--+-----+--+---------------+--+---------------+------->
'- -n-' '- -m-' '- -L--language-' '- -l--log-file-'
>--+-----------------+--+-----+--------------------------------><
'- -t--trace-file-' +- -h-+
'- -?-'
Command parameters
- -b install-path
Specifies the path where the DB2 database
product is to be installed. install-path must be
a full path name and its maximum length is limited to 128 characters.
This parameter is mandatory when the -n parameter
is specified.
The -b option is not required
for a non-root installation of the DB2 database
product, but it is still mandatory for a root installation, if the -n option
is used. If -b is used in a non-root install,
the path must be valid, which has to be the user's $HOME/sqllib.
For both root and non-root install, the length of the absolute installation
path is limited to 128 bytes.
- -f NOTSAMP
- Specifies that IBM® Tivoli® System
Automation for Multiplatforms (SA MP) should
not be either installed or updated.
- -f nobackup
- This applies to the non-root upgrade only. Forces db2_install to
not backup installation files when the components are updated. If
you choose not to backup the files, the space requirement of the installation
directory is reduced. However, choosing not to backup the files also
means that if any errors occur, the DB2 database
installer will not be able to perform a rollback operation. In this
case, you will need to manually clean up the files and reinstall the
product.
- -f ignoreType1
- This applies to the non-root upgrade only. Forces db2_install to
ignore type-1 indexes when checking the database status.
- -p productShortName
- Specifies
the DB2 database 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). The ComponentList.htm file lists all the
components that are installed with your DB2 database
product. The file is located in the db2/plat subdirectory
on your media where plat is the platform name that
you are installing on. You can only install one product at a time.
Note: The
components listed in the ComponentList.htm file
is dependant on the version of DB2 that
you are installing. This file might be different on another version
of DB2.
- -c NLPACK_location
- Specifies the absolute path location of the related DB2 National Language Pack (NLPACK). This parameter
is mandatory when -n is specified. The DB2 NLPACK location needs to be
provided explicitly if all of the following conditions are met:
- The -n option is specified.
- The installation requires National Language (non-English) support.
- The DB2 NLPACK is neither
inside the DB2 database product
image nor in the same subdirectory as the DB2 database product image.
- -n
- Specifies noninteractive mode. When specified, you must also specify -b, -p,
and/or -c.
- -m
- This option applies to non-root installation only. Specifies upgrade
of a non-root copy. During upgrade, all preexisting DB2 database products in the current path are
removed. Upgrade installs the specified product. Following the upgrade,
other DB2 database products
need to be installed separately.
- -L language
- Specifies national language support. You can install a non-English
version of a DB2 database product.
However, you must run this command from the product CD, not the National
Language pack CD. 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. This parameter
is case insensitive.
- -l log-file
- Specifies the log file. For root installations, the default log
file is /tmp/db2_install.log$$,
where $$ represents the process ID. For non-root
installations, the default log file is /tmp/db2_install_userID.log,
where userID represents the user ID that owns the
non-root installation. If IBM Tivoli System
Automation for Multiplatforms (SA MP) is
being installed or updated with the db2_install command,
the corresponding log file will be located in the same directory as DB2 database log files.
- -t trace-file
- Turns on the debug mode. The debug information is written to the
file name specified as trace-file.
- -h | -?
- Displays usage information.
Usage notes
Default log and trace filenames
for a non-root DB2 database
installation includes the user ID so as not to overwrite files resulting
from root installations of DB2 database
products.
The default file names for non-root install will be
as follows (the
userID is the username of the non-root
user who performs the non-root installation):
- /tmp/db2_install_userID.log
- /tmp/db2_install_userID.err
- /tmp/db2_install_userID.trc
After the non-root installation is complete, the log file
will be copied to $DB2DIR/install/logs directory,
which is the same directory as for a root installation.
For
additional information, see the -l logfile command
parameter.
If
a IBM PowerHA® SystemMirror for AIX® cluster
is running, you can not perform a IBM Tivoli System
Automation for Multiplatforms (SA MP) installation,
upgrade or update because SA MP bundles
Reliable Scalable Cluster Technology (RSCT) file sets that are dependent
on PowerHA SystemMirror.
To skip the SA MP installation
use the db2_install command or the installFixPack command.
For information on installing or upgrading SA MP using
a PowerHA SystemMirror cluster,
see the white paper entitled "Upgrade guide for DB2 Servers in HACMP™ Environments",
which is available from the IBM Support
and downloads web site (http://www.ibm.com/support/docview.wss?uid=swg21045033).