Upgrading partitioned database environments requires that
you install Db2® version 11.5 as a new copy in all database partition servers, upgrade
the instances and then upgrade the databases.
Before you begin
Restrictions
- The database partition server where the catalog partition resides
must be up and running.
- Use only the Install New option
in the Install a Product panel to install Db2 version 11.5. If you choose the upgrade action
when you select the Work with Existing option
on the Install a Product panel, the installation
process fails.
- Additional upgrade restrictions apply. Review the complete
list.
Procedure
To upgrade Db2 servers in a
partitioned database environment:
- Perform a full offline backup for all database partitions.
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. Refer to
Pre-upgrade tasks for Db2 servers.
Note: Although database upgrade is a recoverable
operation, for partitioned database environments recovery through
migration is not supported. So ensure a full offline backup for all
database partitions exists before proceeding.
- 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 11.5 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.
The catalog partition must be available when you issue the UPGRADE
DATABASE regardless on what database partition you issue
this command from.
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.
-
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.