The DB2 Instance Profile Registry

All these registry profile variables can be set using the

db2set 

command. 

Example 8 5 shows different modes in which the 

db2set

 command can be used.

Example 8 5   Changing registry and environment variables using db2set

bash>db2set  all   this shows the current registry variables

[i] DB2COMM=tcpip

[i] DB2AUTOSTART=YES

[g] DB2SYSTEM=lochnessr1a

[g] DB2ADMINSERVER=dasusr1

bash>db2set DB2AUTOSTART=NO  i db2inst1   this sets registry for all 

databases in particular instance

bash>db2set DB2AUTOSTART=NO  g   this sets registry variable for all 

instances

bash>db2set DB2AUTOSTART=NO  i db2inst1 65000   this sets registry variable 

for particular node

DB2 UDB configures the operating environment by checking for registry values 

and environment variables, and resolving them in the following order:

1. Environment variables set using the 

export 

command

2. Registry values set with the instance node level profile using 

db2set  i 

instname nodenum

3. Registry values set with the instance level profile using 

db2set  i

4. Registry values set with the global level profile using 

db2set  g

Configuration files

In addition to DB2 Profile Registry, DB2 UDB also has instance and database 

configuration files, which provide users the flexibility to configure the database 

and the database engine to fit business and application needs. These files are 

created when the DB2 instance or database is created. They contain the 

parameters that define values such as resource allocated to DB2 UDB, 

diagnostic level, log files location, etc. As shown in Figure 8 7, there are two DB2 

configuration files and additional operating system configurations.

 Chapter 8. Database administration 

251