DB2 Version 10.1 for Linux, UNIX, and Windows
DB2 Version 10.1 for Linux, UNIX, and Windows
Version 10.1 contains a number of new and changed database configuration parameters.
| Parameter name | Description | Details |
|---|---|---|
| dft_schemas_dcc | Default data capture on new schemas | This parameter allows the control of default setting for DATA CAPTURE CHANGES on newly created schemas for replication purposes. For more information, see Replication improvements. |
| hadr_replay_delay | HADR standby log replay time delay | This parameter specifies the time that must have passed from when the data is changed on primary before these changes would be reflected on the standby database. The time is specified in number of seconds. For more information, see HADR delayed replay provides protection against application errors. |
| hadr_spool_limit | HADR spool limit | This parameter allows log replay on the HADR standby database to be behind the HADR primary database. If there is a spike in transaction volume or slow replay caused by specific operations and the log receive buffer fills up, the log data is written (or spooled) to disk and then read later. For more information, see HADR log spooling prevents spikes on throughput. |
| hadr_target_list | HADR target list | This parameter, which is used to enable multiple HADR standbys, specifies a list of up to three target host:port pairs that act as HADR standby databases. For more information, see HADR now supports multiple standby databases. |
| log_appl_info | Application information log record | This parameter specifies that the application information log record is written at the start of each update transaction. |
| log_ddl_stmts | Log DDL statements | This parameter specifies that extra information regarding DDL statements will be written to the log. |
| mon_uow_execlist | Monitoring unit of work events with executable list | This parameter enables (ON) or disables (OFF) the collection of execution list information by the unit of work event monitor. By default, execution list information is not collected (OFF). It is a child parameter of the mon_uow_data database configuration parameter. For more information, see Executable ID list is included in unit of work event monitor information. |
| mon_uow_pkglist | Monitoring unit of work events with package list | This parameter enables (ON) or disables (OFF) the collection of package list information by the unit of work event monitor. By default, package list information is not collected (OFF). It is a child parameter of the mon_uow_data database configuration parameter. For more information, see Collection of package list information has changed. |
| systime_period_adj | Adjust temporal SYSTEM_TIME period | This database configuration parameter specifies how to handle the situation of a history row for a system-period temporal table potentially being generated with an end timestamp less then the begin timestamp. |
The following database configuration parameters have changed behaviors, new ranges, or new values in Version 10.1.
| Parameter name | Description | Details |
|---|---|---|
| auto_stats_views | Statistical views configuration parameter | This parameter enables and disables automatic statistic collection on statistical views. When enabled, DB2® will maintain the statistics on statistical views automatically. |
| HADR-related configuration parameters | In previous releases, no HADR configuration
parameter could be updated dynamically; the database had to be deactivated
and reactivated for the updates to take effect. Starting in Version 10.1,
updates to these configuration parameters can take effect on the HADR
primary without deactivating the database. You do have to issue a
STOP HADR on the primary, followed by a START HADR AS PRIMARY. As
a result, you can make configuration parameter updates to your HADR
primary without having an impact on the applications that are using
the database. Note: The following new HADR configuration parameters
also have this behavior:
|
|
| mon_obj_metrics | Monitoring object metrics configuration parameter |
|
| mon_uow_data | Monitoring units of work | In Version 10.1, the values that you can specify for mon_uow_data have changed. The default value for mon_uow_data continues to be NONE. It is a parent parameter to mon_uow_execlist and mon_uow_pkglist. For more information, see Collection of package list information has changed. |
| num_iocleaners | Controls the number of asynchronous page cleaners for a database | In previous releases, the AUTOMATIC setting calculated the number of page cleaners based on the number of logical CPUs. In Version 10.1, the calculation now uses the number of physical CPU cores instead. (On the HP-UX platform the number of logical CPUs is still used.) |
| seqdetect | Sequential detection and readahead flag | This parameter controls whether the database manager is allowed to perform sequential detection or readahead prefetching during I/O activity. |
| mon_req_metrics | Monitoring request metrics configuration parameter | In Version 10.1, the default value for mon_req_metrics is changed from BASE to NONE. |
| mon_act_metrics | Monitoring activity metrics configuration parameter | The default value for mon_act_metrics is changed from BASE to NONE. |
| mon_obj_metrics | Monitoring object metrics configuration parameter | The default value for mon_obj_metrics is changed from BASE to NONE. |
| mon_lw_thresh | Monitoring lock wait threshold configuration parameter | The default value for mon_lw_thresh is changed from 5000000 to 4294967295. |
Take advantage of enhanced functionality or new features by adopting new functionality through the use of new database configuration parameters or new values for existing database configuration parameters.
For new database configuration parameters or changes to existing database configuration parameters that result in DB2 server behavior changes, adjust your existing applications or scrips.
Review the list of discontinued database configuration parameters to determine additional changes that might impact your applications and scripts.