IBM DB2 manual Requirements and limitations on Linux and Unix platforms, Limitations

The non-root/non-Administrator might not be ideal for all because it poses some limitations. Before planning to deploy the DB2 product as a non-root/ non-Administrator user, restrictions and requirements associated with non-root/ non-Administrator installation should be fully considered.

Requirements and limitations on Linux and UNIX platforms

Here we provide the requirements for using non-root/non-administrator installation on Linux and UNIX platforms as well as the limitations of this installation method.

Requirements

These are the requirements of non-root/non-Administrator installation:

￿Non-root user ID must be able to mount the installation DVD. or have it mounted for you.

￿Non-root user ID is a valid user id that can be used as the owner of a DB2 instance.

￿Non-root user ID must have a primary group other than guests, admins, users, and local.

￿Non-root user ID cannot be longer than eight characters.

￿Non-root user ID cannot begin with IBM, SYS, SQL or a number non-root user ID cannot be DB2 reserved word (USERS, ADMINS, GUESTS,PUBLIC, or LOCAL) or an SQL reserved word.

￿Non-root user ID cannot include accented characters.

￿Non-root user’s home directory path must conform to DB2 installation path rule:

–Cannot exceed 128 characters

–Cannot contain spaces

–Cannot contain non-English characters

￿On AIX Version 5.3, Asynchronous I/O (AIO) must be enabled.

Limitations

These are the limitations of non-root/non-Administrator installation:

￿Non-root installation of IBM Data Studio, DB2 Embedded Application Server (DB2 EAS), DB2 Query Patroller, DB2 Net Search Extender and locally installed DB2 Information Center is not supported.

￿The DB2 Administration Server (DAS) and its associated commands, dascrt, dasdrop, daslist, dasmigr, and dasupdt are not available on non-root installation.

Chapter 1. Introduction to DB2 deployment 23