To support new and changed functionality in DB2® Version 10.5, a number of changes were made to registry and environment variables.
Registry variable | Description |
---|---|
DB2_SMP_INDEX_CREATE | Introduced in DB2 Cancun Release 10.5.0.4, this DB2 registry variable overrides the default number of agents used to scan and sort the index data when building or rebuilding an index. |
Registry variable | New values |
---|---|
DB2_WORKLOAD | For column-organized tables, the new ANALYTICS value enables column organization, space reclamation, and automatic workload management, and automatically configures initial memory values and page and extent sizes. To help establish an optimal default configuration for analytic workloads, set this value before creating the database. |
Registry variable | Changed behavior |
---|---|
DB2DSDRIVER_CFG_PATH | You can now use this variable to specify multiple configuration files with different names at the same or different locations. If you do not specify a file name in a path and name pair, the file name defaults to a value of db2dsdriver.cfg. If you do not specify a path name, it defaults to the directory structure for your operating system. |
DB2_COLLECT_TS_REC_INFO | Starting in Fix Pack 1, the default setting for this registry variable is now OFF for high availability disaster recovery (HADR) databases. Tablespace recovery is not supported with HADR, so there is no need for the overhead of keeping track of which table spaces changed in each log file. |
Take advantage of enhanced functionality or new features by using new registry variables or new values for registry variables.
For new registry variables or changes to registry variables that result in DB2 server behavior changes, adjust your applications or scripts.
Review the list of deprecated and discontinued registry variables to learn about additional changes that might impact your applications and scripts and determine whether you have to adjust them.