Quick Beginnings for DB2 Universal Database for UNIX

Updating Instances

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:

1. Replaces the files in the INSTHOME/sqllib directory, where INSTHOME is the home directory of the instance.

2. 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 HP-UX, SCO UnixWare 7, or Solaris

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 DB2 server is installed. Otherwise, the AuthType is set to (CLIENT).

Notes:

1. The authentication type of the instance applies to all databases owned by the instance.

2. While authentication type (DCE) is an optional parameter, it is not valid to choose (DCE) for this command.

-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.

-k

Is an optional parameter that preserves the current instance type. If you do not specify this parameter, the current instance will be upgraded to the highest instance type available in the following order:

• Partitioned database server with local and remote clients (DB2 Extended Enterprise Edition default instance type)

• Database Server with local and remote clients (DB2 Universal Database Enterprise Edition default instance type)

• Client (DB2 Client Application Enabler default instance type)

instance_name

Is the login name of the instance owner.

If a server product is installed, the syntax is:

   db2iupdt -u FencedID instance_name

Examples:

• If you installed DB2 Universal Database Workgroup Edition or DB2 Universal Database Enterprise Edition after the instance was created, enter the following command to update that instance:

     db2iupdt -u db2fenc1 db2inst1
  

• If you installed DB2 Connect Enterprise Edition after creating the instance, you can use following command to update that instance:

     db2iupdt -u db2inst1 db2inst1
  

• To update client instances, you can use the following command:

     db2iupdt db2inst1
  

The db2iupdt command updates the files in the INSTHOME/sqllib directory, where INSTHOME is the home directory of the instance owner.

[ DB2 List of Books | Search the DB2 Books ]