DB2 Version 9.7 for Linux, UNIX, and Windows

Upgrade restrictions for DB2 servers

Before you start to upgrade your DB2® server, you must understand what the support for upgrade is and what the restrictions are.

What is supported?

Upgrading to DB2 Version 9.7 is supported from DB2 Version 9.5, DB2 Version 9.1, and DB2 UDB Version 8. If you have DB2 UDB Version 7 or earlier, you must upgrade to DB2 UDB Version 8.2 before upgrading to DB2 Version 9.7.
Upgrading to a DB2 Version 9.7 non-root installation is supported from a DB2 Version 9.5 non-root installation. Upgrading to a DB2 Version 9.7 non-root installation from a pre-Version 9.7 root installation is not supported.
On Windows operating systems, the upgrade action shows for existing DB2 copies that can be upgraded during the installation of DB2 Version 9.7. This action automatically installs DB2 Version 9.7 and upgrades all of your instances and your DB2 Administration Server (DAS) running on the DB2 copy. This action also uninstalls the DB2 copy and any add-on products installed in this copy. If you do not choose the upgrade action, you must manually upgrade your instances and your DAS after installation.
On Linux and UNIX operating systems, the upgrade action is not available and you can only install a new copy of DB2 Version 9.7. You have to manually upgrade your instances after installation. You can manually upgrade your existing DAS.
Instance bit size is determined by the operating system where DB2 Version 9.7 is installed, and support for 32-bit kernels and 64-bit kernels has changed.
Upgrading from a system with multiple DB2 copies of DB2 Version 9.5, DB2 Version 9.1, DB2 UDB Version 8, or all levels is supported. On Windows operating systems, you must be aware of the restrictions on coexistence of previous versions of the DB2 database products.
Upgrading from a partitioned database environment with multiple database partitions is supported.
Restoring full database offline backups from pre-Version 9.7 DB2 copies is supported. However, rolling forward of logs from a previous level is not possible. Review Backup and restore operations between different operating systems and hardware platforms for complete details about upgrade support using the RESTORE DATABASE command.
When the DB2 Workload Manager feature is installed and you are upgrading from DB2 Version 9.1 or DB2 UDB Version 8, an upgraded database has three predefined default service classes: the default user class, the default maintenance class, and the default system class. After database upgrade, all connections belong to the default workload. Connections that belong to the default workload are mapped to the default user class. The default user class has only one service subclass: the default subclass. All activities from the connections in the default user class run in the default subclass.
In upgraded databases with the RESTRICT_ACCESS database configuration parameter set to YES, you must grant the USAGE privilege to non-DBADM users on SYSDEFAULTUSERWORKLOAD. Otherwise, these users are unable to submit any work to the database.
Index extensions are upgraded as part of the database upgrade. However, you might have to re-create your indexes if you upgraded from a DB2 UDB Version 8 32-bit instance to a DB2 Version 9.7 64-bit instance. Review the post-upgrade tasks for details.

What is unsupported?

DB2 Version 9.7 installation fails if the following situations exist:

The operating system is not supported. You must upgrade to a supported version of the operating system before you upgrade to DB2 Version 9.7 or upgrade to a new DB2 server that meets the operating system requirements.
A 32-bit kernel is running on Linux and UNIX operating systems except for Linux on x86. A 64-bit kernel must be installed prior to installing DB2 Version 9.7.
A copy of DB2 UDB Version 7 or earlier is installed on Windows operating systems.

The db2iupgrade command fails if the following situations exist:

You do not have authorization to upgrade the instance.
The instance that you are trying to upgrade is active. Run the db2stop command to stop the instance.
The instance is already at DB2 Version 9.7 or later. Run the db2iupdt command to update to a different fix pack levels or copies of DB2 Version 9.7.
You try to upgrade from DB2 Version 9.7 back to DB2 Version 9.5, DB2 Version 9.1, or DB2 UDB Version 8. Reversing DB2 server upgrade is possible, however, you must follow the prerequisites and steps in this procedure.

The type of instance that you are trying to upgrade to the DB2 Version 9.7 copy is unsupported. The following table describes the upgrade support for each type of instance by DB2 database product:

Table 1. Instance upgrade support for DB2 Version 9.7 database products
Instance type	Node type	Upgrade support
client - default type for DB2 clients ¹	Client	Upgrade to a client, a standalone, a wse, or an ese instance is supported.
standalone - default type for DB2 Personal Edition (PE)	Database server with local clients	Upgrade to a standalone, a wse, or an ese instance is supported. Upgrade to a client instance is unsupported.
wse - default type for DB2 Workgroup Server Edition (WSE)	Database server with local and remote clients	Upgrade to a wse or an ese instance is supported. Upgrade to a standalone instance creates a standalone instance² (Linux and UNIX only) Upgrade to a client instance is unsupported.
ese - default type for DB2 Enterprise Server Edition (ESE)	Partitioned database server with local and remote clients or Enterprise Server Edition with local and remote clients	Upgrade to an ese instance is supported. Upgrade to a standalone or a wse instance from single database partition environments creates a standalone or wse instance²(Linux and UNIX only) Upgrade to a client instance is unsupported.

Note:

The highest level for each DB2 database product is the default instance type as indicated in Table 1 ordered from lower to higher-level. Each instance type supports instance types of a lower-level. For example, the ese instance type supports wse, standalone, and client. You can use the db2icrt command with the -s parameter to create instances of a lower-level. If you do not specify the -s parameter, the instance is created using the highest level of instance type supported by the DB2 database product installed.
Database manager configuration parameters have default values for the created instance. Previous database manager configuration settings are not retained. If the configuration parameters are available in the new instance, after upgrade, you can restore previous settings. The db2iupdt command does not support downgrading from a higher-level instance type to a lower-level instance type. You can downgrade the instance type manually but avoid doing so if possible.

The db2ckupgrade command fails and causes the db2iupgrade command to fail. The db2iupgrade command calls the db2ckupgrade command to verify whether cataloged local databases are ready for upgrade to DB2 Version 9.7.
DB2 Data Links Manager Version 8 is installed on the DB2 server. DB2 Data Links Manager is unsupported in DB2 Version 9.7. You can upgrade to a standard DB2 Version 9.7 instance without the DB2 Data Links Manager functionality.
DB2 Data Warehouse Manager Version 8 and any extensions are installed on the DB2 server. DB2 Data Warehouse Manager is unsupported in DB2 Version 9.7. However, when you run the db2iupgrade command, the error message that is generated includes instructions on how to upgrade to a standard DB2 Version 9.7 instance without the DB2 Data Warehouse Manager functionality.

The UPGRADE DATABASE command fails if the following situations exist:

You do not have authorization to upgrade the database.
A cataloged database does not exist.
Database upgrade encounters any of the problems described in the reason codes of error message SQL1704N.
User-defined distinct types (UDTs) are encountered with the names ARRAY, BINARY, CURSOR, DECFLOAT, ROW, VARBINARY, or XML. You must drop these UDTs and re-create them with different names before database upgrade.
Database objects were created using restricted schema names described in the error message SQL0553N. The list of restricted schema names now includes SYSPUBLIC.
User objects use the system-defined DATALINK data type. You must drop or alter these objects before database upgrade. Also, if you installed DB2 Net Search Extender (NSE) on your DB2 server, you must drop the UDFs created by NSE for Data Links support. Refer to Upgrading DB2 Data Links Manager environments for details.
A database enabled as a high availability disaster recovery (HADR) standby database.