Upgrading partitioned database environments
requires that you install DB2® Version
9.7 as a new copy in all database partition servers, upgrade the instances
and then upgrade the databases.
About this task
Restrictions
Procedure
To upgrade DB2 servers
in a partitioned database environment:
- Perform a full offline backup for all database
partitions. In Version 9.5, use the BACKUP DATABASE command
with the ON ALL DBPARTITIONNUMS parameter to
back up all partitions. Verify that your databases are ready for upgrade,
and perform any other pre-upgrade
tasks that apply.
- Log on as root on Linux and UNIX operating systems or as a
user with Local Administrator authority on Windows operating systems.
- Install DB2 Version
9.7 on each participant database partition server and set up your
partitioned database environment.
Select the Install New option in the Install
a Product panel. Do not select the Work with
Existing option.
- Upgrade
each instance on the database partition server that owns the
instance. The first entry in the db2nodes.cfg file
of the instance is the database partition server instance owner.
- Upgrade each database by
running the UPGRADE DATABASE command on the catalog
partition. If any database partitions are not available, these database
partitions are not upgraded. Also, if the UPGRADE DATABASE command
is stopped, the remaining database partitions are not upgraded. However,
you can run the UPGRADE DATABASE command again
to process these particular database partitions afterward when they
are available.
The catalog partition must be available
when you issue the UPGRADE DATABASE regardless
on what database partition you issue this command from.
- Create a new DB2 Administration Server (DAS) on each database partition server. If you need to
keep your existing DAS settings, you can upgrade the DAS on each participating database
partition server instead of creating a new DAS.
What to do next
After upgrading the DB2 server,
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.