DB2 10.5 for Linux, UNIX, and Windows
DB2 10.5 for Linux, UNIX, and Windows
When planning your DB2® server upgrade, there are a number of best practices to consider. Review these best practices before you start your upgrade.
Changes in existing functionality introduced in DB2 Version 10.5 can potentially impact your applications, scripts, maintenance processes, and any other aspects related your DB2 server upgrade process.
Upgrading in a test environment allows you to learn about possible issues, evaluate the impact on your environment and find a resolution.
The supported UNIX, Linux and Windows operating systems have changed in DB2 Version 10.5. Review the installation requirements for DB2 database products to determine whether your operating system version is supported and if you need to upgrade your operating system before installing DB2 Version 10.5. Newer versions of operating systems can also bring new hardware requirements.
Performing hardware and operating system upgrades separately from DB2 database product upgrade simplifies problem determination if you encounter upgrade difficulties. If you upgrade your software or hardware before a DB2 database product upgrade, ensure that your system is operating as expected before attempting to upgrade your DB2 database product.
If you have a DB2 Version 9.7 copy on SUSE Linux Enterprise Server 10, first apply DB2 Version 9.7 Fix Pack 2 or later, before you upgrade the operating system to SUSE Linux Enterprise Server 11.
Run a number of performance tests before upgrading your DB2 server. The db2batch benchmark tool helps you to collect elapsed and CPU times for running queries. You can use this tool to develop performance tests. Record the exact environment conditions where you run your tests.
Also, keep a record of the db2expln command output for each test query. Compare the results before and after upgrade. This practice can help to identify and correct any performance degradation that might occur.
There is no utility to reverse an upgrade or fall back from DB2 Version 10.5 to a pre-DB2 Version 10.5 release. See Reversing DB2 server upgrade to learn all the required steps to reverse a database upgrade.
There are several pre-upgrade tasks outlined in the Pre-upgrade tasks for DB2 servers topic that you should execute for a successful upgrade, such as backing up DB2 configuration parameters settings, ensure that you have enough disk free space for table spaces and log files, and verifying that databases are ready for upgrade.
Upgrading your DB2 servers before upgrading your data server clients is the traditional approach to avoid any known restrictions and limitations such as support of new DB2 database product functionality, network protocols, and connectivity. These restrictions and limitations are not associated with DB2 Connect™.
Upgrading your data server clients first requires that you manage any incompatibilities between releases. If you must upgrade your client due to a software requirement, make sure that the software supports the DB2 database product version that you are running on your DB2 server. In this case, the software manages any incompatibilities between releases. See Best practices for upgrading clients in the DB2 Version 10.5 documentation for details about incompatibilities. See DB2 client considerations for the IBM® DB2 pureScale® Feature for details about supported Version 9.8 functionality.
If you upgrade your DB2 server, you might also need to upgrade your database applications and routines to support changes for 64-bit instances, SQL stored procedures, Java™ Virtual Machine (JVM), and development software.
Review the factors that can impact your database application upgrade or routine upgrade and make any necessary changes to your database applications and routines to ensure that they run after the upgrade. See Upgrade essentials for database applications and Upgrade essentials for routines for details about the factors that can impact your database application upgrade or routine upgrade.
In an upgrade testing environment, you can test and verify that your database applications and routines run successfully in DB2 Version 10.5 to find out if you need to upgrade them. You can also upgrade your database applications and routines before you upgrade your production environment.
Upgrading a primary database to DB2 Version 10.5 changes the database role from primary to standard. Upgrading standby databases to DB2 Version 10.5 is not supported because these databases are in rollforward pending state. Because of these restrictions, upgrading an HADR environment to DB2 Version 10.5 requires that you stop HADR, upgrade your DB2 server where the primary database resides, and then reinitialize HADR.
Before you activate your standby database, you must move the log files from the previous version of DB2 out of the log path of the new version of DB2. If you do not move the log files, DB2 might try to use the old files and fail to initialize.
After upgrading your database servers, you can optionally migrate your SQL replication environment to DB2 Version 10.5.
See Migrating to SQL replication Version 10.5 for details about when to migrate and how to migrate your SQL replication environment.
If you had DB2 Spatial Extender installed and you upgraded your spatially enabled databases to DB2 Version 10.5, see Upgrading to DB2 Spatial Extender V10.5 for upgrade details specific to DB2 Spatial Extender.
In a Microsoft Cluster Server (MSCS) environment, install DB2 Version 10.5 as a new copy and then run the db2iupgrade command to upgrade the MSCS instance. See Upgrading DB2 servers in Microsoft Cluster Server environments for details.
Query Patroller is discontinued. See Migrating from Query Patroller to DB2 workload manager for details on how to migrate.