DB2 10.5 for Linux, UNIX, and Windows

Some database configuration parameters are deprecated or discontinued

Due to changes in functionality, the introduction of new database configuration parameters, or the removal of support, the following database configuration parameters are either deprecated or discontinued.

Details

The following database configuration parameters are deprecated:

Table 1. Deprecated database configuration parameters
Parameter name	Description	Details
buffpage	Buffer pool size	This parameter indicated the default buffer pool size for the ALTER BUFFERPOOL or CREATE BUFFERPOOL statements that indicated the value -1 as the size. Use the SIZE parameter for both statements to indicate an explicit value or use the AUTOMATIC value to enable self tuning of the buffer pool.
softmax	Recovery range and soft checkpoint interval	This parameter determines the frequency of soft checkpoints and the recovery range, which help out in the crash recovery process. Use the page-age_trgt_mcr and page-age_trgt_gcr database configuration parameters, instead of the softmax parameter. The page-age_trgt_mcr parameter specifies the target duration for changed pages to be retained in the local bufferpool before being persisted to table space storage, or for DB2® pureScale instances, to the group bufferpool. The page-age_trgt_gcr specifies the target duration for changed pages to be kept in the group buffer pool before being persisted to disk.

The following database configuration parameters are discontinued:

Table 2. Discontinued database configuration parameters
Parameter name	Details
auto_stats_prof	This configuration parameter is discontinued because automatic statistics profiling is discontinued. For more information, see Automatic statistics profiling is discontinued.
auto_prof_upd	This configuration parameter is discontinued because automatic statistics profiling is discontinued. For more information, see Automatic statistics profiling is discontinued.

Resolution

Remove the use of database configuration parameters that are deprecated because the functionality associated with the configuration parameter is obsolete or has been replaced by new functionality. Also, remove the use of discontinued database configuration parameters as they do not have the intended effect.

If a replacement database configuration parameter is provided, set it to maintain the intended database behavior.