DB2 Version 9.7 for Linux, UNIX, and Windows

Post-upgrade tasks for DB2 servers

After upgrading your DB2® servers, you should perform several post-upgrade tasks to ensure that your DB2 servers perform as expected and at their optimum level.

Procedure

Perform the following post-upgrade tasks that apply to your DB2 server:

If you set the diaglevel database manager configuration parameter to 3 or higher as recommended in the pre-upgrade tasks for DB2 servers, reset this parameter to the value set before the upgrade.
Adjust the log space size. If you changed your log space setting as recommended in the pre-upgrade tasks for DB2 servers, reset the logfilsiz, logprimary, and logsecond database configuration parameters to their pre-upgrade values. Ensure that the amount of log space that you allocate is adequate for your DB2 server.
Ensure that existing libraries for your external routines remain on the original location prior to the upgrade, if necessary, restore these libraries from the backup that you perform in Backing up DB2 server configuration and diagnostic information.
Activate your database after upgrade to start your database and all necessary database services.
Manage changes in DB2 server behavior. There are new registry variables, new configuration parameters, and new default values for registry variables and configuration parameters introduced in DB2 Version 9.7 that can impact the behavior of DB2 server. There are also changes in physical design characteristics of databases and changes to security that also have an impact.
Set up security to manage database audit in upgraded databases. If you enabled the audit facility in your upgraded databases, grant security administrator (SECADM) authority to allow users to configure and manage database audit using DDL statements.
If the automatic collection of statistics failed on certain system catalog tables during database upgrade, update the statistics on those system catalog tables.
Rebind packages in upgraded databases to validate packages and to use updated statistics or new index information.
Migrate DB2 explain tables to retain explain table information that you previously gathered.
If you have tables with XML columns that you created in a pre-Version 9.7 release, convert the XML storage object to the Version 9.7 format by recreating these tables to have access to new functions such as compression on XML data and collection of statistics to estimate the inline length for XML columns.
Ensure that you meet system temporary table spaces page sizes requirements to accommodate the largest row size in your result sets from queries or positioned updates, and create a system temporary table space with a larger page size if necessary.
If you obtained customized code page conversion tables from the DB2 support service, copy all of the files for those tables from the DB2OLD/conv to DB2DIR/conv, where DB2OLD is the location of your DB2 Version 9.1 or DB2 UDB Version 8 copy and DB2DIR is the location of your DB2 Version 9.7 copy. You do not have to copy standard code page conversion tables.
If you upgraded your existing DB2 Version 9.1 or DB2 UDB Version 8 copy on Windows operating systems, you can restore the customized code page conversion tables that you backed up as part of the pre-upgrade tasks for DB2 servers to the DB2PATH\conv directory, where DB2PATH is the location of your DB2 Version 9.7 copy.
If you created write-to-table event monitors in DB2 Version 9.1 or DB2 UDB Version 8, recreate your write-to-table event monitors so that you can successfully activate these monitors after you upgrade to DB2 Version 9.7.
Verify that your DB2 server upgrade was successful. Test your applications and tools to ensure that the DB2 server is working as expected. See Verifying upgrade of DB2 servers for details.
Back up your databases after the DB2 server upgrade is complete.
If you have recoverable databases, the UPGRADE DATABASE command renamed all log files in the active log path using the .MIG extension. After verifying the database upgrade was successful and backing up your databases, you can delete the S*.MIG files that are located in the active log path.

What to do next

Perform the following post-upgrade tasks that apply to your DB2 database products or add-on features:

If you upgrade a DB2 server running high availability disaster recovery (HADR) replication, initialize HADR replication During upgrade to DB2 Version 9.7 in a high availability disaster recovery (HADR) replication environment, a database role is changed from primary to standard. Upgrade of standby databases is not supported because these databases are in roll forward pending state.
If you are using index extensions or spatial indexes and you upgraded from a DB2 UDB Version 8 32-bit instance to a DB2 Version 9.7 64-bit instance, recreate your index extensions or spatial indexes. If you are a Spatial Extender user, review the upgrading the Spatial Extender environment task for details on how to recreate your spatial indexes. The DB2 Spatial Extender and Geodetic Data Management Feature User's Guide and Reference is available by at http://www.ibm.com/software/data/spatial/db2spatial/library.html.
If you revoked privileges from PUBLIC for any catalog views before upgrading, they will have been granted back during the upgrade process. You should decide if you need to revoke privileges from the catalog views again.

When your DB2 server performance is stable, take advantage of optimizer improvements and collect statistics for new functionality by updating statistics for your upgraded databases. During database upgrade to DB2 Version 9.7, the statistics collected from your existing database tables retain their values. Statistics for new characteristics on tables and indexes have a value of -1 to indicate there is no information gathered. However, you only need these statistics if you are using new functionality.

After updating statistics for your upgraded databases, determine if index or table reorganization is necessary by running the REORGCHK command. Table and index reorganization can help you to improve performance.

At this point, you should resume all of your maintenance activities such as backing up databases and updating statistics. You should also remove any DB2 Version 9.1 or DB2 UDB Version 8 copies that you no longer need.