db2updv115 - Update database to version 11.5 mod pack or fix pack command

Authorization

SYSADM

Required connection

Database. The command automatically establishes a connection to the specified database.

Command syntax

Command parameters

-d database name

Specifies the name of the database to be updated.

-u userid

Specifies the user ID.

-p password

Specifies the password for the user.

-a

Forces all updates to be run.

Note: You can use the -a parameter to reset privileges on system views and routines. Before doing so, run the db2look utility to preserve privileges that have a dependency on system views and routines.

-o

Enables Oracle data dictionary-compatible views

-h

Displays help information. When this option is specified, all other options are ignored, and only the help information is displayed.

Usage notes

Before issuing the db2updv115 command, you must commit the fix pack or mod pack update. Committing the fix pack or mod pack update puts the instance in a homogeneous state. If the fix pack or mod pack update is not committed, issuing the db2updv115 command returns an error because the instance is in heterogeneous state.

The instance must be in homogeneous state before issuing the db2updv115 command. If the instance is in heterogeneous state, issuing this command returns an error.

For more details, see Database and instance operations affected by an online fix pack update in progress.

In a partitioned database environment, you must run this command from the catalog partition.

For improved performance, the db2updv115 command only apply updates that are required in order to make the databases appear as if they were created at the fix pack or mod pack level that you are installing. Thus, if the command is issued more than once, no errors are reported and each of the system catalog updates is applied only once. However, if you wish to forcefully reapply all of the updates, you may do so by appending the -a parameter.