- Installing DB2 UDB Servers
- 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
Managing the DB2 Profile Registry
There are some values in the DB2 Profile Registry that are applied globally for the system, some that are applied across database partitions if the database is partitioned, and some that are applied only for a particular instance. The DB2 Profile Registry is divided into four registries:
DB2 instance-level Profile Registry— The majority of DB2 UDB registry variables are placed within this registry. The variable settings for a particular instance are kept in this registry.
DB2 global-level Profile Registry— If a variable is not set for a particular instance, this registry is used. This registry contains machine-wide variable settings.
DB2 instance node-level Profile Registry— In a system where the database is divided across different database partitions, this registry resides on every database partition.
DB2 instance Profile Registry— This registry contains a list of all instance names recognized by this system.