DB2 Version 9.7 for Linux, UNIX, and Windows

Managing DB2 server behavior changes

The changes in DB2® registry variables, configuration parameters, and database physical design characteristics can have an upgrade impact. Review these changes to manage the upgrade impact.

About this task

After upgrading your DB2 server, compare the values of your registry variables and configuration parameters to their values before upgrade. If you find any differences, take the time to understand them because they could alter the behavior or performance of your applications. However, consider carefully whether to disable any new functionality because it provides support for new resources needed by the database manager. You should disable new functionality only if you experience negative performance or unwanted behavior.

Procedure

To manage DB2 server behavior changes:

Review the information about new, changed, deprecated, and discontinued registry variables, and based on the upgrade impact, choose the appropriate settings:
- New registry variables
- Changes to existing registry variables
- There are no registry variables that have been deprecated or discontinued in this release. However, if you are upgrading from DB2 Version 9.1 or earlier, consider removing registry variables that have been deprecated or discontinued in pre-Version 9.7 releases:
Set your DB2 global profile registry variables. The variables that you set at the global profile level, using the db2set command with the -g option, are not upgraded. The global profile variables apply to all instances pertaining to a specific DB2 copy. Therefore, after upgrading your instances, use the configuration information that you saved in the pre-upgrade tasks to restore the values of your global profile registry variables for every DB2 Version 9.7 copy.
Review the information about new, changed, and deprecated database manager configuration parameters, and based on the upgrade impact, choose the appropriate settings:
- New database manager configuration parameters
- Changes to existing database manager configuration parameters
- There are no database manager configuration parameters that have been deprecated or discontinued in this release. However, if you are upgrading from DB2 Version 9.1 or earlier, consider removing database manager configuration parameters that have been deprecated in pre-Version 9.7 releases:
  - Deprecated database manager configuration parameters in DB2 Version 9.5
  - Deprecated database manager configuration parameters in DB2 Version 9.1
Review the information about new, changed, deprecated, and discontinued database configuration parameters, and based on the upgrade impact, choose the appropriate settings:
- New database configuration parameters
- Changes to existing database configuration parameters
- There are no database manager configuration parameters that have been deprecated or discontinued in this release. However, if you are upgrading from DB2 Version 9.1 or earlier, consider removing database manager configuration parameters that have been deprecated or discontinued in pre-Version 9.7 releases:
  - Deprecated and discontinued database configuration parameters in DB2 Version 9.5
  - Deprecated and discontinued database configuration parameters in DB2 Version 9.1
Review the changes in database physical design characteristics and security, and based on the upgrade impact, modify database objects accordingly:
- Changes to physical design characteristics of databases
- Changes to authorities and privileges

What to do next

If you change the settings of any database manager configuration parameters that are not dynamic, you might need to restart the instance so the new settings take effect.