Quick Beginnings for DB2 Extended Enterprise Edition for UNIX
Existing instances are designed to be as independent as
possible from the effects of subsequent installation and removal of
products.
In most cases, existing instances automatically inherit or lose access to
the function of the product being installed or removed. However, if
certain executables or components are installed or removed, existing instances
do not automatically inherit the new system configuration parameters or gain
access to all the additional function. The instance must be
updated.
If DB2 is updated by installing a PTF or a patch, all the existing DB2
instances should be updated using the db2iupdt command. You
should also update the Administration Server using the dasiupdt
command. See "Updating the Administration Server" for further information.
Running the db2iupdt command updates the specified instance by
performing the following:
- Replaces the files in the INSTHOME/sqllib directory, where
INSTHOME is the home directory of the instance.
- If the node type is changed, then a new database manager configuration
file is created. This is done by merging relevant values from the
existing database manager configuration file with the default database manager
configuration file for the new node type. If a new database manager
configuration file is created the old file is backed up to:
INSTHOME/sqllib/backup/db2systm.old
The db2iupdt command is available in the
DB2DIR/instance directory,
| where DB2DIR
| = /usr/lpp/db2_05_00
| on AIX
|
|
| = /opt/IBMdb2/V5.0
| on Solaris
|

|
Because INSTHOME is mounted, you only have to run the
db2iupdt command once to update the instance.
|
The syntax of the db2iupdt command is:

where:
- -h | -?
- Displays a help menu for this command.
- -d
- Sets the debug mode, which you can use for problem analysis.
- -a AuthType
- Is an optional parameter that specifies the authentication type for the
instance. Valid authentication types are SERVER, CLIENT, and
DCS. If the -a parameter is not specified, the authentication
type defaults to SERVER, if a server product is installed. Otherwise,
the AuthType is set to CLIENT.
Notes:
- The authentication type of the instance applies to all databases that are
owned by the instance.
- The authentication type DCE is valid. However, it is not valid to
choose DCE as an AuthType for this command. To enable DCE
authentication for an instance, refer to the Administration
Guide.
- -u FencedID
- Is the user under which the fenced UDFs and stored procedures will
run. This is not required if you install the DB2 Software
Developer's Kit or the DB2 Client Application Enabler. For other
products, this is a required parameter.
Note: | FencedID may not be root or bin.
|
- InstName
- Is the login name of the instance owner.
If a server product is installed, the syntax is:
db2iupdt -u FencedID InstName
Examples:
The db2iupdt command updates the files in the
INSTHOME/sqllib directory, where INSTHOME is the home
directory of the instance owner.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]