DB2 Version 9.7 for Linux, UNIX, and Windows

Updating the instance configuration (Linux, UNIX)

To update the configuration for root instances on Linux or UNIX operating systems, use the db2iupdt command. To update non-root instances, run the db2nrupdt command.

About this task

This topic applies to root instances only.

Running the db2iupdt command updates the specified instance by performing the following:

Replaces the files in the sqllib subdirectory under the instance owner's home directory.
If the node type has 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 the backup subdirectory of the sqllib subdirectory under the instance owner's home directory.

The db2iupdt command is located in the DB2DIR/instance directory, where DB2DIR is the location where the current version of the DB2 database product is installed.

To update an instance using the command line, enter:

  db2iupdt InstName

The InstName is the login name of the instance owner.

There are other optional parameters associated with this command:

-h or -?: Displays a help menu for this command.

-d: Sets the debug mode for use during problem determination.

-a AuthType: Specifies the authentication type for the instance. Valid authentication types are SERVER, SERVER_ENCRYPT, or CLIENT. If not specified, the default is SERVER, if a DB2® server is installed. Otherwise, it is set to CLIENT. The authentication type of the instance applies to all databases owned by the instance.

-e: Allows you to update each instance that exists. Use db2ilist to list the existing instances.

-u Fenced ID: Names the user under which the fenced user-defined functions (UDFs) and stored procedures will execute. This is not required if you install the Data Server Client or the DB2 Software Developer's Kit. For other DB2 products, this is a required parameter. Note: Fenced ID might not be "root" or "bin".

-k

This parameter preserves the current instance type. If you do not specify this parameter, the current instance is upgraded to the highest instance type available in the following order:

Partitioned database server with local and remote clients
Database Server with local and remote clients
Client

Examples:

If you installed DB2 Workgroup Server Edition or DB2 Enterprise Server Edition after the instance was created, enter the following command to update that instance:
```
    db2iupdt -u db2fenc1 db2inst1
```
If you installed the DB2 Connect™ Enterprise Edition after creating the instance, you can use the instance name as the Fenced ID also:
```
    db2iupdt -u db2inst1 db2inst1
```
To update client instances, invoke the following command:
```
    db2iupdt db2inst1
```