IBM Data Server DB2 User Manual
Page 38
24
DB2 Deployment Guide
Configuration Assistant and Control Center are not available on non-root
installation.
Ability for the db2governor to increase priority is not supported.
Agent priority set by Work Load Manager (WLM) in a DB2 services class in a
non-root DB2 instance will not respected.
Automatic starting of non-root DB2 instances at system reboot is not
supported.
Sending alert notifications, running script or task action on alert occurrences
in Health monitor are not supported in non-root installation.
Only single-partition databases are supported in non-root installation (no
additional database partition can be added).
Non-root user can have only one copy of a DB2 product installed.
Non-root installation can have only one DB2 instance created during
installation (for non-root user ID). No other instances can be created
Root installation and non-root installations can coexist on the same computer
in different installation paths. However, DB2 instance action on non-root
instance can be performed only by the instance owner of non-root instance.
DB2 instance commands such as
db2icrt
,
db2iupdt
,
db2idrop
, and
db2imigr
are not available in non-root installation.
Root installed instance cannot be migrated to a non-root instance.
Operating system-based authentication, High Availability (HA) feature, ability
to reserve service name in the /etc/services file, ability to increase ulimit (in
AIX) are not available in non-root installation. However, these limitations can
be overcome by running the Enable root features for the non-root installation
command (
db2rfe
).
Further information can be found in the DB2 Information Center:
Requirements and limitations in Windows platforms
Here we provide the requirements for using non-root/non-Administrator
installation on Windows as well as the limitations of this installation method.
Note: As operating system-based authentication is the default authentication
type for DB2 products without running
db2rfe
, non-root user must manually
set the authentication type in database manager configuration (dbm cfg) file.