Upgrading non-root installations

Upgrading Db2® version 10.1, or earlier non-root installations to version 11.5 on Linux® and UNIX requires that you install version 11.5 as a non-root user and then upgrade your databases to the non-root installation.

Before you begin

Before upgrading a non-root installation:


  • You cannot upgrade a version 11.1 or version 10.5 root installation to a version 11.5 non-root installation.
  • You can upgrade databases from a version 10.5 root installation to a version 11.5 non-root installation by restoring database backups taken in the version 10.5 root installation. Use the same process described in Upgrading to a new Db2 server.
  • On Linux and UNIX operating systems except for Linux on x86, your existing 32-bit or 64-bit instances are upgraded to Db2 version 11.5 64-bit instances. The operating system and Db2 version 11.5 database product that you installed determines the instance bit size, see Support changes for 32-bit and 64-bit Db2 servers for details.
  • Additional upgrade restrictions apply. Review the complete list in Upgrade restrictions for Db2 servers.


To upgrade a non-root installation to Db2 version 11.5:

  1. Log on to the Db2 server as the non-root user or owner for the version 11.1 or version 10.5 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 11.5 as a non-root user and select the upgrade option during installation..

    The upgrade option backs up the version 11.1 or version 10.5 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 version 11.1 or version 10.5 is removed.

    The Db2 product installation also verifies the following conditions:
    • The directory INSTHOME/sqllib_v111 or INSTHOME/sqllib_v105 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.
  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 10.5 installed and then install version 11.5 using the db2setup command, you can find the name of the backup directory as sqllib_v105 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.
  8. Enable root-based features by running the db2rfe command.
  9. If you had additional Db2 products installed in your version 11.1 or version 10.5 non-root copy, install one Db2 product at a time.

What to do next

After upgrading the non-root installation, perform the recommended post-upgrade tasks such as resetting the diagnostic error level, adjusting log space size, and rebinding packages. In addition, verify that the upgrade of your Db2 server was successful. See Post-upgrade tasks for Db2 servers and Verifying upgrade of Db2 servers.