- 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
Environment Variables
Some environment variables may or may not be stored in the DB2 Profile Registry (depending on the OS). They are system environment variables used by DB2 UDB that must be stored in a location where the platform stores its system variables. The following are examples of DB2 UDB system environment variables:
DB2INSTANCE— Specifies the active DB2 instance.
DB2PATH— Specifies the path for the DB2 executables.
A summary of the location of these DB2 environment variables is shown in Table 2.1. For further details on environment variables and on which OS platforms you may see them or need them, refer to the section in the online documentation from the DB2 Information Center titled “System Environment Variables.”
Table 2.1. Location of DB2 Environment Variables
Operating System |
Location |
---|---|
Solaris (or other UNIX) |
Within a script file called db2profile (Bourne or Korn shell) or db2cshrc (C shell) depending on the default shell that is configured for the user. Incorporated with the user's initialization file (.profile or .login). |
Windows NT |
System Environment Variables, specifies the system within the System icon from the Control Panel. |