Upgrading DB2® Version
9.5 non-root installations to DB2 Version
9.7 on Linux and UNIX requires that you install DB2 Version 9.7 as a non-root user and then upgrade
your databases to the Version 9.7 non-root installation.
Before you begin
Before upgrading a non-root installation:
Restrictions
- You cannot upgrade a DB2 Version
9.5 root installation to a DB2 Version
9.7 non-root installation. You can upgrade databases from a DB2 Version 9.5 root installation
to a DB2 Version 9.7 non-root
installation by restoring database backups taken in the DB2 Version 9.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
9.7 64-bit instances. The operating system and DB2 Version 9.7 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.
Procedure
To upgrade a non-root installation to DB2 Version 9.7:
- Log on to the DB2 server
as the non-root user for the DB2 Version
9.5 non-root installation.
- 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.
- Stop the non-root DB2 instance.
- Install DB2 Version 9.7 as a non-root user and
select the upgrade option.
The upgrade option backs up the DB2 Version 9.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 9.5
copy is removed.
The DB2 product
installation also verifies the following conditions:
- The directory INSTHOME/sqllib_v95 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.
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.
- 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 V9.5 installed and then
install V9.7 using the db2setup command, you can
find the name of the backup directory as sqllib_v95 in
the db2setup log file.
- 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.
- Upgrade
databases.
- Enable
root-based features by running the db2rfe command.
- If you had additional DB2 products
installed in your Version 9.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.