Upgrading non-root installations

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

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

1. Log on to the DB2 server as the non-root user for the DB2 Version 9.5, 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.1 as a non-root user and select the upgrade option..

   The upgrade option backs up the DB2 Version 9.5, 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 9.5, DB2 Version 9.7, or DB2 Version 9.8 copy is removed.

   The DB2 product installation also verifies the following conditions:

   • The directory INSTHOME/sqllib_v101 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 re-issue the db2setup command specifying the response file or 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.

   If any of the local databases running under the non-root instance have type-1 indexes, a message box appears giving you the option to continue the installation and ignore this warning or exit the installation. See step 7 in Verifying that your databases are ready for upgrade for details about what happens when you choose to ignore the warning and how to convert type-1 indexes before upgrade. You must specify the UPGRADE_DBCK_IGNORE_TYPE1 keyword with the YES option in the response file or specify the -f ignoreType1 parameter with the db2_install command so that the installer does not check for type-1 indexes and completes processing successfully.

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.1 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 9.5 or DB2 Version 9.7 non-root copy, install one DB2 product at a time.