Introduction to the DB2 user group in Linux

In Linux and UNIX operating systems, installing and operating DB2 UDB usually requires several DB2 users and DB2 user groups for your reference:

1. Installation User Account

2. DB2 Administration ServerDAS) User Account

3. DB2 UDB instance owner User Account

4. DB2 UDBfenced routine User Account

By default, the DB2 Installation wizard automatically creates these users and group accounts during the installation of the DB2 UDB server. You can also specify an existing user account during the installation process.

Installation User Account:

You must use the "root" account to install DB2 UDB. This is the only account with sufficient permissions for installation.

User Account of the Instance owner:

Create a DB2 UDB instance in the instance owner's home directory. This user account controls all DB2 UDB processes and owns all the file systems and devices used by the databases contained in this instance. During the DB2 UDB installation process, the default user ID used by the DB2 UDB instance owner is db2inst1 and the default group is db2iadm1. If the user name already exists, the DB2 Installation Wizard will add a 1-99 number after the default name until a user ID does not exist.

A good way is to restrict the instance owner user account to the instance owner group and not include it in any other group. This helps control the number of user accounts and groups that can modify any objects in an instance or instance.

DB2 Administration Server user account:

DB2 Administration ServerDAS) user accounts are used to run the DAS process on the system. The Default User ID created during installation is dasusr1, and the default group is dasadm1. The DB2 UDBGUI tool also uses the DAS account to manage local server instances and databases. Only one DAS is needed on each machine. It can manage all instances defined on the server. The DAS user account must be different from the instance owner user account.

Once you use this account to start the DAS process, you must also use this account to stop. Therefore, on Linux or UNIX, you must use the su-command to switch to the DAS user account to start and end the DAS process.

Fenced User Account:

Fenced user accounts are used to run user-defined functions (udfs) and stored procedures outside the address space memory used by the DB2 UDB engine. Sometimes, if a process or function is unstable or in testing, it should be defined as FENCED so that it can be run in its own process address space. In this way, if the function or process crashes or terminates abnormally, it will not affect other instance processes. The default user account created for the fenced user is db2fenc1, and the default group is db2fadm1. For security reasons, we recommend that you do not use the instance owner account as the fenced user account. If you do not need this level of security, such as running in a test environment, or are not ready to use fencedUDF or stored procedure, you can directly use the instance owner account without creating other user accounts. When creating a new instance, you must specify the fenced user account db2icrt...-u In the instance creation command ).
 

Top 10 considerations for DB2 Performance Optimization

Connect SQL SERVER to the DB2 database

Learn about the DB2 Index Structure

Provides you with an in-depth understanding of the DB2 materialized query table.

Rollback of A DB2 partitioned Database