DB2 10.5 for Linux, UNIX, and Windows
DB2 10.5 for Linux, UNIX, and Windows
Changes to DB2® registry variables, configuration parameters, database physical design characteristics, and database authorities and privileges can result in DB2 server behavior changes that might impact your upgrade.
Generally, instance profile variables that you set in your DB2 profile registry or your system environment retain their values after an instance upgrade. Some global profile registry variables, such as DB2SYSTEM and DB2PATH, are set by the DB2 installation procedure or instance upgrade. However, the global profile registry variables that you set by running the db2set command with the -g option are not upgraded. Therefore, you must define them after upgrade.
Existing database and database manager configuration parameters also, generally, retain their values after upgrade. However, the default values assigned to new parameters or the new default values assigned to existing parameters might change the behavior or performance of your applications.
| Name | Upgrade impact |
|---|---|
| DB2DSDRIVER_CFG_PATH | This variable now specifies multiple configuration files at same or different locations with different names. If filename is not specified in a path and name pair, then the file name defaults to a value of db2dsdriver.cfg. |
You should remove the use of registry variables that are deprecated because the functionality associated with the variable is obsolete or has been replaced by new functionality. See Deprecated registry variables to determine the upgrade impact of deprecated registry variables. See Discontinued registry variables to determine the upgrade impact of discontinued registry variables.
If you are upgrading from DB2 Version 10.1 or earlier, consider removing deprecated registry variables in pre-Version 10.5 releases because the functionality associated with the variable is obsolete or replaced by new functionality. Also, remove the use of discontinued registry variables in pre-Version 10.5 releases as they do not have the intended effect. See Changes that impact Version 10.1 or earlier releases for details.
No database manager configuration parameters are deprecated or discontinued in this release. However, if you are upgrading from DB2 Version 9.7 or Version 9.8, consider removing deprecated database manager configuration parameters in Version 10.1 releases because the functionality associated with the parameters is obsolete or replaced by new functionality. Also, remove the use of discontinued database manager configuration parameters in Version 10.1 releases as they do not have the intended effect. See Changes that impact Version 10.1 or earlier releases for details.
The following table describes the upgrade impact of the default values of new database configuration parameters:
| Name | Upgrade impact |
|---|---|
| dft_table_org | This parameter specifies whether a user table is created as a column-organized table (value COLUMN) or a row-organized table (value ROW) when the ORGANIZE BY COLUMN or the ORGANIZE BY ROW clause is not specified on the CREATE TABLE statement.The default value for this parameter is ROW, which has no impact on upgrade. If you have DDL scripts and you plan to change the default orientation of tables, modify your exiting scripts to specify the ORGANIZE BY COLUMN or the ORGANIZE BY ROW clause for the CREATE TABLE statements to ensure that tables are created with the proper orientation regardless of the setting of this parameter. |
For more information, see Changes to database configuration parameters.
The following table describes the upgrade impact of changes to existing database configuration parameters:
| Name | Upgrade impact |
|---|---|
| hadr_syncmode | In Version 10.5, the default value for hadr_syncmode is changed from NEARSYNC to ASYNC for DB2 pureScale® databases. For all other database types, the default for hadr_syncmode remains NEARSYNC. |
| hadr_target_list | In Version 10.5, initializing HADR without setting this parameter is deprecated. You should set this parameter regardless of the number of standby databases as part of the initialization process. For more information, see Initializing HADR has changed. |
For more information, see Changes to database configuration parameters.
You must remove the use of database configuration parameters that are deprecated and discontinued because the functionality associated with the variable is obsolete or replaced by new functionality. See Some database configuration parameters are deprecated or discontinued to determine the upgrade impact of deprecated and discontinued database configuration parameters.
If you are upgrading from DB2 Version 9.7, consider removing deprecated database configuration parameters in pre-Version 10.1 because the functionality associated with the parameter is obsolete or replaced by new functionality. Also, remove the use of discontinued database configuration parameters in Version 10.1 as they do not have the intended effect. See Changes that impact Version 10.1 or earlier releases for details.
There are no changes to the authorities and privileges in this release.
See Upgrade impact from DB2 command changes and Upgrade impact from SQL statement changes for a summary of DB2 command and SQL statement changes with upgrade impact. See the Command Reference and SQL Reference for details about all the changes in authorization.