Checks whether your system meets
the prerequisites for the installation of a specific version of DB2® for Linux, UNIX, and Windows.
By
using this command, you can determine whether your system satisfies
the prerequisites before you download
DB2 for Linux, UNIX, and Windows and
start the installation process. The
db2prereqcheck command
uses a resource XML file that contains the prerequisites. The default
path of the XML file is located in
DB2 installation/cfg/DB2prereqs.xml.
You must have read or write permissions on the XML file. Do not modify
the contents of the XML file.
Note: If
you do not specify any options for the db2prereqcheck command,
both DB2 pureScale and non-DB2 pureScale server prerequisites are
checked for all DB2 versions listed in the DB2prereqs.xml file.
Command Syntax
>>-db2prereqcheck--+--------------------------+----------------->
+- -v--version-------------+
'-+-----+--+-------------+-'
'- -l-' '-f--xml_file-'
>--+--------------------------------+--+----------------+------->
+-c------------------------------+ '-o--output-file-'
'- -p--| DB2-pureScale-options |-'
>--+---+--+---+--+---+-----------------------------------------><
'-s-' +-u-+ '-i-'
'-g-'
DB2-pureScale-options
|--t--+--------------------------+------------------------------>
+-SINGLE_IB_PORT_CLUSTER---+
+-MULT_IB_PORT_CLUSTER-----+
+-SINGLE_ROCE_PORT_CLUSTER-+
'-MULTI_ROCE_PORT_CLUSTER--'
>--+-----------------------------------------------------------------------------------+--|
| .-,---------. |
| V | |
'-hl----host-name-+--+----------------+--+-------------------+--+-----------------+-'
| .-,------. | '-iu--instance_user-' | .-,-------. |
| V | | | V | |
'-dl----device-+-' '-nl----netname-+-'
Command Parameters
- -v version
- Checks the prerequisites for the specific DB2 version. The -i
and -v parameters are mutually exclusive
Note: Starting from DB2 Version 10.1 Fix Pack 4,
this parameter checks the prerequisites for the specific DB2 version and prints all the results of prerequisite
validation on the screen. If you do not specify a version, all versions
in the resource XML file will be checked.
- -l
- Checks both the pureScale® and
non-DB2 pureScale prerequisites
for the latest DB2 version that
is defined in the resource XML file. The -l and -v parameters
are mutually exclusive.
Note: This parameter is available in DB2 Version
10.1 Fix Pack 4 and later fix packs only.
- -f xml-file
- Specifies the name of the XML resource file. If you
do not specify the -f parameter, the DB2
installation/cfg/DB2prereqs.xml file is used.
- -c
- Checks the prerequisites for thin client.
- The -c, -u, -g,
and -p parameters are mutually exclusive
- -p
- Checks the prerequisites for the DB2 pureScale environment (Linux and AIX® operating systems only). This is the default
option.
- The -c, -u, -g,
and -p parameters are mutually exclusive.
Important: To
validate prerequisites requirement for a specific network configuration
of a DB2 pureScale installation, the -t network
configuration type option should also be specified along
with this option.
- -o output-file
- Specifies a name for the output file. For example, db2prereqcheck.rpt.
If you do not specify a filename the output will be displayed on the
screen.
- -s
- Print prerequisite validation summary on screen.
- -u
- Checks the uDAPL requirement for the DB2 pureScale environment
(Linux and AIX operating systems only).
- The -c, -u, -g,
and -p parameters are mutually exclusive.
On
RoCE networks, you must manually ensure that the AIX and uDAPL software prerequisites are satisfied.
The db2prereqcheck command does not validate the
levels of the AIX and uDAPL software.
- -g
- Checks the GPL compilation requirement (Linux operating systems only)
- The -c, -u, -g,
and -p parameters are mutually exclusive
- -i
- Checks the non-DB2 pureScale prerequisites for the latest DB2
version that is defined in the resource XML file. The -i and -v parameters
are mutually exclusive
Note: Starting
from DB2 Version 10.1 Fix Pack 4, this parameter checks the non-DB2 pureScale prerequisites for
all the DB2 versions that is
defined in the resource XML file. The -i and -p parameters
are mutually exclusive.
- -t
- Validates the prerequisites for a specific type of
network configuration (Linux operating
systems only)
- The network configuration type must be SINGLE_IB_PORT_CLUSTER, MULT_IB_PORT_CLUSTER, SINGLE_ROCE_PORT_CLUSTER or MULTI_ROCE_PORT_CLUSTER
- -hl host-name
- Specifies a list of hosts that are checked for passwordless
root SSH access between all hosts.
- -dl device
- Specifies one or more PVIDs (on AIX operating systems)
or WWNs (on Linux operating systems) of the shared disks that are
verified to make sure that they are accessible by all hosts. If you
specify this parameter, you must also specify the -hl parameter.
- -iu instance_user
- Specifies the instance user name. The UID and GID of the instance
user name are verified to make sure they are the same across all hosts.
If you specify this parameter, you must also specify the -hl parameter.
- -nl netname
- Specifies the list of netnames. These netnames are
used to ping the RocE & IB networks to verify that they are pingable
between all hosts.
Examples
To
check whether the system meets the basic pureScale prerequisites for a specific DB2 version, run the db2prereqcheck command
with -p ,-v <version number>, -h1 <set
of hosts (member and cf hosts)>, -dl <one
ore more shared disks for GPFS file system>, and -iu <pureScale
instance userid> parameters. For example,
$ ./db2prereqcheck -p -v 10.1.0.0 -hl <host1,host2..> -dl <shared_disk1,shared_disk2..> -iu <user>
To
check whether the system meets the comprehensive pureScale prerequisites for a specific
type of network configuration (Linux operating
systems only) and for a specific DB2 version,
run the db2prereqcheck command with -p ,-v <version
number>, -h1 <set of hosts(member and cf hosts)>, -dl <one
ore more shared disks for GPFS file system>, -iu <pureScale
instance userid>, and -nl <list of networks> parameters.
For example,
$ ./db2prereqcheck -p -v 10.1.0.0 -hl <host1,host2..> -dl <shared_disk1,shared_disk2..> -iu <user> -nl <netname1,netname2..>
To
check whether the system meets the prerequisites for DB2 Version 10.1.0.0, issue the following command:
db2prereqcheck -v 10.1.0.0 -s
To
check whether the system meets the prerequisites for the thin client
of DB2 Version 10.1, issue the
following command:
db2prereqcheck -c -v 10.1.0.0 -s