Filter
Top Products
Related concepts:
v “Security issues when installing the DB2 database manager” on page 6
Related tasks:
v “Modifying kernel parameters (Linux)” in Quick Beginnings for DB2 Servers
v “Preparing to install DB2 for Linux on zSeries” in Quick Beginnings for DB2
Servers
Related reference:
v “Communication protocols supported” in Quick Beginnings for DB2 Clients
v “IBM Software Development Kit for Java levels for DB2 products” in Quick
Beginnings for DB2 Servers
v “Communications variables” in Performance Guide
Centralized user-management considerations (Linux)
In environments that include security software, such as NIS (Network Information
Services) or NIS+, there are some installation considerations. The DB2 installation
scripts attempt to update objects that are under the control of the security
packages, such as users and groups, and will not be able to do so if NIS or NIS+ is
being used for user management.
At instance creation, without a security component present, instance owner’s group
list is modified to include that of the database administrative server (DAS) user’s
primary group, if the DAS is created. If the instance creation program is unable to
modify these properties (it will not if NIS/NIS+ is controlling the group), it reports
that it could not. The warning message provides the necessary information to
manually make the changes.
These considerations hold true for any environment in which an external security
program does not allow the DB2 installation or instance creation programs to
modify user characteristics.
If the DB2 Setup wizard detects NIS on your computer, you are not given the
option of creating new users during the installation. Instead, you must choose
existing users.
Consider the following restrictions if you are using NIS or NIS+:
v Groups and users must be created on the NIS server before running the DB2
Setup wizard.
v Secondary groups must be created for the DB2 instance owner and the DB2
Administration Server on the NIS server. You must then add the primary group
of the instance owner to the secondary DB2 Administration Server group.
Likewise, you must add the primary DB2 Administration Server group to the
secondary group for the instance owner.
v On a partitioned DB2 database system, before you create an instance, there must
be an entry for the instance in the etc/services file. For example, if you want to
create an instance for the user db2inst1, you require an entry similar to the
following:
DB2_db2inst1 50000/tcp
Related tasks:
v “Installing DB2 servers (Linux)” on page 19
14 Getting started with DB2 installation and administration