Upgrading non-root installations

Upgrading DB2® Version 10.1, or DB2 Version 9.7 non-root installations to DB2 Version 10.5 on Linux and UNIX requires that you install DB2 Version 10.5 as a non-root user and then upgrade your databases to the DB2 Version 10.5 non-root installation.

To upgrade a non-root installation to DB2 Version 10.5:

1. Log on to the DB2 server as the non-root user or owner for the DB2 Version 10.1 or DB2 Version 9.7 non-root installation.
2. Review Table 1 to determine the instance type using the nodetype and the DB2 database product to which you can upgrade the non-root instance.

   The DB2 database product installation verifies that you can upgrade the non-root instance to the DB2 database product that you select for installation. If this verification fails, the installation fails and you can only end the installation.

3. Stop the non-root DB2 instance.
4. Install DB2 Version 10.5 as a non-root user and select the upgrade option during installation..

   The upgrade option backs up the DB2 Version 10.1 or DB2 Version 9.7 non-root configuration files, installation directory, installs a new DB2 copy, and upgrades the non-root instance. However, the installation directory is not backed up if you specify the -f nobackup parameter and the DB2 Version 10.1 or DB2 Version 9.7 copy is removed.

   The DB2 product installation also verifies the following conditions:

   • The directory INSTHOME/sqllib_v101 or INSTHOME/sqllib_v97 does not exist.
   • The non-root instance is stopped.
   • The local databases running under the non-root instance are ready for upgrade.
   If any of these verifications fail and:

   • You are running the db2setup command, a message box appears indicating the condition that failed. Take the appropriate corrective action and then select the upgrade option and continue.
   • You are using a response file or running the db2_install command, the installer will exit with error. Take the appropriate corrective action and then reissue the db2setup command specifying the response file or reissue the db2_install command.

   Important: The command db2_install is deprecated and might be removed in a future release. Use the db2setup command with a response file instead.
5. If the DB2 database product installation fails and you specified the -f nobackup parameter, manually install the DB2 database product and then run the db2nrupgrade command to upgrade the non-root instance as follows:

   cd $HOME/sqllib/instance
   db2nrupgrade -b BackupDir

   Where BackupDir is the backup directory for the configuration files of the non-root installation before upgrade. The backup directory is in the db2setup log in the format of sqllib_vVR where V is the version number and R is the release number of the old copy. For example, if you have Version 9.7 installed and then install Version 10.5 using the db2setup command, you can find the name of the backup directory as sqllib_v101 in the db2setup log file.
6. If the DB2 database product installation fails, review the installation log file to determine the cause and how to resolve the issue before attempting the installation again. By default, the installation log file is located in the /tmp directory.
7. Upgrade databases. See Upgrading databases.
8. Enable root-based features by running the db2rfe command.
9. If you had additional DB2 products installed in your DB2 Version 10.1 or DB2 Version 9.7 non-root copy, install one DB2 product at a time.