This topic describes how to set up a partitioned database
environment. You will use the DB2 Setup wizard
to install your instance-owning database server and to create the
response files that will in turn be used to create your participating
database servers.
About this task
A
database partition is part of a database that consists of its own
data, indexes, configuration files, and transaction logs. A partitioned
database is a database with two or more partitions.
Before you begin
Note: A
partitioned database environment is not supported in non-root installations.
- Ensure that you have the InfoSphere® Warehouse Activation CD license
key that will need to be copied over to all participating computers.
- The same number of consecutive ports must be free on each computer
that is to participate in the partitioned database environment. For
example, if the partitioned database environment will be comprised
of four computers, then each of the four computers must have the same
four consecutive ports free. During instance creation, a number of
ports equal to the number of logical partitions on the current server
will be reserved in the /etc/services on Linux and UNIX and in the %SystemRoot%\system32\drivers\etc\services on Windows. These ports will be
used by the Fast Communication Manager. The reserved ports will be
in the following format:
DB2_InstanceName
DB2_InstanceName_1
DB2_InstanceName_2
DB2_InstanceName_END
The only mandatory entries are
the beginning (DB2_InstanceName) and ending (DB2_InstanceName_END)
ports. The other entries are reserved in the services file so that
other applications do not use these ports
To support multiple participating DB2® database
servers, the computer on which you want to install DB2 must belong to an accessible domain. However,
you can add local partitions to this computer even though the computer
doesn't belong to a domain.
- On Linux and UNIX systems, a remote shell utility is required
for partitioned database systems. DB2 database
systems support the following remote shell utilities:
By default, DB2 database
systems use 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. For more information
about security issues when installing DB2 database
products, see the Related Links.
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 registry
variable immediately after the DB2 installation
is complete. If this registry variable is not set, rsh is used.
- On Linux and UNIX operating systems, ensure the hosts file
under the etc directory does not contain an entry
for "127.0.0.2" if that IP address maps to the fully qualified
hostname of the machine.
Procedure
To set up a partitioned database environment:
- Install your instance-owning database server using the DB2
Setup wizard. For detailed instructions, see the appropriate "Installing DB2 servers" topic for your platform.
- On the Select installation, response files creation,
or both window, ensure that you select the Save
my installation settings in a response files option. After
the installation has completed, two files will be copied to the directory
specified in the DB2 Setup wizard: PROD_ESE.rsp and PROD_ESE_addpart.rsp.
The PROD_ESE.rsp file is the response file for
instance-owning database servers. The PROD_ESE_addpart.rsp file
is the response file for participating database servers.
- On the Set up partitioning options for the DB2 instance window,
ensure that you select Multiple partition instance,
and enter the maximum number of logical partitions.
- Make the DB2 install
image available to all participating computers in the partitioned
database environment.
- Distribute the participating database servers response
file (PROD_ESE_addpart.rsp).
- Install a DB2 database
server on each of the participating computers using the db2setup command
on Linux and UNIX, or the setup command
on Windows:
- Linux and UNIX
- Go to the directory where the DB2 database
product code is available and run:
./db2setup -r /responsefile_directory/response_file_name
- Windows
-
setup -u x:\responsefile_directory\response_file_name
For example, here is the command using the PROD_ESE_addpart.rsp as
the response file:
- Linux and UNIX
- Go to the directory where the DB2 database
product code is available and run:
./db2setup -r /db2home/PROD_ESE_addpart.rsp
where /db2home is
the directory where you have copied the response file.
- Windows
-
setup -u c:\resp_files\PROD_ESE_addpart.rsp
where c:\resp_files\ is
the directory where you have copied the response file.
- (Linux and UNIX only) Configure the db2nodes.cfg file.
The DB2 installation only reserves
the maximum number of logical partitions you want to use for the current
computer, but does not configure the db2nodes.cfg file.
If you do not configure the db2nodes.cfg file,
the instance is still a single partitioned instance.
- Update the services file on the participating
servers to define the corresponding FCM port for the DB2 instance. The services file is
in the following location:
- /etc/services on Linux and UNIX
- %SystemRoot%\system32\drivers\etc\services on Windows
- For partitioned database environments on Windows 2000 or later, start
the DB2 Remote Command Service
security feature to protect your data and resources.
To
be fully secure, start either the computer (if the service is running
under the context of the LocalSystem account) or a user for delegation
(if the service is being run under the logon context of a user).
To
start the DB2 Remote Command
Service security feature:
- Open the Active Directory Users and Computers window
on the domain controller, click Start and select
- In the right window panel, right-click the computer
or user to start, select Properties
- Click the General tab and select
the Trust computer for delegation check box.
For user setting, click the Account tab and
select the Account is trusted for delegation check
box in the Account option group. Ensure that
the Account is sensitive and cannot be delegated box
has not been checked.
- Click OK to start the computer
or user for delegation.
Repeat these steps for each computer or user that needs to
be started. You must restart your computer for the security change
to take effect.