DB2 Version 9.7 for Linux, UNIX, and Windows

db2iupdt - Update instances command

Updates an instance to run on a DB2® copy that has a new DB2 database product or feature installed, to run on a DB2 copy of the same version as the DB2 copy associated with the instance, or to upgrade the instance type to a higher level instance type.

The db2iupdt command can be issued against instances of the same version that are associated with the same or a different DB2 copy. In all cases, it will update the instance so that it runs against the code located in the same DB2 copy as where you issued the db2iupdt command. You should issue this command if:

You install a fix pack and the automatic instance update fails.
You install a new DB2 database product or feature to the DB2 copy associated to the DB2 instance.
You want to update a DB2 instance from one DB2 copy to another DB2 copy of the same version of DB2 database product.

After a fix pack is installed on Linux and UNIX operating systems, the db2iupdt command is executed automatically.

To update an instance with db2iupdt, you must first stop all processes that are running for the instance.

Authorization

Root user authority on UNIX and Linux operating systems or Local Administrator on Windows operating systems.

Command syntax

For UNIX and Linux operating systems


>>-db2iupdt--+-----+--+-----+--+-----+--+-----+--+-----+-------->
             +- -h-+  '- -d-'  '- -k-'  '- -D-'  '- -s-'   
             '- -?-'                                       

>--+---------------+--+---------------+--+-InstName-+----------><
   '- -a--AuthType-'  '- -u--FencedID-'  '- -e------'

For Windows operating systems


>>-db2iupdt--InstName--/u:--username,password------------------->

>--+----------------------------+--+-----------------------+---->
   '-/p:--instance-profile-path-'  '-/r:--baseport,endport-'   

>--+---------------+--+----+--+----+--+---------------+--------->
   '-/h:--hostname-'  '-/s-'  '-/q-'  '-/a:--authType-'   

>--+-----------------------------------------------------+------>
   '-/j--"TEXT_SEARCH-+--------------+-+-------------+-"-'   
                      '-,servicename-' '-,portnumber-'       

>--+----+------------------------------------------------------><
   '-/?-'

Command parameters

For UNIX and Linux operating systems

-h | -?: Displays the usage information.
-d: Turns debug mode on.
-k: Keeps the current instance type during the update.
-D: Moves an instance from a higher code level on one path to a lower code level installed on another path.
-s: Ignores the existing SPM log directory.
-a AuthType: Specifies the authentication type (SERVER, SERVER_ENCRYPT or CLIENT) for the instance. The default is SERVER.
-u Fenced ID: Specifies the name of the user ID under which fenced user defined functions and fenced stored procedures will run. This option is only needed when converting an instance from a client instance to a non-client instance type. To determine the current instance type, refer to the node type parameter in the output from a GET DBM CFG command. If an instance is already a non-client instance, or if an instance is a client instance and is staying as a client instance (for example, by using the -k option), the -u option is not needed. The -u option can change the fenced user for an existing instance.
InstName: Specifies the name of the instance.
-e: Updates every instance.

For Windows operating systems

InstName

Specifies the name of the instance.

/u:username,password

Specifies the account name and password for the DB2 service.

/p:instance-profile-path

Specifies the new instance profile path for the updated instance.

/r:baseport,endport

Specifies the range of TCP/IP ports to be used by the partitioned database instance when running in MPP mode. When this option is specified, the services file on the local machine will be updated with the following entries:

DB2_InstName       baseport/tcp
DB2_InstName_END   endport/tcp

/h:hostname

Overrides the default TCP/IP host name if there are more than one TCP/IP host names for the current machine.

/s

Updates the instance to a partitioned instance.

/q

Issues the db2iupdt command in quiet mode.

/a:authType

Specifies authType, the authentication type (SERVER, CLIENT, or SERVER_ENCRYPT) for the instance.

/j "TEXT_SEARCH"

Configures the DB2 Text Search server using generated default values for service name and TCP/IP port number. This parameter cannot be used if the instance type is client.

/j "TEXT_SEARCH, servicename": Configures the DB2 Text Search server using the provided service name and an automatically generated port number. If the service name has a port number assigned in the services file, it uses the assigned port number.
/j "TEXT_SEARCH, servicename, portnumber": Configures the DB2 Text Search server using the provided service name and port number.
/j "TEXT_SEARCH, portnumber": Configures the DB2 Text Search server using a default service name and the provided port number. Valid port numbers must be within the 1024 - 65535 range.

/?

Displays usage information for the db2iupdt command.

Examples (UNIX and Linux)

An instance, db2inst2, is associated to a DB2 copy of DB2 database product installed at DB2DIR1. You have another DB2 copy of DB2 database product on the same computer at DB2DIR2 for the same version of the DB2 database product as that installed on DB2DIR1. To update the instance to run from the DB2 copy installed at DB2DIR1 to the DB2 copy installed at DB2DIR2, issue the following command:
```
DB2DIR2/instance/db2iupdt db2inst2
```
If the DB2 copy installed at DB2DIR2 is at level lower than the DB2 copy installed at DB2DIR1, issue:
```
DB2DIR2/instance/db2iupdt -D db2inst2
```

Usage notes

For all supported operating systems

If you use the db2iupdt command to update a DB2 instance from one DB2 copy to another DB2 copy of the same version of DB2 database product, the DB2 Global Profile Variables defined in an old DB2 copy installation path will not be updated over to the new installation location. The DB2 Instance Profile Variables specific to the instance will be carried over after the instance is updated.
For a partitioned database environment instance, after installing the fix pack on all the nodes, the instance update is only needed on the instance owning node.

For UNIX and Linux operating systems

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.
If you want to update a non-root instance, refer to the db2nrupdt non-root-installed instance update command. The db2iupdt does not support updating of non-root instances.
If you are using the su command instead of the login command to become the root user, you must issue the su command with the - option to indicate that the process environment is to be set as if you had logged in to the system using the login command.
You must not source the DB2 instance environment for the root user. Running db2iupdt when you sourced the DB2 instance environment is not supported.
On UNIX and Linux operating systems, if the IBM® Tivoli® Monitoring for Databases: DB2 Agent is installed and the DB2 instance is updated, the Monitoring Agent for DB2 instance is also created if the following are true:
- The DB2 instance type is standalone, wse, or ese.
- The DB2 instance is at version 9.5 (or higher).
In addition, ITMA must already be installed for the DB2 copy you are updating the instance. Located in DB2DIR/itma directory, where DB2DIR represents the directory where the DB2 database product is installed.
On AIX® 6.1 (or higher), when running this command from a shared DB2 copy in a system workload partition (WPAR) global environment, this command must be run as the root user.

For Windows operating systems

The db2iupdt command is located in the DB2PATH\bin directory, where DB2PATH is the location where the current version of the DB2 database product is installed.
The instance is updated to the DB2 copy from which you issue the db2iupdt command. However, to move your instance profile from its current location to another location, use the /p option and specify the instance profile path. Otherwise, the instance profile will stay in its original location after the instance update. Use the db2iupgrade command instead to upgrade to the current release from a previous release.
On Windows operating systems, if the IBM Tivoli Monitoring for Databases: DB2 Agent is installed and the DB2 copy instance is updated, the Monitoring Agent for DB2 instance is also created if the following are true:
- The DB2 instance type is standalone, wse, or ese.
- The default DB2 copy has the ITM agent component installed.
- The DB2 instance is at version 9.5 (or higher).
- There is no existing ITM for Databases product.
In addition, the following are also created after the creation of the Monitoring Agent for DB2 instance: the Monitoring Agent for DB2 instance files, the Windows service and the registry entries.