Obsolete Database Parameters 
Some database parameters are identified as obsolete. These parameters have either been removed already or will be removed in one of the next database versions.
The following table lists the most important database parameters that have been identified as obsolete.
Name (from version 7.7.03) |
Old Name (up to and including version 7.7.02) |
Marked as Obsolete Since Version |
Removed Since Version |
Description |
|---|---|---|---|---|
- |
_BACKUP_HISTFILE |
7.7 |
7.7 |
Name of the history file for data and log backups |
- |
_BACKUP_MED_DEF |
7.7 |
7.7 |
Name of the file containing the definitions of the backup templates |
DeprecatedParameter22 |
_UNICODE |
7.7 |
- |
Defines whether the database system uses Unicode as the character set for the names of database objects in the database catalog |
DeprecatedParameter22 |
BACKUP_BLOCK_CNT |
7.7 |
- |
Block size used by the database system when writing backups to data carriers Only useful for tapes that have an optimal block size |
DeprecatedParameter13 |
EXPAND_COM_TRACE |
7.7 |
- |
Specifies whether memory space is reserved when COM trace files are created |
DeprecatedParameter29 |
USE_OPEN_DIRECT |
7.7 |
- |
Replaced by UseFilesystemCacheForVolume, see Support Database Parameters YES: the database system uses the O_DIRECT flag when opening volumes (if this flag is supported by the file system). You use this flat to configure that the operating system does not use a separate cache for I/O operations. Note that this flag is ignored for Linux kernel < 2.4.18. Changes only apply after restart |