- Installing DB2 UDB Servers
- Prerequisites
- Before You Begin
- Installing DB2 UDB
- Installed Directory Structure
- Considerations in an NIS Environment
- Distributed Installation
- Sample Response Files
- Creating a Response File
- Distributed Installation with a Response File
- Installing DB2 with db2_install
- DB2 UDB Environment Definitions
- DB2 Profile Registry
- Managing the DB2 Profile Registry
- The db2set Command
- Environment Variables
- Hierarchy of the DB2 UDB Environment
- DB2 Administration Server (DAS)
- DAS Process
- DB2 Instances
- Creating the Sample Database
- Using the Command Line Processor (CLP)
- Uninstalling DB2 Products
- Stopping the DAS Instance
- Stopping All DB2 Instances
- Removing the DAS Instance
- Removing DB2 Instances
- Removing DB2 Products
Hierarchy of the DB2 UDB Environment
Since there are multiple places where a variable can be set, DB2 UDB uses a hierarchy to determine where it will look to determine a variable's value. It uses the following search order:
-
The session's environment variables
-
DB2 Profile Registry variables set in the instance node-level profile
-
DB2 Profile Registry variables set using db2set for the session
-
DB2 Profile Registry variables set at the instance level using the -i option of db2set
-
DB2 Profile Registry variables set at the global level using the -g option of the db2set command
Although most DB2 UDB environment settings can be set either in the DB2 Profile Registry or in the OS environment, it is strongly recommended that the DB2 Profile Registry be used whenever possible.