To successfully upgrade your DB2 Connect™ servers, preparation is required
to address any issues that may exist.
Perform the following pre-upgrade tasks for DB2® servers that also apply to DB2 Connect servers:
- Review the Upgrade essentials for DB2 Connect to
identify the changes or restrictions that can affect your upgrade
and learn how to address any issues prior to upgrading.
-
If the modification level of your product is higher than
10, install DB2 for z/OS® APAR PM35785 on your z/OS system before upgrading to
a new release or fix pack of DB2
Connect.
- Backing up DB2 server configuration and diagnostic information to
have a record of your current configuration that you can compare with
the configuration after the upgrade. You can also use this information
to create new instances or databases using the same configuration
that you had before upgrading.
- Optional: If you enabled the Syncpoint Manager (SPM) functionality
on your DB2 Connect server,
ensure that the DRDA® sync point
managers do not contain any indoubt transactions by using the LIST DRDA INDOUBT
TRANSACTIONS command to
get a list of indoubt transactions and to interactively resolve any
indoubt transactions.
- Optional: If you have transaction manager databases, perform
the following pre-upgrade tasks to prepare your databases for upgrading:
- Ensure that the database to be upgraded does not contain any indoubt
transactions by using the LIST INDOUBT TRANSACTIONS command to
get a list of indoubt transactions and to interactively resolve any
indoubt transactions.
- Verify that your databases are ready
for upgrading to
identify and resolve any problems before the actual upgrade.
- Backing up databases before upgrading to
be able to upgrade them to a new upgraded system or restore them in
the original pre-upgrade system.
- Review the disk space requirements to
ensure that you have enough free disk space, temporary table space
and log space for database upgrading and increase table space and log file sizes if
necessary.
- Linux only: Changing raw devices to block devices
(Linux)
- Optional: If you have DB2
Connect federated databases, refer to preparing to migrate to federated
systems for details
on pre-upgrade tasks for these databases.
- Windows only: If you
obtained customized code page conversion tables from the DB2 support service, you need to backup all of
the files in the DB2OLD\conv directory where
DB2OLD is the location of your existing DB2 Connect copy. Upgrading your current
version or release of DB2
Connect copy removes these tables because standard code page
tables are contained in a new version or release DB2 Connect library. You do not need
to backup standard code page conversion tables.
- Optional: Upgrade your DB2
Connect server in a test environment to identify upgrade issues
and to verify that database applications and routines work as expected
before upgrading your production environment.
- In the latest version or release of DB2 Connect, all significant upgrade
events are logged in the db2diag log files when
the diaglevel database manager configuration
parameter is set to 3 (default value) or higher.
If this parameter is set to 2 or less, set this parameter to 3 or higher before upgrading.
- Take the DB2 Connect server offline for upgrading
DB2 Version 9.7 for Linux, UNIX, and Windows