Entering content frame

Function documentation Properties of Database Parameters Locate the document in the library structure

Use

Beyond its current value, every database parameter also has other properties. These properties are defined in the default parameter file cserv.pcf (see Configuration Files).

Caution

Changes to database parameters do not take effect until the database instance is restarted.

You can also change some database parameters while the database is running. In addition you can choose how long the change is to be effective for these database parameters:

      Until the next restart

      Not until after the next restart

      Immediately and permanently

Properties of Database Parameters

Property

Permitted Values

Description

CASESENSITIVE

YES | NO

The database system observes lowercase and uppercase for the values.

CHANGE

NO | RUNNING | OFFLINE

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

NO = cannot be changed

RUNNING = changeable in the operational states ONLINE and ADMIN; you can choose when the change takes 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 instance (e.g. NO for the parameter RUNDIRECTORY)

DEVSPACE

YES | NO

Type of parameter:

YES = Volume parameter

NO = Kernel parameter

DISPLAYNAME

Character string, may contain blank characters

Name for the parameter displayed in the Database Manager GUI

DYNAMIC

YES | NO

Specifies whether there are placeholders for the parameter (e.g. 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 is not displayed in the Database Manager GUI

TRACE: Parameter for the database trace, database check and monitoring

INSTANCES

LVC | OLTP

Database instance for which the parameter is relevant:

LVC = SAP liveCache

OLTP = OLTP (MaxDB)

Not specified: Valid for all database instance types

INTERN

YES | NO

Specifies whether the value is required for internal calculations

LASTKNOWNGOOD

 

Last valid value (value that the parameter had the last time the database instance was started successfully)

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 instance has been created (e.g. NO for the parameter RUNDIRECTORY)

VALUESET

The individual values have to be separated from each other by blank characters or tabs.

For character string parameters, the permitted character string constants have to be placed in quotation marks.

Value set

Example

As operator DBADMIN with the password SECRET, you use the Database Manager CLI to display the properties of the parameter RUNDIRECTORY for the database instance DEMODB:

dbmcli –d DEMODB –u DBADMIN,SECRET param_getproperties RUNDIRECTORY

OK

CHANGE  OFFLINE

INTERN  NO

MANDATORY       YES

CLEAR   YES

DYNAMIC NO

CASESENSITIVE   YES

DEVSPACE        NO

MODIFY  YES

GROUP   GENERAL

DISPLAYNAME

VALUESET

MAX

MIN

INSTANCES

 

Leaving content frame