Changes to database manager configuration parameters in Db2 11.5.6
Db2 11.5.6 contains a number of new and changed database manager configuration parameters.
Review the changes to learn which ones might affect your existing applications and to determine whether you have to adjust them.
Also, review the list of deprecated and discontinued database manager configuration parameters to learn about additional changes that might also affect your applications and scripts.
Parameter name | Details about the change in 11.5.6 |
---|---|
ALT_DIAGPATH | While in a Db2
pureScale® environment, the
diagnostic data directory path used must contain at least one split token ($h ,
$n , or $m ) to ensure a private db2diag log
file for each member and CF. In addition, if a path without a split token was configured in a
Db2
pureScale
environment it will be updated to include a $m split token appended to the current
configured path during installFixPack -commit_level . |
CF_DIAGPATH | While in a Db2
pureScale environment, the
diagnostic data directory path used must contain at least one split token ($h ,
$n , or $m ) to ensure a private db2diag log
file for each member and CF. In addition, if a path without a split token was configured in a
Db2
pureScale
environment it will be updated to include a $m split token appended to the current
configured path during installFixPack -commit_level . |
DIAGPATH | While in a Db2
pureScale environment, the
diagnostic data directory path used must contain at least one split token ($h ,
$n , or $m ) to ensure a private db2diag log
file for each member and CF. In addition, if a path without a split token was configured in a
Db2
pureScale
environment it will be updated to include a $m split token appended to the current
configured path during installFixPack -commit_level . |
Resolution
Take advantage of enhanced functionality or new features by adopting new functionality through the use of new database manager configuration parameters or new values for existing database manager configuration parameters.
For new database manager configuration parameters or changes to existing database manager configuration parameters that result in Db2 server behavior changes, adjust your existing applications or scripts.