- 论坛徽章:
- 0
|
Share the following information with you, you can refer to it and you can get more understanding for DB2 profile.
*global.reg - global DB2 profile registry
Default Location: /var/db2
A global.reg configuration file, acts as a root configuration file for all DB2 installations on the machine. A UNIX system with only one database version installed does not have this file. My demonstration installation has installed DB2 versions 7 and 8, where the global.reg was located on the highest directory structure position. It is used as a general, system DB2 configuration file.
*profiles.reg - DB2 software version profile registry
Default Location: /var/db2/v81
The profiles.reg configuration file holds a list of all instance profiles running under the same DB2 software version. In the other words, a list of DB2 instances running the same code version. On a UNIX machine having only one DB2 software version installed, profiles.reg is used as the global profile registry file. The profiles.reg file becomes the second configuration file in the hierarchy on a machine with several installed DB2 versions, and is read accordingly--after the global.reg configuration file.
IBM has provided the db2set system command for displaying and changing the profiles.reg file content.
*default.env - global instance profile registry
Default Location: /var/db2/v81
The local instance profile holds certain important information related to the local instance settings, such as license information or default host name. Profile content is normally managed using the DB2 system command 'db2set -g'.
This profile is also called global, generating a misunderstanding to the overall perception of the IBM configuration. Even though the content handling is managed with db2set global command switch "-g", this setting represents real, local instance registry settings.
*profile.env - local instance profile registry
Default Location: $HOME/sqllib
This is a central DB2 configuration file. According to IBM, it is strongly recommended that all DB2-specific registry variables be defined through this registry file. The explanation lays in the remote administration of these variables over Control Center, which would not be possible if registry variables were defined elsewhere. Only the PATH and DB2INSTANCE variables should be defined outside of the DB2 local instance profile.
*userprofile - custom configuration profile
Default Location: $HOME/sqllib
Userprofile is a custom configuration file that is supposed to hold all non-standard db2profile variables. This file is of high importance during fix pack installations, because of the possibility that every new fix pack might clear all non-standard settings from db2profile. The db2profile file, by default, calls the userprofile after the DB2 environment is initialized.
*node_num.env - DB2 instance node level profile registry
Default Location: $HOME/sqllib/nodes
An SDP configured database system, with the DB2 database divided across different physical database partitions, has a node_num.env registry file on every database partition. My demo DB2 database ARTIST was running on only one physical machine and did not have a node-level profile registry file.
*db2profile - DB2 instance owner profile
Default Location: /opt/IBM/db2/V8.1 (template), $HOME/sqllib
The dB2profile is the most important DB2 configuration file. It is created automatically by the DB2 installation, and has all of the needed settings to activate DB2 software properly.
*db2nodes.cfg - partition configuration file
Default Location: $HOME/sqllib/
db2nodes.cfg is the DB2 ESE database partition (node) definition file. A standard, non-partitioned database instance does not use this configuration file.
Beginning with DB2 version 8, db2nodes.cfg is enhanced with the resourcename column. This new column provides the opportunity to direct one logical node to use a particular set of system resources. The new db2nodes.cfg file format has the following structure:
nodenum hostname logical port netname resourcename |
|
免费注册
发表于 2007-11-08 13:45
发表于 2007-11-09 11:25