Show TOC

Properties of Database ParametersLocate this document in the navigation structure

Use

The following table lists the properties of database parameters that are used in the default database parameter file cserv.pcf. Most of these properties are for internal use only and are not available when changing a database parameter using database tools such as Database Studio or Database Manager CLI.

Property

Permitted Values

Description

CASESENSITIVE

YES | NO

Specifies whether the parameter value is case-sensitive.

CHANGE

NO | RUNNING | OFFLINE

Specifies whether and in which operational state the parameter can be changed

NO = not changeable

RUNNING = changeable in ONLINE and ADMIN operational state; you can choose when the change shall take effect

OFFLINE = the new value only takes effect after a restart

CLEAR

YES | NO

Specifies whether the parameter can be adopted in a new database

DEPRECATEDID

Old parameter name

The parameter name has changed.

However, the old name is still recognized by the system.

More information: Obsolete Database Parameters

DEVSPACE

YES | NO

Parameter type:

YES = volume parameter

NO = kernel parameter

DISPLAYNAME

Character string, may contain blank characters

Description that is displayed for the parameter in some database tools

DYNAMIC

YES | NO

Specifies whether there are placeholders for the parameter (for example: DATAVOL_?)) in the default parameter file

GROUP

GENERAL | EXTENDED | SUPPORT | NO | TRACE

Group to which the parameter belongs:

GENERAL: General database parameters

EXTENDED: Special database parameters

SUPPORT: Support database parameters

NO: Parameter not displayed in some database tools

TRACE: Parameter for the database trace, database structure checks and monitoring

INSTANCES

LVC | OLTP

Database type for which the parameter is relevant:

LVC = SAP liveCache Technology

OLTP = SAP MaxDB

If no value is displayed for this property, the parameter is valid for all database types.

INTERN

YES | NO

Specifies whether the value is used for internal calculations

MANDATORY

YES | NO

Specifies whether the parameter has to have a value (non zero or not empty)

MAX

-

Maximum value

MIN

-

Minimum value

MODIFY

YES | NO

Specifies whether you can still change the parameter after the database has been created.

Example: NO for the parameter RunDirectoryPath

SCOPE

-

Not implemented yet

USERDEFINED

YES | NO

YES: The value of the parameter was set directly by a user or a database tool.

If you change a database parameter whose value is normally calculated by the system, then the system uses this user-defined value for all subsequent recalculations of database parameter values. The system discards and recalculates this user-defined value only if it is not within the permitted value range (a situation that might occur, for example, after the database software has been updated).

VALUESET

Value set

Separate the individual values with blanks or tabs. For string parameters, place the strings in quotation marks.

Example

As database system administrator DBADMIN with the password SECRET, you use Database Manager CLI to display the properties of the database parameter CacheMemorySize for the database DEMODB:

dbmcli -d DEMODB -u DBADMIN,SECRET param_directget CacheMemorySize

				OK
CacheMemorySize	2500
			

dbmcli -d DEMODB -u DBADMIN,SECRET param_getproperties CacheMemorySize

OK
CHANGE          OFFLINE
INTERN          NO
MANDATORY       YES
CLEAR           NO
DYNAMIC         NO
CASESENSITIVE   NO
DEVSPACE        NO
MODIFY          YES
GROUP           GENERAL
DISPLAYNAME
VALUESET
MAX
MIN
INSTANCES
SCOPE           INSTANCE
DEPRECATEDID    CACHE_SIZE
USERDEFINED     YES