Show TOC

Obsolete Database ParametersLocate this document in the navigation structure

Use

Starting with version 7.7.03 of the database software, some database parameters have been marked 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 marked as obsolete.

Table 1: Obsolete Database Parameters (Selection)

Name

Old Names

Marked as Deprecated Since Version

Removed Since Version

Description

DeprecatedParameter38

EnableSynchronousTaskIO

_USE_IOPROCS_ONLY

7.8

-

YES: I/O operations are executed only by special I/O threads

NO: The kernel decides whether a task executes an I/O operation itself or delegate the I/O operation to a special I/O thread

-

MaxVolumes

MAXVOLUMES

7.8

-

Maximum number of data and log volumes, including mirrored volumes

-

MiniDumpType

MINI_DUMP

7.8

-

Defines whether the system writes the memory dumps knlmini.dmp and srvmini.dmp (for postmortem debugging) and how much information these dumps contain

-

_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

DeprecatedParameter01

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

-

ClusterCompressionThreshold

7.7.06.04

7.7.04.27

7.8.00.04

-

Minimum number of blocks in a cluster that is eligible for compression that needs to be reached before the database system starts compressing the cluster (in 1/1000 of the total block count)

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