Frequently Used Config Parameters in SAP HANA 1 2

Frequently Used Configuration Parameters in SAP HANA
 SAP HANA Platform Software
Target Audience
■ Consultants
■ Administrators
■ Others
Public
Document version 1.2 – 2016/09/23
Contents
1 Introduction .................................................................................... 5
1.1 About This Document ....................................................................... 5
1.2 SAP HANA Guides ............................................................................ 5
2 Filename: global.ini ........................................................................ 6
Section: auditing configuration ............................................................. 6
Section: authentication........................................................................... 8
Section: backup....................................................................................... 8
Section: communication ....................................................................... 12
Section: cross_database_access ........................................................ 20
Section: cryptography .......................................................................... 21
Section: customizable_functionalities ................................................ 22
Section: execution ................................................................................ 22
Section: expensive_statement ............................................................. 25
Section: ha_dr_provider_<classname>............................................... 31
Section: inifile_checker ........................................................................ 32
Section: internal_hostname_resolution .............................................. 34
Section: memorymanager .................................................................... 34
Section: memoryobjects ....................................................................... 37
Section: multidb .................................................................................... 38
Section: persistence ............................................................................. 40
Section: public_hostname_resolution ................................................ 46
Section: resource_tracking .................................................................. 47
Section: spark_configuration ............................................................... 50
Section: storage .................................................................................... 52
Section: system_information ............................................................... 54
Section: system_replication ................................................................. 54
Section: system_replication_communication .................................... 64
Section: system_replication_hostname_resolution........................... 66
Section: table_placement ..................................................................... 67
Section: threads .................................................................................... 68
Section: trace ........................................................................................ 68
Section: traceprofile% .......................................................................... 71
3 Filename: attributes.ini ................................................................ 73
Section: global ...................................................................................... 73
4 Filename: daemon.ini .................................................................. 74
Section: compileserver ......................................................................... 74
Section: indexserver ............................................................................. 74
Section: indexserver.c .......................................................................... 75
Section: indexserver.<tenandSID> ...................................................... 75
Section: nameserver ............................................................................. 75
Section: preprocessor .......................................................................... 75
Section: sapwebdisp / webdispatcher................................................. 76
SAP HANA Platform 2

Section: scriptserver............................................................................. 76
Section: statisticsserver ....................................................................... 76
Section: xsengine.................................................................................. 76
5 Filename: esserver.ini ................................................................. 77
Section: row_engine ............................................................................. 77
6 Filename: executor.ini ................................................................. 79
Section: pythontrace............................................................................. 79
7 Filename: indexserver.ini ............................................................ 81
Section: authentication......................................................................... 81
Section: authorization........................................................................... 82
Section: cache ....................................................................................... 82
Section: calcengine............................................................................... 84
Section: distribution ............................................................................. 85
Section: execution ................................................................................ 86
Section: import_export ......................................................................... 87
Section: joins ......................................................................................... 88
Section: load_trace ............................................................................... 89
Section: mergedog ................................................................................ 90
Section: optimize_compression .......................................................... 93
Section: parallel .................................................................................... 94
Section: partitioning ............................................................................. 95
Section: password policy ..................................................................... 97
Section: pythontrace........................................................................... 103
Section: queueserver .......................................................................... 104
Section: repository.............................................................................. 104
Section: search ................................................................................... 105
Section: session .................................................................................. 106
Section: smart_data_access .............................................................. 110
Section: sql .......................................................................................... 112
Section: sql_client_network_io .......................................................... 116
Section: sqlscript ................................................................................ 116
Section: sqltrace ................................................................................. 117
Section: table_redist ........................................................................... 121
Section: trace ...................................................................................... 126
Section: traceprofile% ........................................................................ 126
Section: transaction ............................................................................ 126
Section: unload_trace ......................................................................... 128
Section: result_cache ......................................................................... 129
8 Filename: multidb.ini ................................................................. 130
Section: readonly_parameters ........................................................... 130
9 Filename: nameserver.ini .......................................................... 135
Section: auditing configuration ......................................................... 135
Section: password policy ................................................................... 135
Section: public_urls ............................................................................ 135
SAP HANA Platform 3

Section: sld .......................................................................................... 136

Section: statisticsserver ..................................................................... 138
Section: topology ................................................................................ 138
10 Filename: statisticsserver.ini .................................................. 139
Section: memorymanager .................................................................. 139
Section: statisticsserver_general ...................................................... 139
Section: statisticsserver_intervals .................................................... 139
Section: statisticsserver_view% ........................................................ 140
11 Filename: webdispatcher.ini ................................................... 141
Section: profile .................................................................................... 141
12 Filename: xsengine.ini............................................................. 145
Section: application_container .......................................................... 145
Section: authentication....................................................................... 145
Section: communication ..................................................................... 146
Section: customer_usage ................................................................... 147
Section: debugger ............................................................................... 147
Section: httpserver.............................................................................. 148
Section: jsvm ....................................................................................... 150
Section: odata ..................................................................................... 151
Section: public_urls ............................................................................ 151
Section: scheduler .............................................................................. 153
13 Filename: wlreplayer.ini .......................................................... 155
Section: communication ..................................................................... 155
Important Disclaimers on Legal Aspects.................................... 156
Coding Samples .................................................................................. 156
Accessibility ........................................................................................ 156
Gender-Neutral Language .................................................................. 156
Internet Hyperlinks .............................................................................. 156
Copyright ....................................................................................... 157
SAP HANA Platform 4

1 Introduction
1.1 About This Document
This guide provides information about some of the main configurable parameters in SAP
HANA. Information is organized on the basis of the initialization files where the parameters
occur:
 global.ini
 attributes.ini
 daemon.ini
 esserver.ini
 executor.ini
 indexserver.ini
 multidb.ini
 nameserver.ini
 statisticsserver.ini
 webdispatcher.ini
 xsengine.ini
 wlreplayer.ini.
Check SAP Note 2036111 for information on the latest version of this document.
For each parameter a validity value is shown indicating from which HANA revision the
parameter is available. For example: 'SAP HANA revisions >= 90'. It is assumed that all
parameters are valid from release 60 and this is indicated as: 'All SAP HANA revisions'.
1.2 SAP HANA Guides

For more information about SAP HANA landscape, security, installation and administration,
see the SAP HANA platform page of SAP Help Portal at http://help.sap.com/hana_platform.
SAP HANA Platform 5

2 Filename: global.ini
This configuration file describes global parameters for each service in the landscape.
Section: auditing configuration

This section contains parameters that are related to auditing configuration.
Parameter: alert_audit_trail_type
Description: Sets an audit trail target to which audit entries from audit policies with the
audit level ALERT are written.
Multi-tenant database container (MDC) systems:
In a tenant database, the parameter is read-only by default. The
parameter can only be changed in the system database.
Values: CSTABLE
CSVTEXTFILE
SYSLOGPROTOCOL
Default: default_audit_trail_type
Restart required: No
Validity: Non-MDC (single container) systems:
SAP HANA revisions >= 90
MDC systems:
Related information: Auditing Activity in SAP HANA Systems (Admin Guide)
System Properties for Configuring Auditing (Security Guide)
Parameter: critical_audit_trail_type
Description: Sets an audit trail target to which audit entries from audit policies with the
audit level CRITICAL are written.
Values: CSTABLE
CSVTEXTFILE
SYSLOGPROTOCOL
MDC systems:
SAP HANA Platform 6

Parameter: default_audit_trail_type
Description: Default audit trail target of the database.
Values: CSTABLE
CSVTEXTFILE
SYSLOGPROTOCOL
Default: CSTABLE for SAP HANA revisions >= 70
All SAP HANA revisions
MDC systems:
Parameter: emergency_audit_trail_type
Description: Audit trail target to which audit entries from audit policies with the audit
level EMERGENCY are written.
Values: CSTABLE
CSVTEXTFILE
SYSLOGPROTOCOL
MDC systems:
Parameter: global_auditing_state
Description: Enables (true)/disables (false) global auditing regardless of the enabled
state of the audit policies.
Non-MDC (single container) systems:
SAP HANA Platform 7

In a single-container system, the global auditing state is set in the
global.ini file.
MDC systems:
In a multi-tenant database container system, the global auditing state for
the system database is set in the nameserver.ini file, and for the tenant
databases in the global.ini file.
Values: true, false
Default: false
MDC systems:
SAP Note1991634
Section: authentication
This section contains parameters that are related to authentication configuration.
Parameter: authentication_methods
Description: Sets one or more authentication methods.
Values: Comma-separated list of one or more authentication methods
Default: password,kerberos,spnego,saml,saplogon,x509xs,sessioncookie
Validity: SAP HANA revisions >= 120
Related information: User Authentication Mechanisms (Security Guide)
Section: backup
This section contains parameters that are related to configuration of backup.
Parameter: log_backup_parameter_file
Description: Sets a file location of a parameter file for log backup operations when
using a third-party tool through the backint interface.
When the database isolation level is LOW, the system database and tenant
databases use the same backup parameter files.
When database isolation level is HIGH, the system database and the
tenant databases have separate backup parameter files.
Values: Absolute file path. Can include the variable $(SAPSYSTEMNAME).
SAP HANA Platform 8

Parameter: log_backup_parameter_file
Recommended values:
/usr/sap/$(SAPSYSTEMNAME)/SYS/global/hdb/opt/config/$(SAPSYSTEMN
AME)_log.utl
MDC systems:
/usr/sap/$(SAPSYSTEMNAME)/SYS/global/hdb/opt/config/DB_$(TENANTN
AME1)/$(SAPSYSTEMNAME)_$(TENANTNAME1)_log.utl
$(TENANTNAME1) is not a predefined environment variable.
Default: Empty string
MDC systems:
Related information: Set the Isolation Level to High for Backups with an SAP HANA Multitenant
Database Container and Third-Party Backup Tools (Admin Guide)
Parameter: data_backup_parameter_file
Description: Sets a file location of a parameter file for data backup operations when
using a third-party tool through the backint interface.
When the database isolation level is LOW, the system database and tenant
databases use the same backup parameter files.
When database isolation level is HIGH, the system database and the
tenant databases have separate backup parameter files.
Values: Absolute file path. Can include the variable $(SAPSYSTEMNAME).
Recommended values:
/usr/sap/$(SAPSYSTEMNAME)/SYS/global/hdb/opt/config/$(SAPSYSTEMN
AME)_data.utl
MDC systems:
/usr/sap/$(SAPSYSTEMNAME)/SYS/global/hdb/opt/config/DB_$(TENANTN
AME1)/$(SAPSYSTEMNAME)_$(TENANTNAME1)_data.utl
$(TENANTNAME1) is not a predefined environment variable.
MDC systems:
SAP HANA Platform 9

Parameter: data_backup_parameter_file
Related information: Set the Isolation Level to High for Backups with an SAP HANA Multitenant
Database Container and Third-Party Backup Tools (Admin Guide)
Parameter: data_backup_max_chunk_size
Description: Sets a maximum file size (0 = unlimited) in megabytes for file-based data
backup.
When the size of backup data for a service exceeds the specified maximum
value, the HANA System splits a backup stream into multiple smaller files.
When set to zero, the file size is unlimited.
Values: Positive integer or zero
Default: 0 = unlimited
Validity: All SAP HANA revisions
Related information: Backup Console (Admin Guide)
Parameter: data_backup_savepoint_lock_timeout
Description: Sets a data backup savepoint lock timeout (0 = unlimited) in seconds.
The data backup savepoint lock timeout specifies the maximum time
period a data backup operation waits to acquire a lock for executing a
savepoint.
When set to zero, the backup operation can wait an unlimited time to
acquire a savepoint lock.
Default: 7200 (2 hours)
Parameter: enable_accumulated_catalog_backup
Description: Enables (true) / disables (false) the accumulation of backup catalog
changes by multiple log backups to one backup of the backup catalog.
When set to true, the backup catalog is backed up once for multiple log
backups.
When set to false, the backup catalog is backed up after each log backup
operation.
The accumulation has the advantage that fewer backups of the backup
catalog are created.
Accumulated backup operations of the backup catalog are supported for
both using a file system and a third-party backup tool.
Values: true, false
Default: true
SAP HANA Platform 10

Parameter: enable_accumulated_catalog_backup
Related information: Accumulated Backups of the Backup Catalog (Admin Guide)
Parameter: log_backup_using_backint
Description: Enables (true) / disables (false) log backup using a third-party tool through
the backint interface.
Values: true, false
Default: false
Related information: Configure a Third-Party Backup Tool (Admin Guide)
Parameter: log_recovery_resume_point_interval
Description: Specifies a minimum time interval in seconds between two savepoint
operations during log recovery. The savepoint operations are triggered by
savepoint log entries provided that the specified minimum time interval
elapsed.
When set to zero (disabled), no savepoint operations are performed
during log recovery.
Values: Positive integer or zero (disabled)
Default: 1800 (seconds = 30 minutes)
Restart required: Yes (System is down during log recovery).
Related information: Resuming an Interrupted Recovery (Admin Guide)
Parameter: max_log_backup_group_size
Description: Sets a maximum number of log segments to be processed by a single
backint request.
The accumulation of multiple log segments reduces the backups of the
backup catalog and restarts of the backup agent.
Values: Positive integer (1 … 255)
Default: 8
Related information: Log Backups and Third-Party Backup Tools (Admin Guide)

Parameter: max_recovery_backint_channels
Description: Sets a maximum number of backup objects per backint request to read log
backup data for each service in multiple streams when using a third-party
tool through the backint interface.
Values: Positive integer (1 … 1024)
Default: 64
Parameter: parallel_data_backup_backint_channels
Description: Sets a number of parallel channels per data backup to write backup data for
each service in multiple streams when using a third-party tool through the
backint interface.
During recovery, the HANA System uses a number of streams which is
independent of the value of the parameter
parallel_data_backup_backint_channels specified during the backup.
The parameter parallel_data_backup_backint_channels applies only to
HANA services (hdbindexserver, hdbxsengine, etc.) that have more than
128 GB data persisted to disk. HANA services with less than 128 GB
persisted data use only one channel.
Values: Positive integer ( 1 … 32 )
Default: 1
Related information: Multistreaming Data Backups with Third-Party Backup Tools (Admin Guide)
Section: communication
This section contains parameters that are related to configuration of communications.
Parameter: encrypt
Description: Enables (true) / Disables (false) TSL/SSL encryption.
Values: true, false
Default: false
Restart required: Yes

Parameter: listeninterface
Description: Specifies the network interface that the processes listen on.
Values: .global to select all available network interfaces
.internal to select all network interfaces that are listed in
[internal_hostname_resolution]
.local to select only local network interfaces, for example, 127.0.0.1
Default: .global
Restart required: No. Changes take effect after the service has been reconfigured.
MDC systems:
Related information: Configuring the Network for Multiple Hosts (Admin Guide)
Configuring SAP HANA Inter-Service Communication (Admin Guide)
SAP Note 1999797
Parameter: sql_connect_hosts
Description: Defines a list of (virtual) host names or IP addresses that client applications
and components use to connect to the HANA System.
Values: One or more host names or IP addresses separated by commas
Parameter: ssl
Description: Enables (on) / Disables (off) TSL/SSL / Enables system public key
infrastructure (systempki or systemPKI) for secure internal communication
between hosts.
When set to on, the user has to manually configure the public key
infrastructure for secure internal communication.
When set to systempki, the HANA System automatically configures the
secure internal communication.
When set to off, secure internal communication is disabled.

Parameter: ssl
Values: on, off, systempki (case-insensitve)
Default: off
Related information: Verify TLS/SSL Configuration of Internal Communication Channels (Admin
Guide)
Securing Data Communication (Security Guide)
Parameter: ssl_local
Description: Enables (on, true) / Disables (off, false) secure localhost communication
between processes on the same host.
The secure localhost communication is only enabled when the secure
internal communication between hosts has been enabled, i.e., the
parameter ssl has the value true or systempki.
Values: on, true, off, false
Default: on, true
Validity: SAP HANA revisions >=100
Related information: Securing Data Communication (Security Guide)
Parameter: sslCipherSuites
Description: Sets the encryption algorithms available for TSL/SSL connections.
The value depends on the cryptographic service provider used.
For more information, see the documentation of the cryptographic library.
Values: String
Default: 1. PFS:HIGH::EC_HIGH:+EC_OPT if sslCryptoProvider is set to
“commoncrypto” or “sapcrypto”. The value “sapcrypto” is obsolete
and “commoncrypto” should be used instead.
2. ALL:!ADH:!LOW:!EXP:!NULL: if sslCryptoProvider is set to “openssl”
3. Empty string if sslCryptoProvider is set to “mscrypto”. The value
“mscrypto” is not supported on Linux.

Parameter: sslCipherSuites
Parameter: sslCreateSelfSignedCertificate
Description: Enables (true)/disables (false) the creation of a self-signed certificate if the
key store for external communication cannot be found.
Values: true, false
Default: false
MDC systems:
Related information: SAP Note 1891055
Parameter: sslCryptoProvider
Description: Sets the cryptographic library provider used for SSL communication.
When one of the cryptographic library providers CommonCryptoLib
(“commoncrypto”) or SAP Cryptographic Library (“sapcrypto”) are pre-
installed, the HANA System automatically sets it as default.
When not, the HANA System will opt for the OpenSSL library on Linux and
set the value “openssl”.
Note: If you specify a value for this parameter, you must also explicitly
specify paths in both the sslKeyStore and sslTrustStore parameters to
avoid configuration issues.
Values: commoncrypto, sapcrypto, openssl, mscrypto
Default: 1. “commoncrypto” or “sapcrypto” (if installed)
For SAP HANA revisions >= 90, CommonCryptoLib is installed per
default.
For SAP HANA revisions < 90, CommonCryptoLib must be downloaded
from SAP Service Marketplace and installed manually.
The “sapcrypto” option is obsolete and “commoncrypto” is
recommended.
2. “openssl” in other cases on Linux
(if CommonCryptoLib or SAP Cryptographic Library are not installed)

Parameter: sslCryptoProvider
MDC systems:
Parameter: sslEnforce
Description: Enforces (true) / Does not enforce (false) external communication to use
SSL.
Note: The HANA System refuses SQL connection attempts from clients that
do not use SSL.
Values: true, false
Default: false
MDC systems:
Parameter: sslInternalKeyStore
Description: Sets the files system location of the key store file used for internal
communication, comprising communication between hosts in scale-out
and replication scenarios and inter-process communication on the same
host.
Values: Absolute file path. Environment variables are not supported.
Default: 1. “$SECUDIR/sapsrv_internal.pse”
if sslCryptoProvider is set to “commoncrypto”
2. “$DIR_INSTANCE/$VTHOSTNAME/ssl/key.pem”
if sslCryptoProvider is set to “openssl”
When the default settings are unchanged, the environment variables
variables $SECUDIR or $DIR_INSTANCE/$VTHOSTNAME are replaced with
specific values at HANA System restart.

Parameter: sslInternalKeyStore
When an explicit values is set, the absolute file path is needed.
MDC systems:
Parameter: sslInternalTrustStore
Description: Sets the file system location of the trust store file used for internal
communication, comprising communication between hosts in scale-out
and replication scenarios and inter-process communication on the same
host.
Default: 1. “$SECUDIR/sapsrv_internal.pse”
if sslCryptoProvider is set to “commoncrypto”
2. “$DIR_INSTANCE/$VTHOSTNAME/ssl/trust.pem” if sslCryptoProvider is
set to “openssl”
variables $SECUDIR or $DIR_INSTANCE/$VTHOSTNAME are replaced with
specific values at HANA System restart.
MDC systems:
Parameter: sslInternalValidateCertificate
Description: Enables (true) / Disables (false) the validation of the certificate of the
communication partner during secure internal communication.
The certificate is validated for both secure internal inter-host
communication and secure inter-process communication on the same
host.
In a tenant database, the parameter is read-only by default. The parameter
can only be changed in the system database.

Parameter: sslInternalValidateCertificate
Values: true, false
Default: true
MDC systems:
Parameter: sslKeyStore
Description: Sets the file system location of the key store file that contains the server’s
private key used for external communication.
Default: 1. “$SECUDIR/sapsrv.pse” if sslCryptoProvider is set to “commoncrypto”
2. “$HOME/.ssl/key.pem” if sslCryptoProvider is set to “openssl”
$SECUDIR or $HOME are replaced with specific values at HANA System
restart.
When an explicit value is set, the absolute file path is needed.
MDC systems:
SAP Note 1891055
Parameter: sslMaxProtocolVersion
Description: Sets the maximum available SSL protocol version.
Values: TLS10, TLS11, TLS12, MAX
Default: MAX

Parameter: sslMaxProtocolVersion
MDC systems:
Parameter: sslMinProtocolVersion
Description: Sets the minimum available SSL protocol version
Values: SSL30, TLS10
Default: TLS10
MDC systems:
Parameter: sslTrustStore
Description: Sets the file location to the trust store file that contains the server’s public
certificate used for external communication.
Default: 1. “$SECUDIR/sapsrv.pse” if sslCryptoProvider is set to “commoncrypto”
2. “$HOME/.ssl/trust.pem” if sslCryptoProvider is set to “openssl”
variables $SECUDIR or $HOME are replaced with specific values at HANA
System restart.
MDC systems:
SAP Note 1891055

Parameter: sslValidateCertificate
Description: Enables (true) / Disables (false) the validation of communication partner’s
certificate during external communication.
Values: true, false
Default: false
MDC systems:
Related information: Configure SSL for SAP HANA Studio Connections (Admin Guide)
Section: cross_database_access
This section contains parameters that control communication among tenant databases in a
multi-tenant database container system.
Parameter: enabled
Description: Enables (true) / Disables (false) cross database access in a HANA System.
When set to true, the HANA System enables communication from one
tenant database to one or more other tenant databases.
When set to false, the HANA System disables communication among
tenant databases.
Note: The parameter can only be configured in the system database.
Values: true, false
Default: false
Related information: Enable and Configure Cross-Database Access (Admin Guide)
Parameter: targets_for_<source_db_name>
Description: Defines one or more target database names for cross-database access
from one source database name in multitenant database container
systems.
Note: Each parameter entry configures cross-database access only in one
direction.
Examples:
“targets_for_DB1=DB2,DB3” defines cross-database access from DB1 to
DB2 and from DB1 to DB3.

Parameter: targets_for_<source_db_name>
“targets_for_DB2=DB1” defines cross-database access from DB2 to DB1
Note: The parameter can only be configured in the system database.
Values: <target_db_name> or comma-separated thereof.
Default: Parameter not set
Section: cryptography
This section contains parameters that are related to cryptography.
Parameter: ccl_fips_enabled
Description: Enables (true) / Disables (false) the FIPS mode of the cryptographic library
CommonCryptoLib by loading additional kernel modules.
The FIPS mode is only supported when the parameter sslCryptoProvider
has been set to “commoncrypto”.
When set to true, the HANA system will satisfy the Security Requirements
for Cryptographic Modules according to the Federal Information Processing
Standards Publication (FIPS PUB) 140-2.
When set to false, the HANA System will use the internal cryptographic
kernel.
Values: true, false
Default: false
Related SAP Note 2180024
information: SAP’s Crypto Kernel receives FIPS 140-2 certificate (SCN)
Validated FIPS 140-1 and FIPS 140-2 Cryptographic Modules (external)
Parameter: ssfs_key_file_path
Description: Sets a path to the key files used by SSFS (Secure Storage in File System) for
Persistence Encryption and Application Encryption.
Caution: Check that this path is accessible by every server within your
distributed environment.
Default: $(DIR_GLOBAL)/hdb/security/ssfs
The HANA internal variable $(DIR_GLOBAL) represents the path
“/usr/sap/$SAPSYSTEMNAME/SYS/global”, which is replaced with a
specific value when …

Parameter: ssfs_key_file_path
Related information: Change the SSFS Master Keys (Admin Guide)
Encryption Key Management (Security Guide)
Section: customizable_functionalities
This section contains parameters that are related to restricted features of multitenant
database containers.
Parameter: <feature>
Description: Enables (true) / Disables (false) a restricted <feature>
The parameter settings on the database layer overwrite the settings on
the system layer.
Values: true, false
Default: true
MDC systems:
Related information: Disable Features on a Tenant Database (Admin Guide)
System Views:
SYS.M_CUSTOMIZABLE_FUNCTIONALITIES
SYS_DATABASES.
M_CUSTOMIZABLE_FUNCTIONALITIES
Section: execution
This section contains parameters that are related to parallel execution.
Parameter: default_statement_concurrency_limit
Description: Restricts the actual degree of parallel job execution within a statement per
connection.
When set to 0 or not set, there is no limitation.
When set to values greater than 0, reasonable values are between 1 and
max_concurrency.
In the SQL statement 'CREATE WORKLOAD CLASS', this parameter sets a
default value for the statement attribute 'STATEMENT THREAD LIMIT' when
not explicitly specified.
Default: Not set

Parameter: default_statement_concurrency_limit
Validity: SAP HANA revisions >= 102.03
Related information: Configuring Workload Management (Admin Guide)
Controlling Parallel Execution of SQL Statements (Admin Guide)
Parameters that Control CPU (Admin Guide)
Parameter: max_concurrency
Description: Sets a maximum target value for the average number of running job worker
threads (0 = number of available logical cores).
Job worker threads process parallelized OLAP queries and perform system
tasks such as table updates, savepoint operations, garbage collection,
backup, and recovery.
The current number of running job worker threads can exceed the specified
target value.
The total number of job worker threads can be larger than the specified
target value because some of the job worker threads are not in the state
Running.
When set to 0, the target value is the number of available logical CPU cores.
When Hyperthreading is enabled, the server has more logical cores than
physical cores.
When the specified value is smaller than the default value, the job worker
threads will only use a part of the available logical CPU cores.
When the specified target value is too large, the SAP HANA System may be
overloaded due to a high degree of parallelization.
When the specified target value is too small, important system tasks may get
stuck.
In a tenant database, the parameter is read-only by default. The parameter
can only be changed in the system database.
The parameter settings in the database layer overwrite the settings in the
system layer.
In the database layer, the parameter max_concurrency controls an effective
number of logical cores of a corresponding multi-tenant database container.
A reasonable value is the number of available logical CPU cores divided by
the number of tenant databases.
In the database layer, the parameter cannot be set for the system database.
In the database layer, do not set the parameter to 0. In that case, the target
value for the average number of running worker threads will be equal to the
number of available logical CPU cores for each (!) tenant database.
Default: Number of available logical cores.
Restart required: No. Parameter changes take effect not later than the currently running job
worker threads have terminated.

MDC systems:
Related information: Controlling CPU Consumption (Admin Guide)
Parameter: max_concurrency_hint
Description: Limits the number of jobs to create in a parallelization step during statement
execution. Multiple parallelization steps may result in far more jobs being
created for a statement (and hence higher concurrency) than this
parameter. The actual number of jobs being executed in parallel is further
limited by the parameters [execution] default_statement_concurrency limit
and [execution] max_concurrency so that a parallelization step can create
fewer jobs than specified by the parameter max_concurrency_hint.
When set to 0 or not specified, the effective limit is equal to the value of the
parameter [execution] max_concurrency.
Note: SAP recommends to leave the default settings which allow the HANA
System utilize most of the available CPU resources.
If this parameter is modified, reasonable values are between 0 and
max_concurrency.
In large systems with at least four sockets, consider setting [execution]
max_concurrency_hint and [parallel] num_cores equal to the number of
logical cores per socket.
SAP recommends that the parameters max_concurrency_limit and [parallel]
num_cores have equal values because the two values are used in the same
logical function, but affect different places in the code.
Default: 0
Related information: Configuring Workload Management (Admin Guide)

Section: expensive_statement
This section contains parameters that are related to the collection of expensive statement
information.
Parameter: application
Description: Sets an application filter condition to restrict traced SQL statements to
those of the specified application.
The filter is disabled when the value is an empty string.
Example: “ABAP:<SAPSID>”
Values: String
Related information: Expensive Statements Trace Options (Admin Guide)
Parameter: application_user
Description: Sets an application user filter condition to restrict traced SQL statements
to those of the specified application user.
Example: a user of the SAP NetWeaver Application Server
Values: String
Parameter: enable
Description: Enable (true) / Disable (false) the collection of expensive statement
information.
The recorded expensive SQL statements and associated information can
be queried using the monitoring view M_EXPENSIVE_STATEMENTS.
Values: true, false
Default: false

Parameter: in_memory_tracing_records
Description: Sets a maximum number of traced SQL statements to be stored in a
memory ring buffer per service.
The ring buffer stores new records in a cyclic order and, if full,
overwrites old records.
The default value of 30000 records corresponds to about 10 MB of
data, but the real memory consumption depends on the size of the
individual statements. Be aware that longer SQL statements need
more memory than shorter ones.
The parameter in_memory_tracing_records only takes effect when
the parameter use_in_memory_tracing was set to true.
Values: Positive integer
Default: 30000
Parameter: maxfiles
Description: Sets a maximum number of trace files (0 = trace file rotation disabled)
When set to 0, the trace file rotation is disabled.
Trace files have cyclic behavior.
When the parameter maxfiles is greater than 1 and the maximum number
of trace files reached, the oldest trace file is deleted and a new one
opened.
When the parameter maxfiles is 1 and the maximum file size is reached,
the trace file is deleted and a new one opened.
The size of the trace files depends on the parameter
[expensive_statement] maxfilesize.
Values: Positive integer or zero (0 to 999)
Default: 10
Related information: Configure Trace File Rotation (Admin Guide)
Parameter: maxfilesize
Description: Sets a maximum size of an individual trace file in bytes (0 = unlimited)
When set to 0, the file size is unlimited.
The minimum value is the default value of 10000000 bytes.
Trace files have cyclic behavior.
When the parameter maxfiles is greater than 1 and the maximum file size
is reached, a new trace file is opened.

When the parameter maxfiles is 1, and the parameter maxfilesize is
greater than zero, and the maximum file size is reached, the trace file is
deleted and a new one opened.
The maximum number of trace files depends on the parameter
[expensive_statement] maxfiles.
Values: Positive integer ( 10000000 and higher ) and zero
Default: 10000000 (bytes = 9,5 megabytes)
Related information: Configure Trace File Rotation (Admin Guide)
Expensive Statements Trace Options (Admin Guide)
Parameter: object
Description: Sets an object filter condition to restrict traced SQL statements to those
referencing the specified one or more objects.
Objects can be one or more the following: tables, views, and procedures.
Multiple objects are specified as comma-separated list.
The object names can be preceded by corresponding schema qualifiers,
which are separated from the object name by a dot.
Example:
<SCHEMA_1>.<TABLE_1>,
<SCHEMA_1>.<TABLE_2>,
<SCHEMA_2>.<PROCEDURE_1>,
<VIEW_1>
Values: String
Parameter: passport_tracelevel
Description: Sets a passport trace level as an additional filter condition to restrict
traced SQL statements to those that are marked with a passport of the
specified level or a higher level.
The parameter passport_tracelevel is used when expensive statements
trace is activated as part of an end-to-end trace scenario with Process
Monitoring Infrastructure (PMI).
When set to medium, statements are traced with levels medium and high.
When set to high, only statements are traced with level high.

Parameter: passport_tracelevel
Note: Process monitoring is only possible for components in the ABAP and
Business Objects stacks.
Values: high, medium
Parameter: threshold_cpu_time
Description: Sets a lower threshold value for the CPU runtime of SQL statements in
microseconds (-1 = disabled, 0 = all SQL statements).
Only SQL statements that have a longer CPU runtime than the specified
threshold value are recorded in the expensive statement trace.
When set to -1, the filter is disabled.
When set to 0, all SQL statements are traced.
Values: Positive integer, zero, or -1.
Default: -1 (disabled)
Parameter: threshold_duration
Description: Sets a lower threshold value for the runtime of SQL statements in
microseconds (-1 = filter disabled, 0 = all statements).
Only SQL statements that run longer than the specified threshold value are
recorded in the expensive statement trace.
Default: 1000000 ( microseconds = 1 second )

Parameter: threshold_memory
Description: Sets a lower threshold value for the memory usage of statement execution
in bytes (-1 = filter disabled, 0 = all statements).
Only SQL statements that use more memory than the specified threshold
value are recorded in the expensive statement trace.
The memory threshold only takes effect when memory tracking has been
enabled ([resource_tracking] enable_tracking = on and [resource_tracking]
memory_tracking = on).
Default: -1 (disabled)
Parameter: trace_flush_interval
Description: Defines a number of traced SQL statements that are copied at once from a
memory ring buffer to a trace file.
When the number of records in the memory ring buffer exceeds the value
N of this parameter, the N oldest records of the memory ring buffer are
copied to the trace file.
When set to 0 or 1, each trace records is copied to the trace file
immediately.
To minimize data loss in the case of system failure, keep the value of the
parameter small, for example, between 1 and 10.
The parameter trace_flush_interval only takes effect when the parameter
use_in_memory_tracing was set to true.
When the ring buffer is full, new trace records overwrite the oldest ones.
The size of the ring buffer depends on the parameter
[expensive_statement] in_memory_tracing_records.
Values: Positive integer and zero
Default: 10
Parameter: trace_parameter_values
Description: Enables (true) / Disables (false) the tracing of parameter values of SQL
statements.
The parameter values replace question marks (?) of the prepared SQL
statements during execution.

Parameter: trace_parameter_values
When set to true, the parameter values are displayed as a comma-
separated list in the PARAMETERS column of the
M_EXPENSIVE_STATEMENTS view.
When set to false, no parameter values are displayed.
When the tracing of parameter values is disabled, the size of the traced
SQL statements is smaller.
Values: true, false
Default: true
Parameter: use_in_memory_tracing
Description: Controls target location of expensive statements information.
When set to true, expensive statements trace information is stored in a
memory ring buffer. Each service has a separate ring buffer.
When set to false, trace information is stored in trace files. There is one
expensive statements trace file for all servces.
Memory ring buffers and trace files have cyclic behavior. When the ring
buffer is full or the maxium number of trace files reached, new expensive
trace records overwrite the oldest ones.
Values: true, false
Default: true
Parameter: user
Description: Sets a HANA user filter condition to restrict traced SQL statements to
those of the specified HANA SQL user.
Values: String

Section: ha_dr_provider_<classname>
This section contains parameters of HA/DR provider scripts in HANA System replication
scenarios.
Parameter: <parameter_name>
Description: Defines configuration parameters of HA/DR provider scripts as name-
value-pairs.
Note: All HA/DR provider scripts are loaded when the nameserver service
is starting.
Values: <parameter_value>
Default: N/A
Related information: Install and Configure a HA/DR Provider Script (Admin Guide)
System view M_HA_DR_PROVIDERS
Parameter: execution_order
Description: Sets an execution order when having more than one HA/DR provider
script, where 1 indicates highest and 99 lowest priority.
Example: three HA/DR providers have execution_order values 20, 40, and
60 with decreasing priority.
is starting.
Values: Positive integer ( 1 .. 99 )
Default: 50
Parameter: path
Description: Sets the file path for an HA/DR provider script.
is starting.
Default: N/A

Parameter: provider
Description: Sets the class name defined in an HA/DR provider script.
is starting.
Values: String
Default: N/A
Section: inifile_checker
This section contains parameters that control the watchdog checking ini files in HANA
System replication scenarios.
Parameter: enable
Description: Enables (true) / disables (false) the watchdog that checks differences of ini
file parameters between primary and secondary systems in a system
replication scenario.
Values: true, false
Default: True
Related Monitoring INI File Parameter Changes (Admin Guide)
information: SAP Note 1984641
Parameter: exclusion_[<inifilename>|*][/<LAYER>]
Description: All parameter names starting with exclusion_ in the section [inifile_checker]
define an ini file name and LAYER name, and the corresponding parameter
values define one or more combinations of a section name and
configuration parameter name. Multiple combinations are separated by
commas.
The ini file name can be replaced with an asterisk. The LAYER name can be
SYSTEM, HOST or DATABASE.
The section name and configuration parameter name can contain wildcards
or be replaced with an asterisk each.
The pre-defined combinations are excluded from regular checks in HANA
System replication scenarios.
Values: [<section with wildcards>|*][/<configuration parameter with wildcards>|*]
Default: exclusion_global.ini/SYSTEM =
storage/*, persistence/*path*, *hostname_resolution*,
system_replication/*

Parameter: exclusion_[<inifilename>|*][/<LAYER>]
exclusion_nameserver.ini/SYSTEM =
landscape/*
exclusion_daemon.ini/HOST = */instances
exclusion_* = traceprofile_*
Related Monitoring INI File Parameter Changes (Admin Guide)
information: SAP Note 2100052
Parameter: interval
Description: Sets a time interval in seconds between two checks for differences of ini file
parameters between primary and secondary systems in a system replication
scenario.
To disable/enable those checks, set the parameter [inifile_checker] enable.
Default: 3600 (seconds = 1 hour)
Related information: Monitoring INI File Parameter Changes (Admin Guide)
Parameter: replicate
Description: Enables (true) / Disables (false) the replication of ini file parameters from a
primary site to secondary sites
Values: true, false
Default: false
Related information: Monitoring INI File Parameter Changes (Admin Guide)

Section: internal_hostname_resolution
This section contains mappings of IP addresses to internal hostnames.
Parameter: <internal_ip_address>
Description: Specifes internal IP addresses for the internal communication among
multiple server hosts of a distributed SAP HANA System.
When the parameter listeninterface in the section [communication] has
been set to .internal, the internal IP addresses specified in the section
[internal_hostname_resolution] will be used.
Values: <internal_hostname>
Default: N/A
Restart required: No. Changes take effect after one minute.
Related information: Configuring the Network for Multiple Hosts (Admin Guide)
Section: memorymanager
This section contains parameters that are related to configuration of memory management.
Parameter: allocationlimit
Description: Sets an upper limit of memory usable by individual processes in
megabytes.
When set to 0 or missing, the SAP HANA system implicitly calculates a
default value based on global_allocation_limit.
Default: 0 (implicit limit calculation)
MDC systems:
Parameter: global_allocation_limit
Description: Sets an explicit usable memory for the entire SAP HANA system in
megabytes.
When set to 0 or missing, the SAP HANA system implicitly calculates a
default value based on the size of physical RAM.
Note: Set an explicit value to use only a portion of physical RAM.

Parameter: global_allocation_limit
Note: Do not select an explicit value less than 58982, which is 90% of 64
GB, or more than the calculated default value. For details, see Parameter
Reference: Memory Consumption (Admin Guide).
Default: 0 (implicit limit calculation)
Restart required: No, since HANA revision 70
MDC systems:
Related information: Parameter Reference: Memory Consumption (Admin Guide)
Set a Statement Memory Limit (Admin Guide)
Monitoring INI File Parameter Changes (Admin Guide)
SAP Note 1984422
Parameter: oom_dump_time_delta
Description: Sets a lower limit for the time between creating two dump files of the
same type by the same service in seconds (0 = disabled).
The following dump file types are supported:
 compositelimit oom (statement-specific)
 oom memory release (node-specific)
 after oom cleanup (node-specific)
Default: 86400 (1 day)
Parameter: statement_memory_limit
Description: Sets a statement memory limit in gigabytes.
The limit defines the maximum memory that can be temporarily used for
the execution of a statement on one node.
Statements that exceed the limit will be aborted, but other processes of
the SAP HANA system are not affected.
Within the time period defined by the parameter oom_dump_time_delta,
at most one dump file is created per service. The name of the dump file
contains the string “compositelimit oom”.

Parameter: statement_memory_limit
The statement memory limit only takes effect when memory tracking has
been enabled ([resource_tracking] enable_tracking = on and
[resource_tracking] memory_tracking = on).
Caution: Do not set a limit that is too small.
In the SQL statement 'CREATE WORKLOAD CLASS', this parameter sets a
default value for the statement attribute 'STATEMENT MEMORY LIMIT'
when not explicitly specified.
Default: SAP HANA revisions >= 80: Empty string
SAP HANA revisions >= 85.03: 0
Setting a Statement Memory Limit for SQL Statements (Admin Guide)
Additional User Parameters (Admin Guide)
SAP Note 2072856
SAP Note 1999997
Parameter: statement_memory_limit_threshold
Description: Sets a memory usage threshold per cluster node as percentage of the
global allocation limit (0% = disabled) so that the statement memory limit
feature only takes effect when the used memory per node exceeds the
specified memory usage threshold.
Caution: Do not forget the percentage character %.
When the used memory per node falls below the specified memory usage
threshold, the statement memory limit has no effect.
The statement memory limit only takes effect when memory tracking has
been enabled ([resource_tracking] enable_tracking = on and
[resource_tracking] memory_tracking = on).
When set to 0%, the statement memory limit does not depend on the
used memory per node.
Values: Positive integer between 0% and 100%.
Default: 0%
Setting a Statement Memory Limit for SQL Statements (Admin Guide)
Additional User Parameters (Admin Guide)
SAP Note 1999997

Section: memoryobjects
This section contains parameters that are related to the configuration of memory objects.
Parameter: page_loadable_columns_limit
Description: Sets an upper threshold memory size of page loadable column pages per
service in megabytes.
When the total size of page loadable column pages per service exceeds the
specifield threshold size, the HANA System automatically starts unloading
pages from memory until the memory size specified by the parameter
page_loadable_columns_min_size is reached.
When set to 0 or unspecified, the threshold is disabled.
Values: Positive integer (zero = disabled)
Default: 1047527424 (=999 Terabytes)
Related information: Managing cold data in SAP HANA database memory (SCN)
SAP Note 2111649
Parameter: page_loadable_columns_min_size
Description: Sets a lower threshold memory size of page loadable column pages per
service in megabytes.
When the total size of page loadable column pages per service falls below
the specified threshold size, the HANA System automatically stops
unloading pages from memory.
When set to 0 or unspecified, the threshold is disabled.
Values: Positive integer (zero = disabled)
Default: 1047527424 (=999 Terabytes)
Related information: Managing cold data in SAP HANA database memory (SCN)
SAP Note 2111649
Parameter: unload_lower_bound
Description: Sets a threshold for a table size in bytes. When a columnstore table
exceeds this threshold, it is unloaded from memory.
When set to 0, the SAP HANA system automatically controls the unloading
of columnstore tables.
Example: 1.649.267.441.664 (1.5 TB)
Default: 0

Parameter: unload_lower_bound
Parameter: unused_retention_period
Description: Sets a retention period for memory objects in seconds.
Memory objects that have not been used for the specified period of time
will be unloaded from memory.
When set to 0, the SAP HANA system automatically controls the unloading
of memory objects.
The unloading of memory objects can take longer than the specified time.
Caution: Do not set an explicit value less than 3600 (one hour).
Recommended: 0, 3600 and larger
Default: 0
Section: multidb
This section contains parameters that are related to multi-tenant database containers.
Parameter: database_isolation
Description: Sets one of the following database isolation levels (low, high).
When set to low, all operating system processes of the HANA System run
under the same operating system user “sidadm” and the same operating
system group “sapsys”.
When set to high, the operating system processes of each tenant run
under a dedicated operating system user <tenantuser>, for example,
“tenant1adm” for “TENANT1”, “tenant2adm” for “TENANT2”, etc., who
belongs to the system group <tenantgrp>, for example, “tenants”, but not
“sapsys”. The directories data, log, backup, trace, and config are owned by
the operating system user “sidadm” who belongs to the system group
<tenantgrp> with access permissions 0770.
Values: high, low
Default: low
Parameter: mode
Description: Sets one of the modes (multidb, singledb)

Parameter: mode
When set to multidb, the HANA System instance is a true multi-tenant
database container system that comprises one system database and one
or more tenant databases.
When set to singledb, the HANA instance comprises only one default
system database. This option is backwards compatible.
Values: multidb, singledb
Default: singledb
Related information: Increase the System Isolation Level (Admin Guide)
Parameter: reserved_instance_numbers
Description: Sets a number of additional reserved instances.
The parameter reserved_instance_numbers defines the port range
(3<nn>00 – 3<mm>99) that will be used for the creation of additional
tenant database containers.
Example: If thepre-defined instance number is <nn> = 02, a port range
from 30200 to 30299 can be used. When the value of the parameter
reserved_instance_numbers is set to 3, the port range is extended by
three further instances <nn> = 03, 04, 05, and you will effectively use
tenant ports ranging from 30200 to 30599.
Values: Positive integer or zero.
Default: 0
Related information: Add a Service to a Tenant Database (Admin Guide)
Parameter: systemdb_reserved_memory
Description: Sets a minimum amount of memory for the system DB of a multitenant
database container system in megabytes.
When set to 0, no minimum amount of memory is reserved.
The parameter only applies to multi-tenant database container (MDC)
systems.
Default: 0
Validity: MDC systems:
Related information: Managing Resources in Multiple-Container Systems (Admin Guide)

Section: persistence
This section contains parameters that are related to the configuration of data and log
locations as well as data and log backup.
Parameter: basepath_databackup
Description: Defines an absolute base file path for data backups. Per default, data
backups will be stored under this file path.
During a backup operation, an administrator can override the default

value to write the data backup to a filesystem that is independent of the
HANA instance.
Default: $(DIR_INSTANCE)/backup/data
Related information: SAP HANA DATABASE BACKUP AND RECOVERY (SCN)
Parameter: basepath_datavolumes
Description: Defines the absolute base file path for data volumes. All data volumes will
be stored under this file path.
Caution: Changing this parameter can cause loss of data. Make sure you
create a full system backup first.
Values: Absolute file path
Default: $(DIR_GLOBAL)/hdb/data
$(DIR_GLOBAL) is an HANA internal variable, not a shell
environment variable
Related information: Persistent Data Storage in the SAP HANA Database (Admin Guide)
Create a Storage Snapshot (Admin Guide)
SAP Note 1766708
SAP Note 1900728
Parameter: basepath_datavolumes_es
Description: Defines the absolute base file path for data volumes of the extended
storage database (SAP HANA dynamic tiering option). All data volumes will
Multi-tenant database container systems:


Parameter: basepath_datavolumes_es
Default: $(DIR_GLOBAL)/hdb/data_es
$(DIR_GLOBAL) is an HANA internal variable, not a shell environment
variable
MDC systems:
SAP Note 1900728
Parameter: basepath_logbackup
Description: Defines an absolute base file path for log backups. Per default, log backups
will be stored under this file path.
During a backup operation, an administrator can override the default
value to write the data backup to a filesystem that is independent of the
HANA instance.
Default: $(DIR_INSTANCE)/backup/log
Parameter: basepath_logvolumes
Description: Defines the absolute base file path for log volumes. All log volumes will be
stored under this file path.
Default: ${DIR_GLOBAL}/hdb/log
variable
Related information: Persistent Data Storage in the SAP HANA Database (Admin Guide)
SAP Note 1766708
SAP Note 1900728

Parameter: basepath_logvolumes_es
Description: Defines the absolute base file path for log volumes or the extended
storage database (SAP HANA dynamic tiering option). All log volumes will
Default: $(DIR_GLOBAL)/hdb/log_es
variable
MDC systems:
Parameter: enable_auto_log_backup
Description: Enables (yes) /disables (no) automatic log backup of closed log segments.
Values: yes, no
Default: yes
Related information: Enable or Disable Automatic Log Backup (Admin Guide)
SAP HANA DATABASE BACKUP AND RECOVERY (SCN)
SAP Note 1645183
Parameter: log_backup_timeout_s
Description: Sets a log backup timeout in seconds (0 = disabled).
The log backup timeout specifies the maximum time period between a
COMMIT operation and the time when a log segment containing the
COMMIT operation is closed and put into the log segment backup queue.
Log segments can be closed before they are completely filled.
When set to 0, log segments are only put into the log segment backup
queue when they are full or explicitly closed.
The log backup timeout depends on the Recovery Point Objective (RPO)
defined by the customer. The RPO is the maximum acceptable amount of
data loss after an unplanned data-loss incident, expressed as an amount of
time.

Parameter: log_backup_timeout_s
Recommended: 300 to 3600.
Default: 900
Restart required: No. Changes take effect at the next log segment switch.
Related information: Change the Log Backup Interval (Admin Guide)
SAP HANA DATABASE BACKUP AND RECOVERY (SCN)
SAP Note 1645183
Parameter: log_buffer_count
Description: Sets a count of log buffers per physical partition
When the log buffer count is raised, the HANA System can buffer
additional peak loads at the cost of a possibly increasing latency of parallel
short transactions.
If the I/O sub-system supports highly-parallel write operations, the
increase of the log buffer count may provide a higher throughput for large
transactions.
Values: Positive integer ( 4 ... 128 )
Default: 8
Parameter: log_buffer_size_kb
Description: Sets a size of an in-memory log buffer in kilobytes.
When the log buffer size is raised, the I/O throughput may grow at the
cost of an increasing COMMIT latency because at most the specified
amount of data must be flushed to the I/O sub-system during a COMMIT
of a transaction.
Values: Positive integer ( 128 .. 16384 ) ( 128 kilobytes ... 16 megabytes )
Default: 1024 ( kilobytes = 1 megabyte )

Parameter: log_mode
Description: Sets the logging mode.
The log area of the database is subdivided into logical log segments.
 In normal mode, log segments are released when they have been
backed up and a savepoint has taken place.
 In overwrite mode, log segments are freed by the next savepoint.
 In legacy mode, log segments are kept in the log area until a full
backup has been executed.
Caution: Legacy mode is deprecated since SPS 03 and is not supported

since SPS 07.
Values: normal
overwrite
legacy (deprecated as of SPS 03, not supported since SPS 07)
Default: normal
Related information: Set up System Replication with hdbnsutil (Admin Guide)
Configure the Primary System (Admin Guide)
Enable Full Sync Option for System Replication (Admin Guide)
Log Modes (Admin Guide)
SAP Note 1645183
SAP Note 2357713
Parameter: max_gc_parallelity
Description: Sets a maximum number of parallel garbage collection threads (0 =
number of available logical CPU cores).
When set to 0, the number of threads is limited by the number of available
logical CPU cores.
When the specified value is too small, historical data may grow faster than
garbage collection is able to clean up, which may cause “database full”
situations.
Keep in mind that the number of available threads will be also limited by
the configuration parameters of the job executor framework:
 [execution] max_concurrency
 [execution] max_concurrency_hint
 [parallel] num_cores
Values: Positive integer or zero ( 0 .. 256 )
Default: 0

Parameter: savepoint_interval_s
Description: Sets the savepoint interval in seconds.
The savepoint interval controls the frequency at which savepoint
operations are performed.
Recommended: 10 (seconds) to 7200 (2 hours)
Default: 300 (5 minutes)
Parameter: tablepreload_write_interval
Description: Sets a table preload write interval in seconds (0 = disabled).
This parameter defines the time period at which table preload information
is collected and written to disk.
The table preload information comprises all column-store table columns
that are currently loaded into memory.
The collected information is used as follows:
- When the table reload option is enabled, the table preload information
determines the table columns that are loaded during SAP HANA system
restart.
- In a system replication scenario, when the table preload option has been
enabled in the primary system, the table preload information is collected
in the primary system and transferred to a secondary system.
- In a system replication scenario, when the table preload option has been
enabled in the secondary system, the table preload information
determines the table columns that are loaded into memory.
Default: 3600 (1h) for SAP HANA Revisions < 70
86400 (1 day) for SAP HANA Revisions >= 70

Parameter: use_mountpoints
Description: Includes (true) / excludes (false) mountpoint directories in the file path of
data and log volumes. The mountpoint directories have the format
mntNNNNN, where NNNNN represents a 5-digit number. The mountpoint
directories are an intermediate layer between the base file paths and the
volume directories hdbNNNNN.
Caution: Do not change this parameter unless the reasons described in the
SAP Notes below apply.
Values: true, false
Default: True
SAP Note 1820553
Section: public_hostname_resolution
This section specifies how internal hostnames are resolved to external names. External
names could be IP addresses, hostnames, or fully qualified host names.
Parameter: map_<internal_hostname>
Description: Defines explicit addressing of database server hosts by external clients
when the parameter use_default_route has been set to no.
The parameters refer to one or more internal hostnames. The values refer
to one or more external/public names, which are mapped to the
corresponding external/public names.
Exact mapping:
map_<internal_hostname> = <external_name>
Pattern mapping:
map_<internal_hostname_prefix>* = <external_name-prefix>*
map_<internal_hostname_prefix>* = <external_name-
prefix>*<external_name_suffix>
In the case of pattern mapping, the parameter name must end with *, the
parameter value can have the * in the middle or in the end.
The external names can be IP addresses, hostnames or fully qualified
domain names.
Values: <external_name-prefix>
<external_name-prefix>*
<external_name-prefix>*<external_name_suffix>
Default: N/A

Parameter: map_<internal_hostname>
Related information: Mapping Host Names for Database Client Access (Admin Guide)
SAP Note 1906381
Parameter: use_default_route
Description: Defines one or more ways of addressing database server hosts by external
clients:
ip = through external IP addresses
name = through external hostnames
fqdn = through external fully qualified domain names
no = through internal hostnames
Values: ip, name, fqdn, or any combinations thereof;
no
Default: ip
Related information: Mapping Host Names for Database Client Access (Admin Guide)
SAP Note 1906381
Section: resource_tracking
This section contains parameters that are related to the tracking of system resources.
Parameter: cpu_time_measurement_mode
Description: Enables (on) / Disables (off) CPU time tracking / measurements for
threads, statements, or sessions.
The values “fast” and “detailed” are deprecated and have been mapped to
“on”.
Values: on, off
Default: off
Validity: on,off:
fast (deprecated), detailed (deprecated):
SAP HANA revisions < 90
Parameter: enable_tracking
Description: Enables (on) / disables (off) tracking of system resources.
For performance reasons, the system resource tracking is disabled by
default.

Parameter: enable_tracking
If enabled, all resources for which tracking has been enabled, will be
measured periodically and the values can be displayed in corresponding
system views and/or trace files.
To enable statement memory tracking and/or to use statement memory
limits, set the parameter enable_tracking to true.
Values: on, off
Default: off
Related information: Set a Statement Memory Limit (Admin Guide)
SAP Note 1999997
Parameter: load_monitor_granularity
Description: Defines a sampling interval in milliseconds for load monitoring data.
When set to values between 100 milliseconds and 10000 milliseconds (10
seconds), the HANA System samples the load monitoing data with the
specified period of time.
Note: Avoid small sampling intervals, which cause a measurable increase
of the system load.
When set to values between 10000 milliseconds (10 seconds) and 60000
milliseconds (60 seconds), the HANA System samples the load monitoring
data every 10000 milliseconds (10 seconds) and calculates average values
to save memory.
Values: Positive integer (100 .. 60000)
Default: 10000
Related information: System View: M_LOAD_HISTORY_INFO
Parameter: load_monitor_max_samples
Description: Defines a maximum number of samples of load monitoring data.
For the default settings, load_monitor_max_samples = 100000 and
load_monitor_granularity = 10000 milliseconds, the HANA System can
collect load monitoring data for about 11 days.
Note: Avoid large values to save memory.
Values: Positive integer (greater than 10)
Default: 100000
Related information: System View: M_LOAD_HISTORY_INFO

Parameter: memory_tracking
Description: Enables (on) / disables (off) statement memory tracking.
For performance reasons, the statement memory tracking is disabled by
default.
If enabled together with system resource tracking (enable_tracking = on),
the memory usage for statement execution will be measured periodically
and the values can be displayed in corresponding system views and/or
trace files.
To use statement memory limit, set the parameter memory_tracking to
on.
Values: on, true
off, false
Default: off, false
Related information: Set a Statement Memory Limit (Admin Guide)
SAP Note 1999997
Parameter: service_thread_sampling_monitor_max_sample_lifetime
Description: Sets a memory lifetime of samples collected by the service thread monitor
in seconds.
When set to 0, the monitor continues sampling, but does not save the
information.
Default: 7200 (seconds = 2 hours)
Parameter: service_thread_sampling_monitor_max_samples
Description: Sets a maximum number of samples that the service thread monitor can
keep in memory.
When set to 0, the monitor continues sampling, but does not save the
information.
When the number of samples in memory reaches the specified limit, the
oldest samples are removed from memory.
The samples are removed from memory even if the memory lifetime is
less than the maximum value specified by the parameter
service_thread_sampling_monitor_max_sample_lifetime.
Default: 1500000

Parameter: service_thread_sampling_monitor_max_samples
Parameter: service_thread_sampling_monitor_sample_interval
Description: Sets a sampling interval for the service thread monitor in seconds.
Default: 1 (second)
Parameter: service_thread_sampling_monitor_thread_detail_enabled
Description: Enables (on) / disables (off) the collection of thread detail information in
the service thread monitor.
Values: true, false
Default: false
System monitoring view
M_SERVICE_THREAD_SAMPLES
Section: spark_configuration
This section contains parameters that are related to configuring HANA for mutual SSL
authentication with a Spark controller. The Spark controller is a server side communication
component deployed in a Hadoop cluster, providing access to Spark/Hadoop data. The
HANA System acts as a client side communication component and connects to the Spark
controller.
Parameter: sslKeyStore
Description: Sets the file system location of the key store file in PSE format, which holds
a single key and certificate chain for SAP HANA to communicate with all
Spark controllers.
Default: $SECUDIR/sparksql_ks.pse
When the default settings are unchanged, the environment variable
$SECUDIR is replaced with a specific value at HANA System restart.
Related information: Configure SSL Mode (Admin Guide)

Parameter: sslTrustStore
Description: Sets the file system location of the trust store file in PSE format, which
holds certificates for all Spark controllers that it connects to.
Default: $SECUDIR/sparksql_ts.pse
When the default settings are unchanged, the environment variable
$SECUDIR is replaced with a specific value at HANA System restart.
Parameter: sslValidateCertificate
Description: Enables (true) / Disables (false) validation of the certificate from the Spark
Controller during communication.
Values: true, false
Default: true or false
Parameter: sslValidateHostNameInCertificate
Description: Enables (true) / Disables (false) validation of the hostname in the
certificate from the Spark Controller during communication.
The validation takes only effect when the parameter sslValidateCertificate
has been set to true.
Values: true, false
Default: True

Section: storage
This section contains parameters that are related to SAN configuration.
See also SAP HANA Fiber Channel Storage Connector Admin Guide
Parameter: enable_ets
Description: Enables (true) / Disables (false) the storage connector API for SAP HANA
Accelerator for SAP ASE (ETS).
When set to true, SAP HANA Accelerator for SAP ASE resides on SAN using
the storage connector API.
When set to false, SAP HANA Accelerator for SAP ASE data resides on an
NFS share.
Values: true, false
Default: true
Parameter: enable_extended_storage
Description: Enables (true) / Disables (false) the storage connector API for Dynamic
Tiering / Extended Storage data.
When set to true, dynamic tiering data resides on SAN using the storage
connector API.
When set to false, dynamic tiering data resides on an NFS share.
Values: true, false
Default: true
Parameter: ha_provider
Description: Sets a name of an HA (High Availability) provider script.
Values: Name of python script (*.py)
Parameter: ha_provider_path
Description: Sets a path of an HA (High Availability) provider script.

Parameter: partition_<partition number>_<usage type>__<param name>

Description: The partition number (PN) is a positive integer that refers to a HANA
partition or an asterisk “*”.
The usage type can be “data”, “log”, or asterisk “*”.
The fcClient supports the parameters:
 wwid (world wide identifier) or alias
 prType
 mountOptions.
The fcClientLVM supports the parameters:
 lvmname
 prType
 mountOptions
Note: Use a double underscore (__) between <usage type> and <param
name>
Values: The values are parameter-specific:
 partition_[<PN>|*]_[data|log]__wwid=<name of LUN>
 partition_[<PN>|*]_[data|log]__alias = <user friendly alias of
LUN>
 partition_[<PN>|*]_[data|log]__lvmname = <device name
<volumegroup_name>-<logical volume> under /dev/mapper>
 partition_*_*__prType = [5|6] controls how persistent
reservations influence accessibility of devices to other hosts
(5=denies only external write access, but allows read, 6 denies
external read/write access).
 partition_[*]_[data|log]__mountOptions = <mount options> is
mapped to the command
“mount <mount options> <device> <path>”, for example, <mount
options> = “-t xfs”
Default: Not set
Related information: SAP HANA Fiber Channel Storage Connector Admin Guide (SCN)

Section: system_information
This section contains parameters that are related to system information.
Parameter: usage
Description: Defines a database usage type.
Values: production
test
development
custom
Default: custom
Related information: Configure System Usage Type (Admin Guide)
Section: system_replication
This section contains parameters that are related to system replication.
Parameter: datashipping_logsize_threshold
Description: Sets a minimum total size of log buffers in bytes that the secondary system
expects to receive from the primary system between two datashipping
requests, which the secondary system sends to the primary system.
Log buffers are memory areas that store information about changes made
to the database. Log buffers are written to log segment files on disks after
a commit operation occurs. The log information is necessary for database
recovery.
In response to receiving a data shipping request, the primary system
invokes a transfer of delta data pages that have changed after the last data
shipping.
When the total size of received log buffers exceeds the specified threshold
size, the secondary system sends a new data shipping request.
When the time interval datashipping_min_time_interval has passed first,
the data shipping request is sent even before the threshold size
datashipping_logsize_threshold has been reached.
When set to 0, the next data shipping starts immediately after the last has
finished.
System in replication The parameter has to be set on the secondary system.
scenario:
Default: 5368709120 = 5*1024*1024*1024 (5 GB)
Restart required: No restart or re-connect is necessary.
Related information: System Replication Configuration Parameters (Admin Guide)

Parameter: datashipping_min_time_interval
Description: Sets a minimum time interval that the secondary system waits between
two data shipping requests, which the secondary system sends to the
primary system.
In response to receiving a data shipping request, the primary system
invokes a transfer of delta data pages that have changed after the last data
shipping.
When the specified time interval elapsed after the last data shipping
request, the secondary system sends the next data shipping request.,
When the threshold size datashipping_logsize_threshold has been reached
first, the data shipping request is sent before the time interval
datashipping_min_time_interval elapsed.
When set to 0, the next data shipping starts immediately after the last has
finished.
scenario:
Restart required: No restart or re-connect is required.
Parameter: datashipping_snapshot_max_retention_time
Description: Sets a maximum retention time of the active snapshot in the primary
system in minutes after the snapshot information has been successfully
shipped to the secondary system.
Inactive snapshots, which are currently used in data shipping, are not
dropped even when data shipping takes longer than the specified
retention time.
Inactive snapshots are marked as active after the snapshot information
has been successfully shipped.
Active snapshots that are older than the specified retention time are
automatically dropped in the primary system.
When set to 0, active snapshots are immediately dropped after data
shipping completed.
The retention of the last snapshot may reduce the time of failback
operations in the primary system because full data shipping is not
necessary and only delta data shipping is required.
A drawback to snapshot retention is a higher consumption of memory and
disk space.
System in replication The parameter has to be set on the primary system.
scenario:
Default: 120

Parameter: datashipping_snapshot_max_retention_time
Parameter: enable_data_compression
Description: Enables (true) / disables (false) compression of data pages in the primary
system before sending them over the network to the secondary system,
which decompresses the data pages it receives.
A drawback to sending compressed data pages is that it requires
additional time and processing power for compression and
decompression. This can result in worse data shipping performance, in
particular in environments with a fast network.
scenario:
Values: true, false
Default: false
Restart required: No, but the secondary system has to re-connect to the primary system in
order to activate the parameter change. A re-connect can be forced by
restarting the secondary system.
Data and Log Compression (Admin Guide)
Parameter: enable_full_sync
Description: Enables (true) / disables (false) the full synchronization (sync) option in
synchronous system replication mode.
When set to true, the system replication operates in synchronous mode
with full sync option. In that case, a log write operation is successful, when
the log buffer has been written to the log segment files on disks of the
primary and secondary system. When the secondary system is
disconnected, the primary system suspends processing write transactions
until the connection to the secondary system is re-established.
When set to false, the system replication operates in synchronous mode.
The log write operation succeeds when the log buffer has been written to
the log segment files on disks of the primary and secondary system. When
the connection to the secondary system is lost, the primary system
continues processing write transactions and writes changes only to the
local log segment file.
The connection to the secondary system is re-established when the
secondary system is restarted. To enable synchronous system replication,
the system replication is invoked with the option “—mode=sync” of the
command “hdbnsutil”.

Parameter: enable_full_sync
scenario:
Values: true, false
Default: false
System Replication Details (Admin Guide)
Parameter: enable_log_compression
Description: Enables (true) / disables (false) compression of log buffer pages on the
primary system before sending them over the network to the secondary
system, which decompresses the received log buffer pages.
The drawback to sending compressed log buffer pages is that it requires
additional time and processing power for compression and
decompression.
This can result in worse log buffer shipping performance, in particular in
environments with a fast network.
scenario:
Values: true, false
Default: false
Data and Log Compression (Admin Guide)
Parameter: enable_log_retention
Description: Enables (on) / Disables (off) log retention / Sets automatic log retention
(auto).
Log retention is only relevant when the operation mode of the secondary
system was set to “log replay”. See the description of parameter
“operation_mode”.
Note: For an optimized failback from the old secondary (new primary)
system to the old primary (new secondary) system, explicitly enable (on)
log retention in both the primary and secondary systems.
When log retention is enabled (on) in the primary system and the
secondary system is disconnected from the primary system, the primary
system will protect free log segments against re-use until they are shipped

to the secondary system. Protected log segments get the status
“RetainedFree”.
When a log segment was closed before the last savepoint operation and
not yet backed up, it has the status “Truncated”. When a log segment was
closed after the last saveopoint operation and already backed up, it has
the status “BackedUp”. When a log segment was closed before the last
savepoint operation and backed up, it gets the status “Free” or
“RetainedFree”. The status “Free” is assigned when the secondary system
is connected, and the status “RetainedFree”, when not.
After a re-connect, log buffer shipping continues to transfer log buffers
missing in the secondary system When a log segment was completely
shipped from the primary system to the secondary system, its status
changes to “Free”.
Log retention helps to avoid a re-initialization with expensive full data
shipping since the primary system can transfer protected log segments
that are missing in the secondary system.
When log retention is disabled (off) in the primary system and when the
secondary system is disconnected, the primary system can overwrite free
log segments.
In this case, when the secondary system re-connects to the primary
system, a re-initialization with expensive full data shipping is necessary
because some log segments are missing in both the secondary and primary
systems.
When the automatic mode (auto) is set in the primary system, there are
two cases:
When the secondary system has operation_mode=”logreplay”, the log
retention is enabled, but when the
operation_mode=”delta_datashipping”, the log retention is disabled.
Log retention in the secondary system optimizes failback from the old
secondary (new primary) system to the old primary (new secondary)
system.
When log retention is enabled (on) in the secondary system, and a failover
swaps the roles of primary and secondary systems, log retention will
protect free log segments in the old secondary (new primary) system as
described above.
When log retention is disabled (off) in the secondary system and a failover
takes place, free log segments of the old secondary (new primary) system
can be overwritten.
System in replication The parameter can be set in the primary system and in the secondary
scenario: system.
Values: on: primary and secondary system
off: primary and secondary system
auto: only primary system
Default: Auto

Parameter: keep_old_style_alert
Description: Enables (true) / disables (false) alerting that is backwards compatible with
HANA Revisions before SPS 09.
When set to true, the statisticsserver alert 21 is raised when closed system
replication connections and configuration parameter mismatches occur.
When set to false, separate alerts are raised for each of both events.
scenario:
Values: true, false
Default: True
System Replication Alerts (Admin Guide)
Parameter: logshipping_async_buffer_size
Description: Sets a maximum size of the asynchronous log shipping buffer in bytes in
asynchronous system replication mode.
The asynchronous log shipping buffer is a transient memory buffer, which
temporarily stores copies of log buffers before sending them to the
secondary system.
A log writer process copies closed log buffers to the asynchronous log
shipping buffer.
An asynchronous sender process reads the log buffers from the
asynchronous log shipping buffer to send them to the secondary system
over a network.
The asynchronous log shipping buffer is useful to handle peak load
situations when log information is generated faster in the primary system
than sent to the secondary system.
When the asynchronous log shipping buffer is full, the parameter
logshipping_async_wait_on_buffer_full controls the behaviour of the
primary system.
To select asynchronous system replication, the system replication is
invoked with the option “—mode=async”. See the output of the command
“hdbnsutil”.
scenario:
Default: 67108864 = 64*1024*1024 (64 MB)

Parameter: logshipping_async_buffer_size
Parameter: logshipping_async_wait_on_buffer_full
Description: Controls the behavior of the primary system in asynchronous system
replication mode when the asynchronous log shipping buffer is full. The
asynchronous log shipping buffer temporarily stores log buffers before
sending them to the secondary system.
When set to true and when the asynchronous log shipping buffer is full,
the primary system waits until enough memory space has been freed from
the asynchronous log shipping buffer so that new log buffers can be
copied into it.
When more log information is generated than can be sent over the
network, waiting for free memory space can slow down the primary
system.
When set to false and when the asynchronous log shipping buffer is full,
the system replication connection to the secondary system will be closed
temporarily to avoid a performance impact on the primary system.
After the time interval defined by the parameter reconnect_time_interval
has elapsed, the secondary system tries to re-connect and synchronize
with the primary system.
To select asynchronous system replication, the system replication is
invoked with the option “—mode=async”. See the output of the command
“hdbnsutil”.
scenario:
Values: true, false
Default: true
Parameter: logshipping_max_retention_size
Description: Sets a maximum size of free log segments in megabytes that log retention
protects against re-use in the primary system when the secondary system
disconnects. Protected log segments have the status “RetainedFree”.
The parameter logshipping_max_retention_size only takes effect when log
retention is enabled (on, auto) in the primary system.
See the description of the parameter “enable_log_retention”.

Parameter: logshipping_max_retention_size
When set to a positive value greather than 0 in the primary system and the
secondary system is disconnected, the size of protected log segments can
grow until the specified maximum size is reached or the HANA System
runs into a log full situation. In this case, the protected log segments can
be overwritten so that the primary system does not stand still. After a re-
connect, the secondary system must start a full datashipping to
synchronize up with the primary system.
When set to 0 in the primary system and the secondary system is
disconnected, log segments are not re-used until a log full situation results
in a standstill of the primary system. When the reason for the log full
situation has been resolved, transaction processing can continue. After a
re-connect, the secondary system, however, can synchronize (up) with the
primary system much faster.
In the secondary system, the parameter logshipping_max_retention_size
can control the size of protected log segments when log retention is
enabled (on) in the secondary system and a failover swaps the roles of
primary and secondary systems.
System in replication The parameter can be set in the primary system and in the secondary
scenario: system.
Default: 1048576 ( = 1 terabyte )
Log Retention (Admin Guide)
Parameter: logshipping_timeout
Description: Sets a maximum wait time for sending a log buffer from the primary to the
secondary system.
Log buffers are memory areas that store information about changes made
to the database. Log buffers are written to log segment files on disks after
a commit operation occurs. The log information is necessary for database
recovery.
The parameter applies to all system replication modes: synchronous,
synchronous in memory, and asynchronous.
In the synchronous and synchronous in memory system replication modes,
the secondary system sends a confirmation back to the primary system
after receiving the log buffer.
In the asynchronous system replication mode, the operating system layer
of the primary system confirms that the log buffer has been sent.
When the specified wait time elapsed after sending a log buffer without
receiving a confirmation, the primary system closes the system replication
session/connection with the secondary system.
After the secondary system has disconnected from the primary system in
the synchronous system replication mode, the behaviour depends on the
parameter enable_full_sync:

Parameter: logshipping_timeout
When the parameter enable_full_sync is set to false, write transactions
are only processed in the primary system until the secondary system re-
connects and initiates new data shipping.
When the parameter enable_full_sync is set to true, the primary system
suspends processing write transactions until the connection to the
secondary system has been re-established.
See also the parameter reconnect_time_interval.
To select a system replication mode, the system replication is invoked with
the corresponding option “—mode=sync|syncmem|async”. See the
output of the command “hdbnsutil”.
scenario:
Default: 30 (seconds)
Parameter: operation_mode
Description: Sets a default operation mode of the secondary system during system
replication.
Note: The operation mode can only be changed in the secondary system
by submitting the command “hdbnsutil -sr_register
--operationMode=”.
When the command “hdbnsutil –sr_register” does not specify the “—
operationMode”, the value of the parameter operation_mode takes
effect.
When set to “delta_datashipping”, the system replication uses both data
and log shipping.
Data shipping comprises initial data shipping when system replication
starts, and periodically triggered delta data shipping.
Log shipping transfers log buffers from the primary to the secondary
system, where they are saved to disk.
After a delta data shipping completes, a savepoint is executed in the
secondary system.
When a log segment in the secondary system was closed before the last
savepoint operation and not yet backed up, it has the status “Truncated”.
The secondary system receives notifications about log backup operations
from the primary system to control corresponding operations in the
secondary system.
When a log segment in the secondary system was closed after the last
savepoint operation and the secondary system received a notification that
the corresponding log segment was backed up in the primary system, the
log segment in the secondary system gets the status “BackedUp”.
When a log segment was closed before the last savepoint operation in the
secondary system and receives the corresponding log backup notification

Parameter: operation_mode
from the primary system, the log segment in the secondary system gets
the status gets the status “Free”.
The secondary system does not execute delta merge operations on
columnstore tables. But delta data shipping transfers merged column
store tables from the primary to the secondary system.
The operation mode “delta_datashipping” is available since SPS 05.
When set to “logreplay”, system replication uses an initial data shipping
and continues only log buffer shipping, but no delta data shipping.
The primary system sends log buffers to the secondary system, which
replays the received log buffers and saves them to disk.
The secondary system receives notifications about savepoint, log backup,
and delta merge operations from the primary system to control
corresponding operations in the secondary system.
The operation mode “logreplay” is available since SPS 11.
scenario:
Values:  delta_datashipping
 logreplay
Default: delta_datashipping
Restart required: No restart of the primary system, but restart of the secondary system with
the following command sequence:
1) Stop secondary system
2) hdbnsutil –sr_unregister
3) hdbnsutil –sr_disable
4) hdbnsutil –sr_enable
5) hdbnsutil –sr_register
6) Start secondary system
Parameter: preload_column_tables
Description: When set on the primary system, the parameter enables (true) / disables
(false) collecting table preload information. The table preload information
describes which columnstore table columns are loaded into memory. The
table preload information is included in the snapshot that is shipped to the
secondary system.
When set on the secondary system, the parameter enables (true) /
disables (false) receiving of the table preload information from the
primary system and loading of the corresponding columnstore tables in
the secondary system
System in replication The parameter can be set on the primary system and on the secondary
scenario: system.
Values: true, false
Default: true

Parameter: preload_column_tables
Validity: All SAP HANA revisions.
Parameter: reconnect_time_interval
Description: Sets a time interval in seconds at which the secondary system periodically
tests if the system replication connections to the primary system are alive.
When the connections have been closed, the secondary system tries to re-
connect to the primary system.
scenario:
Values: Positive integer.
Section: system_replication_communication
This section contains parameters that are related to communication properties of system
replication.
Parameter: allowed_sender
Description: Defines one or more allowed sending systems in system replication
communication.
When a receiving system gets a communication request from a system
that is not in the pre-defined list of sending systems, the receiving system
returns a response that the connection is not allowed.
When the trace component allowed_sender is set to info in the receiving
system, a trace entry about the unsuccessful communication attempt is
recorded.
System in replication The parameter has to be set in the primary system.
scenario:
Values: A list of one or more IP addresses and/or CIDR notations separated by
commas
Restart required: No, takes effect after the next re-connect of the secondary system.
Validity: HANA Revisions >= 70

Parameter: enable_ssl
Description: Enables / Disables SSL communication for source and/or target replication
channels in a system replication scenario.
In a two-tier configuration, there is one source system and one target
system.
In a three-tier configuration, there is one source system, one target and
source system, and one target system.
An SSL communication between a source and target system requires
corresponding source and target replication channels.
When set to “off”, SSL communication is disabled for both source and
target replication channels.
When set to “on”, SSL communication is enabled for both source and
target replication channels.
When set to “source”, SSL communication is only enabled for the source
replication channels, but not for the target replication channels.
When set to “target”, SSL communication is only enabled for target
replication channels, but not for the source replication channels.
SSL communication must be enabled for both communication partners,
otherwise the SSL communication will fail.
System in replication The parameter has to be set on both the primary and secondary systems
scenario: of each replication channel.
Values: off, on, source, target
Default: off
System in replication The parameter has to be set on the primary system and on the secondary
scenario: system.
.internal to select all network interfaces that are listed in
[system_replication_hostname_resolution]
Default: .global

Section: system_replication_hostname_resolution
This section contains mappings of IP addresses to hostnames in a system replication
scenario.
Parameter: <system_replication_ip_address>
Maps IP addresses of the system replication network to virtual hostnames
of the other system in a system replication scenario to enable
communications between hosts of the primary system and hosts of the
secondary system.
When the parameter listeninterface in the section
[system_replication_communication] has been set to .internal, the
internal IP addresses specified in the section
[system_replication_hostname_resolution] will be used.
When the parameter listeninterface in the section
[system_replication_communication] has been set to .global, …
Note: The mapping must be defined before the secondary system is
registered with the primary system using hdbnsutils –sr_register.
System in replication On the primary system, specify virtual hostnames of the secondary system
scenario: and corresponding IP addresses of the system replication network
On the secondary system, specify virtual hostnames of the primary system
and corresponding IP addresses of the system replication network.
Values: <virtual_hostname>
Default: N/A
Related information: Configuring Hostname Resolution for SAP HANA System Replication (Admin
Guide)

Section: table_placement
This section contains parameters that are related to table placement.
Parameter: method
Description: Controls the default behavior of table placement and redistribution.
When set to 0, row store and column store tables can be created on any
node or moved to any node
When set to 2, row store tables are created on or moved to the master
node during table redistribution. Column store tables are created on or
moved to the master node only when the table name starts with the prefix
‘/’ and continues with the database schema name as defined by the
parameter bw_schema, and when the table is not partitioned. All other
column store tables are created on or moved to slave nodes.
As of Revision 80, the SAP HANA system can use configurable rules for the
placement and redistribution of column store tables. The rules are stored
in the table _SYS_RT.TABLE_PLACEMENT. Until SPS 09, when the rules are
not defined in the table _SYS_RT.TABLE_PLACEMENT, the SAP HANA
System applies the default behavior based on the specified parameter
method.
Values: 0 and 2
Default: 0
Validity: All SAP HANA revisions < 100
Obsolete as of SPS 10.
Related information: Table Placement (Admin Guide)
Table Distribution in SAP HANA (Admin Guide)
Parameter: same_num_partitions
Description: Controls the behavior of table placement and redistribution in relation to
table classifications, which are stored in the table
_SYS_RT.TABLE_GROUPS. There is an entry in this table for all tables for
which a group type, subtype, or group name is specified.
When set to true, all tables with the same group name have the same
number of level 1 partitions. The number of partitions is determined by
the table with the largest number of records within the group.
When set to false, the number of level 1 partitions is independent of other
tables with the same group name.
Values: true, false
Default: True

Section: threads
This section contains parameters that are related to threads.
Parameter: default_stack_size_kb
Description: Sets a default stack size for threads in kilobytes.
Values: Positive integer ( 128 .. 16384 = 128 kB .. 16 MB)
Default: Linux on Power. 1152 kB (SAP HANA revisions >= 91)
Linux on Intel: 1024 kB (All SAP HANA revisions)
Restart required: No (Applies to newly created worker threads.)
Parameter: worker_stack_size_kb
Description: Sets a default stack size for worker threads in kilobytes.
Values: Positive integer ( 128 .. 16384 = 128 kB .. 16 MB)
Default: Linux on Power. 1152 kB (SAP HANA revisions >= 91)
Linux on Intel: 1024 kB (All SAP HANA revisions)
Restart required: No. (Applies to newly created worker threads.)
Section: trace
This section contains parameters that are related to tracing.
Parameter: alert
Description: Sets the trace level of the alert trace.
Trace messages of the specified trace level and higher are duplicated into
the alert trace.
For example, when set to warning, the alert trace contains messages at
the trace levels Fatal, Error, and Warning
Values: error, warning, info, debug
Default: error
Parameter: alertfilename
Description: Sets a name prefix of the corresponding alert trace file
Note: Do not change the parameter

Values: String
Default: <service_name>_alert, for example, indexserver_alert

Parameter: alertfilename
Parameter: compressioninterval
Description: Sets the scan interval of time for the trace compression thread in seconds
(0 = disabled).
The trace compression thread scans the trace directory at regular intervals
of time to find trace files that need compression.
When set to 0, the trace compression thread is disabled.
Parameter: default
Description: Sets the default trace level for all trace components.
Trace messages of the specified trace level are written to the trace file.
For example, when set to Warning, the trace contains messages at the
trace levels Fatal, Error, and Warning
Values: error, warning, info, debug
Default: error
Parameter: filename
Description: Sets a name prefix of the corresponding trace file
Note: Do not change the parameter
Values: String
Default: <service_name>, for example, indexserver
Parameter: flushinterval
Description: Sets the time interval at which memory buffers for trace information are
flushed to disk in seconds (0 = disabled).
When set to 0, the trace information is not cached in memory, but directly
written to disk.

Parameter: flushinterval
Parameter: formatter
Description: Sets the type of formatter to print the trace header information.
Values: updatetid, statementtid, connection
Default: updatetid
Parameter: maxalertfilesize
Description: Sets the size of the alert file in bytes (0 = unlimited).
Default: 10000000 (approximately 10 megabytes)
Parameter: maxfiles
Description: Sets a maximum number of trace files (0 = trace file rotation disabled).
When the specified maximum number of files is reached, the next time a
new file is created, the first file is deleted, and so on (trace file rotation).
Values: Positive integer or zero (0 to 999)

Default: 10
Related information Configure Trace File Rotation (Admin Guide)
Description: Sets a maximum size of an individual trace file in bytes (0 = unlimited).
When a trace file reaches the specified maximum file size, it is closed, and
a new file created.

Default: 1000000000 (approximately 1 GB)
1073741824 = 1024 * 1024 * 1024 (1 GB)
Parameter: python_output
Description: Enables (true)/disables (false) the redirection of the output of embedded
python scripts from stdout and stderr to a trace file <service>.python.log.
Values: true, false
Default: false
Related information SAP Note 1888573
Parameter: saptracelevel
Description: Sets a trace level for SAP Netweaver kernel components that are
integrated in the HANA System kernel.
The lowest trace level is 0 and the highest trace level is 3.
Values: 0 (lowest), 1, 2, 3 (highest)
Default: 0
Validity: All SAP HANA
Section: traceprofile%
This section contains parameters that are related to tracing using a specific profile.
Description: Sets an application user to filter trace messages for a specific profile.
Specific profiles are used for user-specific and end-to-end traces.
Values: String
Default: N/A

Parameter: maxfiles
Description: Sets a maximum number of trace files for a specific trace profile (0 = trace
file rotation disabled).
When the specified maximum number of files is reached, the next time a
new file is created, the first file is deleted, and so on (trace file rotation).
Values: Positive integer (0 to 999) or zero
Default: 10
Description: Sets a maximum size of an individual trace file for a specific profile in bytes
(0 = unlimited).
When a trace file reaches the specified maximum file size, it is closed, and
a new file created.
Default: 1000000000 (approximately 1 GB)
Parameter: sql_user
Description: Sets a HANA SQL user to filter trace messages for a specific profile.
Values: String
Default: N/A

3 Filename: attributes.ini
This configuration file describes parameters for the Attribute Engine.
Section: global
This section contains parameters that are related to each service of the landscape
Parameter: inverted_index_verification_after_load
Description: Enables (true)/disables (false) verification of index information associated
with uncompressed columns of columnstore tables. The verification is
performed after loading the corresponding columns into memory.
The inverted index verification is only effective when the parameter
[global] runtime_structure_persistence has been set to true.
Values: true, false
Default: false
Parameter: runtime_structure_persistence
Description: Enables (true) / disables (false) loading of runtime structure information of
columnstore tables from persistence into memory.
The runtime structure information comprises index information and SQL
optimizer statistics, which are associated with corresponding columns. The
parameter only applies to non-paged columns which are loaded as one
entity into memory.
When set to true, the runtime structure information is read from
persistence rather than being generated at a column load so that the
system startup time is reduced at the expense of increased disk space
consumption.
When set to false, the runtime structure information is generated after
each column load.
Values: true, false
Default: true
Related information: SAP Note 1976994 (Revision 70)

4 Filename: daemon.ini
This configuration file describes parameters for the daemon service.
Section: compileserver
This section contains parameters that are related to the compileserver service.
Parameter: affinity
Description: See the section [indexserver].
Section: indexserver
This section contains parameters that are related to the indexserver service.
Parameter: affinity
Description: Selects a subset of available logical core indexes to define an affinity of the
hdbindexserver process to the selected logical cores (0 = ignored).
When set to 0, no affinity is set for the indexserver process.
The subset can comprise comma-separated single indexes and index ranges,
the ranges having a start index, hyphen, and an end index.
For example, in a system with 32 logical cores, the affinity value '1-7, 17-23'
assigns logical cores with indexes 1 to 7 and 17 to 23 to the hdbindexserver
process.
The distribution of logical cores to physical sockets and cores depends on the
hardware system and architecture.
To retrieve the hardware topology on Linux, use the command “numactl –
hardware” or check contents of the directories /sys/devices/system/cpu and
/proc/cpuinfo.
When set to 0, there is no affinity for the hdbindexserver process.
Values: Subset of positive integers between 1 and the maximum number of available
logical cores where multiple integers are separated by commas and hyphens.
Default: 0
Related information: Controlling CPU Consumption (Admin Guide)

Section: indexserver.c
This section contains parameters that are related to the additional indexserver services.
Parameter: affinity
Parameter: instanceids
Description: Specifies a list of identifiers for additional indexserver services in a single
database container at HOST level.
The list of instance identifiers starts with a value greater than or equal to 40,
each subsequent instance identifier is separated by a comma and
incremented by 2; the highest identifier is less than 60.
The identifiers determine the last two digits of the port number.
Example: When the HANA instance identifier is 02 and the parameter
instanceids have the value “40,42,44”, three indexserver services are added,
which have the corresponding port numbers 30240, 30242, and 30244.
Values: Comma-separated list of one or more instance identifiers (40 … 58)
Related information: Add a Service Before Database Copy (Admin Guide)
Section: indexserver.<tenandSID>
This section contains parameters that are related to the additional indexserver services of
tenant database containers.
Parameter: affinity
Section: nameserver
This section contains parameters that are related to the nameserver service.
Parameter: affinity
Section: preprocessor
This section contains parameters that are related to the preprocessor service.
Parameter: affinity

Section: sapwebdisp / webdispatcher

This section contains parameters that are related to the webdispatcher service.
Parameter: affinity
Section: scriptserver
This section contains parameters that are related to the scriptserver service.
Parameter: affinity
Section: statisticsserver
This section contains parameters that are related to the statisticsserver service.
Parameter: affinity
Section: xsengine
This section contains parameters that are related to the xsengine service.
Parameter: affinity

5 Filename: esserver.ini
This configuration file describes parameters for extended storage.
Section: row_engine
This section contains parameters that are related to the rowstore engine configuration.
Parameter: bulk_inserts_as_load
Description: Controls whether data insert into extended storage tables uses LOAD
TABLE or INSERT statements/commands.
When set to true, use LOAD TABLE statement/command.
When set to false, use INSERT statement/command.
Values: true, false
Default: true
Parameter: bulk_load_as_binary
Description: Controls whether the data file for the LOAD TABLE statement/command is
a text file or a binary file.
When set to true, the data file is binary.
When set to false, the data file ist text.
Values: true, false
Default: true
Parameter: execution_strategies
Description: Controls the location of query processing
Values: “local”: Dynamic Tiering processes a first part of the query and HANA a
second part
“remote”: HANA sends table contents to Dynamic Tiering, which processes
the complete query
“auto”: a cost-based optimizer decides between “local” and “remote”.
Default: auto

Parameter: keep_shared_memory_over_restart
Description: Enables (true) / Disables (false) keeping rowstore data in memory after a
shutdown of the HANA System to accelerate a subsequent restart.
When set to true, the HANA System will keep the rowstore data in shared
memory provided that certain technical preconditions are fulfilled.
When set to false, all rowstore data have to be reloaded from the
persistent storage during the restart.
Values: true, false
Default: True
Parameter: keep_shared_memory_over_restart_timeout
Description: Defines a time interval in seconds to keep rowstore data in memory after a
shutdown provided that the parameter
keep_shared_memory_over_restart is set to true.
When the specified time interval elapsed after a shutdown, the shared
memory will be released, and at the next restart, all rowstore data have be
loaded from the persistent storage.
Default: 3600 (seconds = 1 hour)

6 Filename: executor.ini
This configuration file describes parameters for the columnstore plan executor.
Section: pythontrace
This section contains parameters that are related to pythontrace configuration.
Parameter: level
Description: Sets for the tracing of Python API calls a filter on trace groups and
functions. If many, they are separated by commas.
Example of a comma-separated list of trace groups:
admin,indexing,searching
Values: When set to “all”, all trace groups are included.
Specific trace groups are “admin”, “datamining”, “indexing”,
“planningengine”, “python”, “searching”, “trexviadbsl”, “xse_web
Default: all
Parameter: trace
Description: Enables (on, yes, true)/disables (off, no, false) tracing of Python API calls,
which writes executed plans into a dedicated trace file. The plans are
represented as python program code, which can be used for analysis and
debugging.
Values: on, yes, true
off, no, false
Default: off, no, false
Parameter: trace_errors
Description: Enables (on, yes, true)/disables (off, no, false) error tracing of Python API
calls, independent of filters specified by the parameters level and
trace_indexes.
Values: on, yes, true
off, no, false
Default: off, no, false

Parameter: trace_indexes
Description: Sets for the tracing of Python API calls a table name filter in TREX notation.
If many tables, the names are separated by commas.
Values: One or more table names in TREX notation, if many, separated by commas.
Example: MYSCHEMA:MYTABLE
Parameter: trace_user
Description: Sets for the tracing of Python API calls a user name filter, which can be an
application user or a HANA SQL user, as shown by the HANA
Administration tools and System Views.
Only Python API calls from system threads that are associated with the
specified user name are written to the trace file.
Values: Application user name or HANA SQL user name
Parameter: tracefile
Description: Specifies the name of the trace file of Python API calls.
The trace file is written to the trace directory
$DIR_INSTANCE/$VTHOSTNAME/trace
Values: File name (for SAP HANA Revisions >= 94)
Prefix “trace/” and file name (for SAP HANA Revisions < 94)
Environment variables are not supported except for $HOST, $PORT, $PID,
and $COUNT.
Default: extrace.py
(for SAP HANA Revisions >= 94)
trace/extrace.py
(for SAP HANA Revisions < 94)

7 Filename: indexserver.ini
This configuration file describes parameters for the indexserver service.
This section contains parameters that are related to authentication configuration.
Parameter: saml_service_provider_name
Description: Defines the name under which the HANA server instance will act as SAML
(Security Assertion Markup Language) service provider.
Related information: Configure Outbound SSO with Assertion Tickets (Admin Guide)
Parameter: SapLogonTicketTrustStore
Description: Sets an absolute file path to the SAPLogon Ticket trust store file, which
must contain exactly one certificate.
Caution: Do not use environment variables in the file path.
Multi-tenant database container systems:
Default: The SAP HANA system sequentially tests which cryptographic service
providers have been installed.
1) If the cryptographic library CommonCryptoLib has been found, the
default value of this parameter is $SECUDIR/saplogon.pse and the
trust store file must be encoded in PSE format.
2) If the SAP Cryptographic library has been detected, the default value
is the same as
in 1). The SAP Cryptographic Library is obsolete and the
CommonCryptoLib is recommended.
3) If OpenSSL is used as cryptographic service provider, the default value
of this parameter is $HOME/.ssl/saplogon.pem and the trust store file
must be encoded in PEM format.
Related information: Configure Outbound SSO with Assertion Tickets (Admin Guide)
Configure the Trust Store for SAP Logon Tickets and Assertions (Admin
Guide)
SAP Note 1927949

Parameter: session_cookie_for_kerberos
Description: Enables (yes) / Disables (no) a session cookie mechanism for Kerberos
Single Sign-On (SSO).
When set to yes, a session cookie mechanism allows the HANA System to
control the lifetime of a session cookie, which replaces the function of the
original Kerberos ticket granting ticket (TGT).
For a long running connection in a distributed system, the lifetime of the
original TGT may not be long enough and applications can be disrupted.
When set to no, the original Kerberos SSO mechanism is used.
Values: yes, no
Default: yes
Section: authorization
This section contains parameters that are related to authorization configuration.
Parameter: internal_support_user_limit
Description: Sets a maximum number of users whom the internal support role
(SAP_INTERNAL_HANA_SUPPORT) can be granted at the same time.
When set to 0, no user is allowed to get the internal support role.
Default: 1
Section: cache
This section contains parameters that are related to cache configuration.
Parameter: resultcache_clear_reconfig
Description: Enables (yes) / Disables (no) clearing the query result cache on
configuration changes.
Values: yes, no
Default: no
Parameter: resultcache_enabled
Description: Enables (yes)/disables (no) the query result cache.
Values: yes

Parameter: resultcache_enabled
no
Default: no
Parameter: resultcache_maximum_value_size_in_bytes
Description: Sets a maximum size of a result in bytes to be written to the query result
cache (0 = disabled).
When the result size is larger than the specified maximum value, the
result data will not be cached.
When set to 0, the result size takes no effect on caching.
Values: Positive integer and zero.
Default: 1048576 (bytes = 1 megabyte).
Parameter: resultcache_minimum_query_execution_time_in_milliseconds
Description: Sets a minimum query execution time in milliseconds to write a result to
the query result cache (0 = disabled).
When the execution time is shorter than the specified minimum value, the
result data will not be cached.
When set to 0, the execution time takes no effect on caching.
Default: 100 (ms)
Parameter: resultcache_request_timeout_in_milliseconds
Description: Sets a timeout for requests between query result caches on separate
nodes in milliseconds in a distributed environment (0 = only requests on
the same node)
When a first query result cache sends a request to a second query result
cache on another node, the specified timeout value defines the maximum
time the first query result cache waits for the response from the second
query result cache.
When set to 0, the first query result cache sends request only to second
query result caches on the same node (local lookups).

Parameter: resultcache_request_timeout_in_milliseconds
Default: 0 (ms)
Parameter: resultcache_white_list
Description: Defines a comma-separated list of one or more table or view names, for
which query results can be written to the query result cache.
When the parameter is omitted or its value is an empty string, query
results of all tables and views can be cached.
The table or view names must be preceded by the schema name. Each of
the schema name and table/view name can be embraced with double
quotes or not.
Examples: “MYSCHEMA”.”MYTABLE”, “MYSCHEMA”.MYVIEW,
SYSTEM.VIEW
Values: One or more strings separated by commas, the strings representing table
or view names
Default: N/A
Section: calcengine
This section contains parameters that are related to calcengine configuration.
Parameter: max_cache_size_kb
Description: Sets a maximum memory cache size for calculation engine operations in
kilobytes.
Do not set a value less than the default.
Recommended:
1048576 = 1024 * 1024 (1 GB),
4194304 = 4 * 1024 * 1024 (4 GB)
Default: 1048576(1 GB)
Related information: For SAP BW systems, apply:
SAP Note 1856131
SAP Note 1942407
SAP Note 1988050

Section: distribution
This section contains parameters that are related to client distribution configuration.
Parameter: client_distribution_mode
Description: Sets the client distribution mode.
For the optimal connection performance, the client property
DISTRIBUTION must be set appropriately. See SAP Note 2079372.
Values: off: all distribution features are disabled.
connection: client side load balancing is enabled.
statement: statement routing is enabled.
all: all distribution features are enabled.
Default: statement
SAP Note 1743225
SAP Note 1745057
SAP Note 1774187
SAP Note 1785171
SAP HANA SQL and System Views Reference (M_CONNECTIONS)

Section: execution
This section contains parameters that are related to parallel execution.
Description: Sets a maximum target value for the average number of running job
worker threads (0 = number of available logical CPU cores).
Job worker threads process parallelized OLAP queries and perform system
tasks such as table updates, savepoint operations, garbage collection,
backup, and recovery.
The current number of running job worker threads can exceed the
specified target value.
The total number of job worker threads can be larger than the specified
target value because some of the job worker threads are not in the state
Running.
When set to 0, the target value is the number of available logical CPU
cores.
When Hyperthreading is enabled, the server has more logical cores than
physical cores.
When the specified value is smaller than the default value, the job worker
threads will only use a part of the available logical CPU cores.
When the specified target value is too large, the SAP HANA System may be
overloaded due to a high degree of parallelization.
When the specified target value is too small, important system tasks may
get stuck.
Multi-tenant database container system:
The parameter max_concurrency controls an effective number of logical
cores of a multi-tenant database container.
A reasonable value is the number of available logical CPU cores divided by
the number of tenant databases.
Example:
Available logical CPU cores: 32
Number of tenants: 4
Tenant database max_concurrency: 8
Do not specify a value of 0 to avoid that each tenant database takes all
available logical CPU cores.
The value of [execution] max_concurrency in the file indexserver.ini
overrides the value of [execution] max_concurrency in the file global.ini.
Default: Number of available logical cores.
Restart required: No. Parameter changes take effect not later than the currently running job
worker threads have terminated.
Validity: Single-container systems:
Multiple-container systems:

Section: import_export
This section contains parameters that are related to Import/Export SQL statements (i.e.,
IMPORT, IMPORT FROM, IMPORT SCAN, and EXPORT).
Parameter: csv_import_path_filter
Description: Sets one or more file system paths for the path filter on CSV file locations
when executing an IMPORT FROM SQL statement.
Multiple file system paths are separated by a semicolon delimiter (;).
The path filter restricts read access to CSV files located under the specified
file system paths. Additionally, the following file system paths are
implicitly set and cannot be excluded from the path filter:
•$DIR_INSTANCE/work
•$DIR_INSTANCE/backup
•$SAP_RETRIEVAL_PATH/trace
Values: One or more absolute file system paths, separated by a semicolon
delimiter (;)
Parameter: enable_csv_import_path_filter
Description: Enables (true) / Disables (false) the path filtering for CSV file locations
when executing an IMPORT FROM SQL statement.
When set to true, the path filtering restricts read access to CSV files
located under the file system paths specified by the parameter
csv_import_path_filter.
When set to false, CSV files can be ready from any file system path.
Values: true, false
Default: false (HANA Revision 85)
true (HANA Revisions >= 90)

Section: joins
This section contains parameters that are related to Join Engine configuration.
Parameter: translator_cache_size
Description: Defines the maximum number of tables in the JoinEngine translation table
cache.
Translation tables are created for caching join column entries of join
engine queries.
Default: 2000
SAP Note 1998599
Parameter: translator_hashmap_max_size
Description: Sets an upper threshold for using the hash-based implementation of
translation tables in bytes.
When the HANA System builds a translation table, it estimates the table
size using the vector-based implementation.
When the estimated size is smaller than the specified threshold value, the
HANA System always uses the hash-based implementation.
Otherwise, the HANA System also estimates the the size of the translation
table using the vector-based implementation and selects the
implementation with the smaller table size.
When neither the parameter translator_hashmap_max_size nor the
parameter translator_hashmap_min_size are defined, the HANA System
used the vector-based implementation of translation tables.
Translation tables are created for caching mapping information required
by join engine queries. The mapping information correlates values of
joined table columns.
The HANA System rebuilds translation tables at the first join query after a
delta merge operation of either of the two tables involved in the join
operation. Before the rebuild the HANA System determines the
implementation type.
When set to zero, the HANA System uses the vector-based
implementation for all translation tables.
Default: 50000 (HANA Revisions >= 90)
0 (HANA Revisions < 90)

Parameter: translator_hashmap_max_size
SAP Note 2036494
Parameter: translator_hashmap_min_size
Description: Sets a lower threshold value for using the hash-based implementation of
translation tables in bytes.
When the HANA System builds a translation table, it estimates the table
size using the vector-based implementation.
When the estimated table size is smaller than the specified lower
threshold value, the HANA System always uses the vector-based
implementation.
Otherwise, the HANA System evaluates the upper threshold value defined
by the parameter translator_hashmap_max_size.
When neither the parameter translator_hashmap_max_size nor the
parameter translator_hashmap_min_size are defined, the HANA System
used the vector-based implementation of translation tables.
Translation tables are created for caching mapping information required
by join engine queries. The mapping information correlates values of
joined table columns.
The HANA System rebuilds translation tables at the first join query after a
delta merge operation of either of the two tables involved in the join
operation. Before the rebuild the HANA System determines the
implementation type.
When set to zero, the HANA System uses the vector-based
implementation for all translation tables.
Default: 50000 (HANA Revisions >= 90)
0 (HANA Revisions < 90)
SAP Note 2036494
Section: load_trace
This section contains parameters that are related to collecting load event information.
Parameter: enable
Description: Enables (true) / disables (false) collecting load event information when
columnstore tables are loaded into memory.automatic delta merge
operations globally for all columnstore tables.
Values: true, false
Default: true

Parameter: enable
Parameter: maxfiles
Default: 10
Description: Sets a maximum size of an individual trace file in bytes (0 = unlimited)
Default: 10000000
Section: mergedog
This section contains parameters that are related to mergedog configuration.
Parameter: active
Description: Enables (yes) / disables (no) automatic delta merge operations globally for
all columnstore tables.
For an individual columnstore table, automatic delta merge operations can
be activated and deactivated in the system view SYS.TABLES by changing
the value in the column AUTO_MERGE_ON to TRUE and FALSE,
respectively.
Values: yes, no
Default: yes
Restart required: no

Parameter: auto_merge_decision_func
Description: Defines an automatic merge decision cost function that determines
whether or not a requested automatic delta merge operation is executed.
Values: Logical string expression
Default: See Cost Functions (Admin Guide)
Related information: Cost Functions (Admin Guide)
Parameter: auto_merge_priority_func
Description: Defines an auto merge priority cost function that determines the priority
that is assigned to an automatic delta merge request.
Parameter: critical_merge_decision_func
Description: Defines a critical merge cost function that determines whether or not a
critical delta merge operation is executed to avoid out of memory or
system crash situations even if other cost functions have been turned off
or failed to run.
Parameter: hard_merge_priority_func
Description: Defines a hard merge priority cost function that determines the priority
that is assigned to a hard delta merge request.

Parameter: load_balancing_func
Description: Defines a load balancing cost function that determines the allocation of
system resources to delta merge operations.
Parameter: smart_merge_decision_func
Description: Defines a smart merge decision cost function that determines whether or
not a requested delta merge operation triggered by a smart merge hint is
executed.
Parameter: smart_merge_enabled
Description: Enables (yes) / disables (no) delta merge operations triggered by smart
merge hints.
Caution: The parameter is deprecated.
Values: yes, no
Default: yes
Related information: Merge Motivations (Admin Guide)
Parameter: smart_merge_priority_func
Description: Defines a smart merge priority cost function that determines the priority
that is assigned to a delta merge request triggered by a smart merge hint.

Parameter: smart_merge_priority_func
Parameter: token_per_table
Description: Sets a default number of merge tokens to control parallel thread
executions of operations under the merge monitor, including delta merge
and optimized compression.
The merge monitor can determine a non-default number of threads
depending on the available system resources (CPU, memory).
Default: 2
Related information: Merge Tokens (Admin Guide)
Cost Functions (Admin Guide)
Section: optimize_compression
This section contains parameters that are related to optimized compression.
Parameter: active
Description: Switches automatic data compression optimization on (yes)/off (no).
The delta merge operation automatically determines if data compression
is required.
Values: yes, no
Default: yes
Related information: Data Compression in the Column Store (Admin Guide)
Parameter: auto_decision_func
Description: Defines a cost function that determines whether or not a data
compression optimization is executed when requested by an automatic
delta merge operation.
Default: See SAP HANA Administration Guide (Cost Functions)

Parameter: smart_decision_func
Description: Defines a cost function that determines whether or not a data
compression optimization is executed when requested by a smart delta
merge operation.
Default: See SAP HANA Administration Guide (Cost Functions)
Section: parallel
This section contains parameters that are related to the configuration of parallel algorithms.
Parameter: mode
Description: Sets the mode for parallel processing by multiple logical CPU cores in some
system functions that use this parameter:
Values: One of the following string values (case-insensitive):
 off: turns off parallel processing
 auto: lets the system functions decide to use parallel processing or
not
 force: turns on parallel processing
Default: Auto
Validity: All SAP HANA Revisions
Parameter: num_cores
Description: Limits the number of jobs to create in a parallelization step during
statement execution. Multiple parallelization steps may result in far more
jobs being created for a statement (and hence higher concurrency) than
this parameter.
The actual number of jobs being executed in parallel is further limited by
the parameters [execution] default_statement_concurrency limit and
[execution] max_concurrency and by the available CPU resources so that a
parallelization step can create fewer jobs than specified by the parameter
num_cores.
When not set, the effective limit is equal to the value of the parameter
[execution] max_concurrency_hint.
The value zero is not supported.
Note: SAP recommends that the parameters num_cores and [execution]
max_concurrency_limit have equal values because the two values are
used in the same logical function, but affect different places in the code.

Parameter: num_cores
SAP recommends to leave the default settings which allow the HANA
System utilize most of the available CPU resources.
If this parameter is modified, reasonable values are between 0 and
max_concurrency.
In large systems with at least four sockets, consider setting [execution]
max_concurrency_hint and [parallel] num_cores equal to the number of
logical cores per socket.
Default: Not set.
Validity: SAP HANA Revisions >= 80
Related information: Parameters that Control CPU (Admin Guide)
Parameter: tables_preloaded_in_parallel
Description: Sets the maximum number of tables that are reloaded in parallel during
system restart.
See also the configuration parameter [sql] reload_tables.
Default: 5
Related information: Restart Sequence (Admin Guide)
Section: partitioning
This section contains parameters that are related to the partitioning of columstore tables.
Parameter: dynamic_range_check_time_interval_sec
Description: Sets a default time interval in seconds for the Dynamic Range Partitioning
background job to check the row count of dynamic range partitions
periodically.
A dynamic range partition is a rest partition represented by the PARTITION
OTHERS DYNAMIC clause in CREATE TABLE or ALTER TABLE statements.
When the background job detects dynamic range partitions where the row
count is greater than a pre-defined threshold, a new dynamic range
partition will be created.
When the background job detects an empty dynamic range partition, the
empty partition will be dropped.
When set to 0, the Dynamic Range Partitioning background job will be
disabled.

Parameter: dynamic_range_check_time_interval_sec
Parameter: dynamic_range_default_threshold
Description: Sets a default row count threshold for splitting a dynamic range partition of
a specific table partitioned by range.
A dynamic range partition is a rest partition represented by the PARTITION
OTHERS DYNAMIC clause in the CREATE TABLE or ALTER TABLE statement.
A Dynamic Range Partitioning background job determines the row count
threshold by checking in the following order:
1) a pre-defined threshold value in the PARTITION OTHERS DYNAMIC
clause of the CREATE TABLE or ALTER TABLE statement of the
specific table.
2) a PARTITIONING_THRESHOLD value in the system view
M_EFFECTIVE_TABLE_PLACEMENT for the specific table.
To change the value, use the REPARTITIONING_THRESHOLD
clause of the SQL statement ALTER SYSTEM ALTER TABLE
PLACEMENT.
3) the parameter dynamic_range_default_threshold
When set to 0, the maximum size of the dynamic range partition is not
limited by the background job.
Default: 10 000 000 (10 million rows)
Parameter: split_history_parallel
Description: When columnstore tables have history indexes, the parameter enables
(yes) / disables (no) parallel partitioning of the main and history indexes.
Values: yes, no
Default: no
Related information: Partitioning Operations (Admin Guide)
Parameter: split_threads
Description: Sets a maxium number of threads per host to perform parallel partitioning
operations.
Each partitioning operation takes at least one thread.
Caution: A high number of threads may overload the system.

Parameter: split_threads
Values: Positive integer (1 to 128)
Default: 16
Related information: Partitioning Operations (Admin Guide)
Section: password policy

This section contains parameters that are related to password policies for a single-container
system or for the tenant databases of a multiple-container system.
Parameter: detailed_error_on_connect
Description: Sets the detail level or error information returned when a logon attempt
fails.
When set to false, the message “authentication failed” is returned.
When set to true, the specific reason for the failed logon is returned:
 “Invalid user password”
 “User is locked”
 “Connect try is outside validity period”
 “User is deactivated”
In a single-container system, the parameter "detailed_error_on_connect"
is set in the indexserver.ini file
MDC systems:
In a multi-tenant database container system, the parameter
"detailed_error_on_connect" for the system database is set in the
nameserver.ini file and for the tenant databases in the corresponding
indexserver.ini files.
Values: true, false
Default: false
SAP HANA revisions >= 97.03
MDC systems:
Parameter: force_first_password_change
Description: Enables (true) / disables (false) enforced password change after first logon.
When set to true, a user is forced to change his/her password after logon
with an initial password given by a system administrator.
When set to false, a user can continue to use the initial password.

Parameter: force_first_password_change
In a single-container system, the parameter "
force_first_password_change " is set in the indexserver.ini file
MDC systems:
"force_first_password_change" for the system database is set in the
Values: true, false
Default: true
Related information: Password Policy Configuration Options (Admin Guide)
Parameter: last_used_passwords
Description: Sets a number of last used passwords (0 = disabled) that a user is not
allowed to reuse.
When set to 0, a user can reuse all old passwords.
In a single-container system, the parameter "last_used_passwords" is set
in the indexserver.ini file
MDC systems:
"last_used_passwords" for the system database is set in the
Default: 5
Parameter: maximum_invalid_connect_attempts
Description: Sets a maximum number of failed logon attempts until a user is locked.
In a single-container system, the parameter
"maximum_invalid_connect_attempts" is set in the indexserver.ini file
MDC systems:
"maximum_invalid_connect_attempts" for the system database is set in

Parameter: maximum_invalid_connect_attempts
the nameserver.ini file and for the tenant databases in the corresponding
Default: 6
Parameter: maximum_password_lifetime
Description: Sets a maximum number of days after which a user’s password expires.
"maximum_password_lifetime" is set in the indexserver.ini file
MDC systems:
"maximum_password_lifetime" for the system database is set in the
Values: Positiver integer
Default: 182 (days)
Parameter: maximum_unused_inital_password_lifetime
Description: Sets a maximum lifetime of an initial password given by a system
administrator in number of days.
When a user gets an initial password from the system administrator and
does not log in within the specified number of days, the given initial
password becomes invalid and the user administrator has to reset the
password.
"maximum_unused_inital_password_lifetime" is set in the indexserver.ini
file.
MDC systems:
"maximum_unused_inital_password_lifetime" for the system database is
set in the nameserver.ini file and for the tenant databases in the
corresponding indexserver.ini files.

Parameter: maximum_unused_inital_password_lifetime
Note: The parameter is mis-spelled in the HANA configuration files. It
contains the word “inital” where “initial” is expected.
Values: Positive integer (1 .. 65536)
Default: 7 (days)
Parameter: maximum_unused_productive_password_lifetime
Description: Sets a maximum number of days after which a user’s password expires if
the user has not logged on.
After the lifetime elapsed, the password becomes invalid and the user
administrator has to reset the password.
"maximum_unused_productive_password_lifetime" is set in the
indexserver.ini file
MDC systems:
"maximum_unused_productive_password_lifetime" for the system
database is set in the nameserver.ini file and for the tenant databases in
the corresponding indexserver.ini files.
Default: 365 (days)
Parameter: minimal_password_length
Description: Sets a minimum number of characters a password has to consist of.
When the parameter minimal_password_length is increased, existing
passwords with a smaller number of characters remain valid.
In a single-container system, the parameter "minimal_password_length" is
set in the indexserver.ini file
MDC systems:
"minimal_password_length" for the system database is set in the

Parameter: minimal_password_length
Values: Positive integer (6 ... 64)
Default: 8
Parameter: minimum_password_lifetime
Description: Sets a minimum number of days to elapse before a user can change
his/her password.
When set to 0, a password has no minimum lifetime.
"minimum_password_lifetime" is set in the indexserver.ini file
MDC systems:
"minimum_password_lifetime" for the system database is set in the
Values: Positve integer or zero
Default: 1 (day)
Parameter: password_expire_warning_time
Description: Sets a number of days before a password is due to expire that a user
receives notification
When set to 0, a user does not receive a notification that his/her password
is due to expire.
"password_expire_warning_time" is set in the indexserver.ini file
MDC systems:
"password_expire_warning_time" for the system database is set in the
Default: 14

Parameter: password_expire_warning_time
Parameter: password_layout
Description: Sets the character types that the password must contain. The password
requires at least one character of each character type.
Values: String of characters comprising none or one of each of the following
character types:
 Lowercase letter (a-z)
 Uppercase letter (A-Z)
 Numerical digits (0-9)
 Special characters (underscore (_), hyphen (-), question mark (?),
and so on)
Examples:
 Aa1 is equivalent to Bb2
The password must contain at least one uppercase character, at
least one lowercase character, and at least one number.
 A_ is equivalent to B?
The password must contain at least one uppercase character and
at least one special character.
Note: Passwords containing special characters other than underscore must
be enclosed in double quotes (“). The SAP HANA Studio supports
passwords enclosed in double quotes whereas the SAP HANA HDSQL
command line tool does not.
In a single-container system, the parameter "password_layout" is set in
the indexserver.ini file
MDC systems:
"password_layout" for the system database is set in the nameserver.ini file
and for the tenant databases in the corresponding indexserver.ini files.
Default: Aa1
Parameter: password_lock_for_system_user
Description: Enables (true) / Disables (false) locking the user SYSTEM for the specified
password lock time after the maximum number of failed logon attempts.
"password_lock_for_system_user" is set in the indexserver.ini file

Parameter: password_lock_for_system_user
MDC systems:
"password_lock_for_system_user" for the system database is set in the
Values: true, false
Default: True
SAP HANA revisions >= 97.03
MDC systems:
Parameter: password_lock_time
Description: Sets a time period in minutes for which a user is locked after the maximum
number of failed logon attempts.
When set to 0, a user is not locked after the maximum number of failed
logon attempts.
When set to -1, a user is locked for an infinite period. The user can only be
unlocked by a user administrator.
In a single-container system, the parameter "password_lock_time" is set in
the indexserver.ini file
MDC systems:
"password_lock_time" for the system database is set in the nameserver.ini
file and for the tenant databases in the corresponding indexserver.ini files.
Values: Positive integer, zero, and -1
Section: pythontrace
This section contains parameters that are related to the tracing of the Python API.
For other parameters, see executor.ini.
Description: Specifies the name of the trace file of Python API calls.

Values: File name (for SAP HANA Revisions >= 94)
Prefix “trace/” and file name (for SAP HANA Revisions < 94)
Environment variables are not supported except for $HOST, $PORT, $PID,
and $COUNT.
Default: servertrace_$HOST_${PORT}_${COUNT:3}.py
(for SAP HANA Revisions >= 94)
trace/servertrace_${HOST}_${PORT}_${COUNT:3}.py
(for SAP HANA Revisions < 94)
When the default settings are unchanged, the variables $HOST and ${PORT}
are replaced with the host name and port number associated with the HANA
service. ${COUNT:3} is a three-digit file counter that is cyclically
incremented.
Section: queueserver
This section contains parameters that are related to queueserver configuration.
Parameter: inactive_at_service_start
Description: Enables (false) / Disables (true) automatic loading of asynchronous
fulltext indexes at HANA System startup. Individual indexes can be set
to active by executing ALTER FULLTEXT INDEX <indexName>
ACTIVATE QUEUE
Values: true, false
Default: false
Restart required: With restart, the parameter change takes effect for all fulltext indexes.
Without restart, only fulltext indexes created after the parameter change are
affected.
Section: repository
This section contains parameters that are related to repository configuration.
Parameter: content_vendor
Description: Defines the vendor attribute for delivery units created on this server.
Each delivery unit has a vendor attribute.
Values: String
Default: UNDEFINED

Parameter: content_vendor
Section: search
This section contains parameters that are related to search configuration.
Parameter: late_materialization_threshold
Description: Sets the lowest number of rows for compressed materialization of large
result sets from column store tables. This processing mode is called late
materialization and significantly reduces the memory consumption for
processing large result queries with the tradeoff of slightly decreased query
performance.
Default: 20000
Parameter: late_materialization_threshold_for_insert
Description: Sets the lowest number of rows for compressed materialization of large
result sets during “insert as select” operations from column store tables. This
processing mode is called late materialization and significantly reduces the
memory consumption for processing large result queries with the tradeoff of
slightly decreased query performance.
Default: 2000000

Section: session
This section contains parameters that are related to sessions / connections.
Parameter: connection_history_lifetime
Description: Sets a maximum lifetime of historical information about
connections/session in minutes (0 = disabled).
When set to a positive value, information about connections/sessions will
be stored for the specified lifetime.
Information about connections/sessions can be displayed in the system
views M_CONNECTIONS and M_CONNECTION_STATISTICS.
When set to 0, no information about connections/sessions will be stored in
the above system views.
Values: Positive integer or zero: 0 ... 10080 (7days)
Default: 60 (1 hour)
Parameter: connection_history_maximum_size
Description: Sets a maximum number of historical information entries about
connections/sessions (0 = disabled).
When set to a positive value, information about connections/sessions will
be stored until the maximum number of entries has been reached.
When set to 0, there is no upper limit on the number of historical
information entries.
Default: 100000
Parameter: idle_connection_timeout
Description: Sets a timeout interval in minutes for the maximum duration of idle
connections/sessions (0 = disabled).
When set to a positive value, idle connections/sessions will be
disconnected and associated resources released after the specified timeout
interval has elapsed.
When set to 0, idle connections/sessions will not be disconnected.
Default: 1440 (1 day)

Parameter: idle_connection_timeout
SAP Note 2035443
Parameter: idle_connection_timeout_application_<application_name>
Description: Sets a maximum timeout interval for the maximum duration of idle
connections/sessions that were established by a specific application
<application_name> in minutes (0 = disabled).
When the <application_name> is, for example, “statisticsserver”, the
parameter reads idle_connection_timeout_application_statisticsserver.
In this case, the parameter applies to idle connections/sessions established
by the statisticsserver process.
When set to a positive value, idle connections/sessions that were
established by the specific application will be disconnected and associated
resources released after the specified timeout interval has elapsed.
When set to 0, idle connections/sessions that were established by the
specific application will not be disconnected.
When set to a negative value or when the parameter is not specified, the
value of the parameter idle_connection_timeout takes effect.
Values: Positive or negative integer or zero
Default: -1 (idle_connection_timeout)
Parameter: idle_connection_timeout_application_hdbstudio
Description: Sets a maximum timeout interval for the maximum duration of idle
connections/sessions that were established by the HDBStudio application in
minutes (0 = disabled).
When set to a positive value, idle connections/sessions that were
established by the HDBStudio application will be disconnected and
associated resources released after the specified timeout interval has
elapsed.
When set to 0, idle connections/sessions that were established by the
HDBStudio application will not be disconnected.
When set to a negative value or when the parameter is not specified, the
value of idle_connection_timeout takes effect.
Values: Positive or negative integer or zero

Parameter: maximum_connections
Description: Sets a maximum number of connections.

Default: 65536
Parameter: maximum_external_connections
Description: Sets a maximum number of connections that are created by user sessions.
Default: 65536
Parameter: reserved_connections
Description: Sets a number of reserved connections for administrative access only.
When the maximum number of connections defined by the parameter
maximum_connections minus the specified number of reserved connections
is reached, only an administrator with the system privilege SESSION ADMIN
can log on to the system, for example, to resolve blocking situations by
canceling sessions.
Default: 10
Related information Reserve Connections for Administrators (Admin Guide)
Parameter: socket_keepalive
Description: Enables (on)/disables (off) monitoring of active connections/sessions by
means of keep-alive probes. The monitoring may help to detect network
errors.
Values: on, off
Default: on

Parameter: socket_keepalive
Parameter: tcp_keepalive_intvl
Description: Sets a time interval between subsequent keep-alive probes in seconds. If no
acknowledgement has been received to a previous keep-alive probe, a
subsequent keep-alive probe is sent after the specified time interval.
Default: 10
Parameter: tcp_keepalive_probes
Description: Sets a number of unacknowledged keep-alive probes to send before
notifying the application layer that the connection/session is not available
any more.
Default: 5
Parameter: tcp_keepalive_time
Description: Sets a time interval between the last packet sent and the first keep-alive
probe in seconds.
Default: 600
Validity: SAP HANA revisions > 71

Section: smart_data_access
This section contains parameters that are related to remote caching.
Parameter: default_connections_pool_max_size
Description: Sets a maximum number of connections allowed in one pool.
Each HANA front-end session has one corresponding connection pool per
HANA cluster node for a remote source.
The number of connections depends on the degree of multi-threading of
the executed statements, but cannot exceed the number specified in
default_connections_pool_max_size.
Default: 3
Related information: Remote Connection Pooling (Admin Guide)
Parameter: enable_remote_cache
Description: Enables (true) / disables (false) remote caching for federated queries.
Currently, only Hive sources are supported.
When set to false, the USE_REMOTE_CACHE hint will be ignored.
When set to true and the USE_REMOTE_CACHE hint is used, the result set
of virtual table’s queries is materialized in Hive. Subsequent queries are
served from the materialized view.
Values: true, false
Default: False
Parameter: enable_remote_source_capability
Description: Enables (true) / disables (false) sending complex queries to a remote
source.
When set to true, queries that depend on the remote source capabilities
(filter, join, aggregation etc) are sent to the remote source for execution.
When set to false, only queries that perform full table scans are sent to
the remote source.
Values: true, false
Default: True
Related information: Smart Data Access System Parameters (Admin Guide)

Parameter: remote_cache_validity
Description: Sets a lifetime of the remote cache in seconds ( 0 = disabled)
When the lifetime of an object elapses, the object is automatically
removed from the remote cache. Subsequent queries create new objects
in the remote cache.
When set to zero, the remote cache is disabled.
Parameter: semi_join_execution_strategies
Description: Specifies a preferred order of semi-join execution strategies (T, I, TI, IT) or
disables them (N)
Values: IT = in-clause strategy, followed by temporary table strategy
TI = temporay table strategy, followed by in-clause strategy
T = temporary table strategy
I = in-clause strategy
N = disables the semi-join execution strategies
Default: IT = in-clause strategy, followed by temporary table strategy
Parameter: semi_join_max_in_elements
Description: Specifies a maximum number of values in the IN-clause that is generated
in the SQL statement when performing an IN-clause strategy (0 =
disabled).
To take effect, the parameter semi_join_execution_strategies must
contain an in-clause strategy.
When set to 0, no IN-clause is generated.
Default: 1024

Parameter: semi_join_max_temp_table_cardinality
Description: Sets a maximum number of rows in a temporary table that is created
when performing a temporary table strategy (0 = disabled).
To take effect, the parameter semi_join_execution_strategies must
contain a temporary table strategy.
When set to 0, no temporary table is created.
Default: 16384
Parameter: virtual_table_default_cardinality
Description: Sets a default number of rows for virtual tables, which are considered by
the SQL optimizer if the table statistics has not been calculated.
Default: 1 000 000
Parameter: virtual_table_format
Description: Specifies the mode of temporary tables to store data retrieved from
virtual tables.
Values: ROW: row-based
COLUMN: column-based
AUTO: an optimizer selects ROW or COLUMN
Default: ROW
Section: sql
This section contains parameters that are related to sql query processing.
Parameter: calculation_view_unfolding
Description: Enables (true) / Disables (false) unfolding of calculation views.
Values: true, false
Default: true

Parameter: calculation_view_unfolding
Parameter: max_sql_executors
Description: Sets a maximum total number of SQL executor threads including all thread
states (Running, Inactive, Semaphore Wait, etc.) (0 = unlimited). SQL
executor threads are processing SQL statement requests.
When set to 0, the number of SQL executor threads is not limited.
Default: 0 (unlimited)
Related information: Controlling Parallel Execution of SQL Statements (Admin Guide)
Parameter: plan_cache_parameter_enabled
Description: Enables (true) / disables (false) capturing of parameter (bind) values of an
SQL statement when the sum of execution times of the SQL statement is
greater than the lower time limit defined by the parameters
plan_cache_parameter_sum_threshold and
plan_cache_parameter_threshold
Captured parameter values can be displayed in the system view
M_SQL_PLAN_CACHE_PARAMETERS.
Values: true, false
Default: true
Parameter: plan_cache_parameter_sum_threshold
Description: Sets a time threshold for the sum of execution times of an SQL statement
in milliseconds.
When the sum of execution times exceeds the specified time threshold,
parameter (bind) information of the SQL statement is captured.
The captured parameter (bind) information can be displayed in the system
view M_SQL_PLAN_CACHE_PARAMETERS.
The capturing of parameter (bind) information is disabled when the
parameter plan_cache_parameter_enabled is set to false.

Parameter: plan_cache_parameter_sum_threshold
Default: 100000 (100 seconds)
Parameter: plan_cache_parameter_threshold
Description: Sets a time threshold for the single execution time of an SQL statement in
milliseconds
When the last single execution time exceeds both the specified time
threshold and previously recorded single execution times of the SQL
statement, parameter (bind) information of the SQL statement is
captured.
The captured parameter (bind) information can be displayed in the system
view M_SQL_PLAN_CACHE_PARAMETERS.
The capturing of parameter (bind) information is disabled when the
parameter plan_cache_parameter_enabled is set to false.
Default: 100 (milliseconds)
Parameter: plan_cache_size
Description: Sets a maximum size of the SQL plan cache in bytes.
Default: 2147483648 = 2 * 1024 * 1024 * 1024 (bytes = 2 Gigabytes)
SAP Note 1763592
System views:
M_SQL_PLAN_CACHE
M_SQL_PLAN_CACHE_OVERVIEW
Parameter: reload_tables
Description: On system startup, the parameter reload_tables enables (true)/disables
(false) automatic reload of tables that were loaded before shutdown.
Values: true, false

Parameter: reload_tables
Default: true
Related information: Restart Sequence (Admin Guide)
SAP Note 1889081
Parameter: reserved_connections
Description: Sets a number of reserved connections for administrative access only.
When the maximum number of connections defined by the parameter
maximum_connections minus the specified number of reserved
connections is reached, only an administrator with the system privilege
SESSION ADMIN can log on to the system, for example, to resolve blocking
situations by canceling sessions.
Default: 10
Parameter: sql_executors
Description: Sets a target value for the maximum number of SQL executor threads in
the thread state “Running” (0 = number of available logical CPU cores).
SQL executor threads are processing SQL statement requests.
The actual number of SQL executor threads can exceed the specified value
when some of the threads are not running.
When set to 0, the target value is the number of available logical CPU
cores.
Note: A reduction of sql_executors value can help to avoid memory
footprint.
Default: Number of available logical CPU cores.
Related information: Controlling Parallel Execution of SQL Statements (Admin Guide)
SAP Note 1763592
SAP Note 1844237

Parameter: subplan_sharing
Description: Sets a mode for sharing subplans
Values:  Force: prefer shared subplan
 Auto: select best cost plan
 Off: avoid shared subplan
Default: Auto
Restart required: No. Changes only affect new SQL plans in the plan cache.
Section: sql_client_network_io
This section contains parameters that are related to client network communication.
Parameter: buffer_size
Description: Sets a maximum number of entries that are stored in the system view
M_SQL_CLIENT_NETWORK_IO
When set to less than or equal 0, the default value (1000000) is used.
Default: 1000000
Parameter: enabled
Description: Enables (true) / Disables (false) SQL client network IO tracing. The trace
information is stored in the system view M_SQL_CLIENT_NETWORK_IO
Values: true, false
Default: false
Section: sqlscript
This section contains parameters that are related to sqlscript query processing
Parameter: typecheck_procedure_input_param
Description: Defines how SQLScript procedures handle type checks on input parameters,
for example, length of string values.
When set to true and type checks fail, the SQLScript procedure aborts with
an error.
When set to false and type checks fail, the SQLScript procedure prints a
warning in the indexserver trace.

Parameter: typecheck_procedure_input_param
Values: true, false
Default: false
Section: sqltrace
This section contains parameters that are related to tracing SQL statements.
Parameter: application
Description: Specifies an application name to filter SQL statements.
When the parameter is an empty string, no filter is applied on the
application name.
Values: String
Description: Specifies an application user to filter SQL statements.
When the parameter is an empty string, no filter is applied on the
application user.
Values: String
Parameter: details
Description: Specifies which detail information of the SQL statement is written to the
trace file when the parameter details is set to one of the following string
values:
 basic: connection information and statement information
 passport: decoded passport contents
 session_variables: system-defined variables in the session context
 user_variables: user-defined variables in the session context
 connection: connection information such as session ID, transaction ID,
client PID, client IP, user name, schema name, and session variable-
value pairs.
 statement: statement information, such as executed timestamp, thread
ID, connection ID, and statement ID.
 all: filter in all comments of connection and statement
 empty string: no detail information

Parameter: details
Values: One of the string values:
basic, passport, session_variables, user_variables, connection, statement, all
Or empty string
To leave the trace without these comments, just set the value of the field to
empty.
Default: basic
Parameter: filesize_limit
When a trace file reaches the specified maximum file size, it is closed, and a
new file created.
Default: 1610612736 = 1.5 * 1024 * 1024 * 1024 (bytes = 1.5 GB)
Parameter: flush_interval
Description: Specifies the maximum number of SQL trace statements that are written to
the trace file at once.
When set to 0, every SQL trace statement is immediately written to the trace
file.
Default: 16
Parameter: level
Description: Specifies a trace level to filter SQL statements
Values: String values
error: Only SQL statemets that returned an error
rollback: Only SQL statements that are rolled back
normal: Only SQL statements that finished without error or rollback
all: All SQL statements, union of error, rollback, and normal, excluding result
sets.
all_with_results: All SQL statements, including result sets.

Parameter: level
Default: all
Parameter: max_files
Values: Positive integer (0 to 999) and zero
Default: 1
Parameter: object
Description: Specifies one or more object names to filter SQL statements. An object can
be a table, view, or procedure.
When the parameter is an empty string, no filter is applied on the object
name.
Values: Comma-separated list of one or more objects in the format
<schema_name>.<object_name>,
For example,
<schema_1>.<view_1>,<schema_2>.<procedure_2>,
<schema_3>.<table_3>
Parameter: query_plan_trace
Description: Includes (on) / Excludes (off) query plan information into / from the SQL
trace.
The query plan information is the the output of the EXPLAIN PLAN operation.
Values: on, off
Default: off
Parameter: statement_type
Description: Specifies one or more of the following statement types to filter
corresponding SQL statements:

Parameter: statement_type
 ddl, for example, ALTER TABLE, …
 dml, for example, INSERT INTO TABLE, SELECT, …
 procedure, for example, CALL, CREATE PROCEDURE, …
 session, for example, CONNECT, SET SESSION, …
 system, for example, ALTER SYSTEM
 transaction, for example, COMMIT, ROLLBACK,
When the parameter is an empty string, no filter is applied on statement
type.
Values: Comma-separated list of one or more string values:
 ddl
 dml
 procedure
 session
 system
 transaction
or empty string
Parameter: trace
Description: Enables (true) / Disables (false) SQL trace.
The traced information is written to an SQL trace file.
Values: on, off
Default: off
Validity: All SAP HANA revisisions
Description: Specifies the name of the SQL trace file.
Values: Filename. Environment variables are not supported except for $HOST,
$PORT, $PID, and $COUNT.
Default: sqltrace_$HOST_${PORT}_${COUNT:3}.py
When the default settings are unchanged, the variables $HOST and ${PORT}
are replaced with the host name and port number associated with the HANA
service. ${COUNT:3}.is a three-digit file counter that is cyclically
incremented.

Parameter: user
Description: Specifies a HANA SQL user to filter SQL statements.
When the parameter is an empty string, no filter is applied on the HANA SQL
user.
Values: String
Section: table_redist
This section contains parameters that are related to table redistribution.
Parameter: all_moves_physical
Description: Enables (true) / disables (false) immediate physical table moves during
table redistribution
If set to true, in response to a table move operation of a column store
table, the persistence storage is moved immediately to the target host
(physical table move).
If set to false, the table move operation will create a link inside the target
host persistence pointing to the source host persistence (logical table
move). The link will be removed on the next table merge operation of that
table or upon execution of the next table move operation of that table
without target host.
Caution: Physical table moves can significantly extend the runtime of the
table redistribution. Logical table moves can have negative impact on later
query executions.
Values: true, false
Default: true
Parameter: balance_by_execution_count
Description: Includes (true) / Excludes (false) the accumulated execution counts for all
SQL plans (M_SQL_PLAN_CACHE) referencing a specific table group to
calculate a score list for placing the specific table group on multiple nodes
allowed by table placement rules (TABLE_PLACEMENT, TABLE_GROUPS).
A table group comprises one or more table partitions that must be placed
on the same node.

Parameter: balance_by_execution_count
A simulation run determines a sequence of table groups, calculates
corresponding score lists, determines optimal locations, and accumulates
the scores of the optimal locations, resulting in a total score.
To determine an optimal distribution of all table groups based on the total
score, the simulation run is repeated for different sequences of table
group.
Values: true, false
Default: true
Parameter: balance_by_execution_count_weight
Description: Sets a weight factor for the scores calculated from the accumulated
execution counts.
The weight factor takes only effect when the value of the parameter
balance_by_execution_count is true.
Default: 1
Parameter: balance_by_execution_time
Description: Includes (true) / Excludes (false) the accumulated execution times for all
SQL plans (M_SQL_PLAN_CACHE) referencing a specific table group to
calculate a score list for placing the specific table group on multiple nodes
allowed by table placement rules (TABLE_PLACEMENT, TABLE_GROUPS).
See description of the parameter balance_by_execution_count.
Values: true, false
Default: true
Parameter: balance_by_execution_time_weight
execution times. The weight factor takes only effect when the value of the
parameter balance_by_execution_time is true.
Default: 1

Parameter: balance_by_execution_time_weight
Parameter: balance_by_memuse
Description: Includes (true) / Excludes (false) the accumulated memory size
(M_CS_TABLES) of a specific table group to calculate a score list for placing
the specific table group on multiple nodes allowed by table placement
rules.
Values: true, false
Default: true
Parameter: balance_by_memuse_weight
Description: Sets a weight factor for the scores calculated from the acculated memory
size. The weight factor takes only effect when the value of the parameter
balance_by_memuse is true.
Default: 1
Parameter: balance_by_partnum
Description: Includes (true) / Excludes (false) the accumulated numbers of partitions
rules.
Values: true, false
Default: true
Parameter: balance_by_partnum_weight
numbers of partitions. The weight factor takes only effect when the value
of the parameter balance_by_partnum_weight is true.

Parameter: balance_by_partnum_weight
Default: 1
Parameter: balance_by_rows
Description: Includes (true) / Excludes (false) the accumulated number of record counts
rules.
A table group comprises one or more table partitions that must be placed
on the same node.
Values: true, false
Default: true
Parameter: balance_by_rows_weight
Description: Sets a weight factor for the scores calculated from the accumulated record
counts. The weight factor takes only effect when the value of the
parameter balance_by_rows is true.
Default: 1
Parameter: balance_by_table_classification
Description: Includes (true) / Excludes (false) the accumulated table classification
counts of a specific table group to calculate a score list for placing the
specific table group on multiple nodes allowed by table placement rules.
Values: true, false
Default: true

Parameter: balance_by_table_classification_weight
Description: Sets a weight factor for the scores calculated from the table classification
counts. The weight factor takes only effect when the value of the
parameter balance_by_table_classification is true.
Default: 1
Parameter: debug_export_detail
Description: Enables (true) / Disables (false) writing debug information of table
reorganizations (move, split, merge) to session temporary tables:
#REORG_LOCATIONS
#REORG_TABLEINFO
#REORG_PARTINFO
Values: true, false
Default: true
Parameter: enable_merge
Description: Enables (true) / Disables (false) table merge operations during table
redistribution.
Values: true, false
Default: true
Parameter: force_partnum_to_splitrule
Description: Controls the behavior of table redistribution in relation to customizing
settings.
Enables (true) / disables (false) execution of operations that change the
number of level 1 partitions according to the customizing settings.
When set to false, the table redistribution process only supports the
following changes of the number of level 1 partitions:
 in table split operations, an increase of the partition number
from 1 to 2, from 1 to 3, from 2 to 4, from 3 to 6, from 4 to 8,
and from 6 to 12.

Parameter: force_partnum_to_splitrule
 in table merge operations, a decrease of the partition
number from 12 to 6, from 8 to 4, from 6 to 3, from 4 to 2,
from 3 to 1, and from 2 to 1
When set to true, the table redistribution process allows all changes of the
number of level 1 partitions.
For example, a table has two level 1 partitions but should have three level
1 partitions according to the customizing settings.
When set to true, the table redistribution process adjusts the number of
level 1 partitions from 2 to 3.
When set to false, the number of level 1 partitions cannot be increased
from 2 to 3.
Values: true, false
Default: false
Parameter: num_exec_threads
Description: Sets a maximum number of parallel execution threads for table
reorganization operations (move, split, merge).
Default: SAP HANA revisions < 110: 10
SAP HANA revisions >= 110: 20
Section: trace
This section contains parameters that are related to tracing.
For the parameter descriptions, see global.ini.
Section: traceprofile%
This section contains parameters that are related to tracing using a specific profile.
For the parameter descriptions, see global.ini.
Section: transaction
This section contains parameters that are related to transactions.
Parameter: idle_cursor_alert_timeout
Description: Sets a threshold time period in minutes for raising an alert about long
running cursors, which could block garbage collection.

Parameter: idle_cursor_alert_timeout
When a cursors runs longer than the time period specified by this
parameter, the HANA System raises an alert and writes a message into the
alert trace file.
When set to zero, the alert is raised for every active cursor.
Default: 60 (minutes)
Parameter: idle_cursor_lifetime
Description: Sets a threshold time period in minutes for closing connections of long
running cursors, which could block garbage collection.
When a cursors runs longer than the time period specified by this
parameter, the HANA System closes the corresponding connection.
When set to zero, the HANA System will not close connections of long
running cursors.
Default: 720 (minutes = 12 hours)
Parameter: lock_wait_timeout
Description: Sets a lock wait timeout threshold in milliseconds (0 = nowait).
A transaction waits to acquire a lock held by another transaction until the
specified timeout period elapses. Then, the HANA System returns an error
and the transaction is rolled back.
When set to 0, transactions will not wait.
Maximum
2,147,483,647 = 2 * 1024 * 1024 * 1024
(approx.. 25days)
Parameter: transaction_history_record_limit
Description: Sets a maximum row number of the system table
SYS.TRANS_TOKEN_HISTORY. (0 =unlimited)
When set to zero, the number of rows of the table is unlimited.

Parameter: transaction_history_record_limit
The table SYS.TRANS_TOKEN_HISTORY contains information for time-
travel queries.
Default: 1000000
Parameter: transaction_history_size_limit
Description: Sets a maximum size of the system table SYS.TRANS_TOKEN_HISTORY in
megabytes.
(0 = unlimited)
When set to zero, the number of rows of the table is unlimited. The table
SYS.TRANS_TOKEN_HISTORY contains information for time-travel queries.
Default: 10240 (10 gigabytes)
Parameter: uncommitted_write_transaction_alert_timeout
Description: Sets a threshold time period in minutes for raising an alert when a write
transaction has not been committed for the specified period of time.
When the alert is raised, , a message is written into the alert trace file.
When set to 0, an alert is raised for each write transaction.
Default: 60 (minutes = 1 hour)
Section: unload_trace
This section contains parameters that are related to collecting unload event information.
Parameter: enable
Description: Enables (true) / disables (false) collecting unload event information when
columnstore tables are unloaded from memory.
Values: true, false
Default: true

Parameter: enable
Parameter: maxfiles
Default: 10
Default: 10000000
Section: result_cache
This section contains parameters that are related to the configuration of the result cache.
Parameter: total_size
Description: Sets a maximum memory size of the result cache in megabytes.
Default: 10000 (megabytes approx.. 10 GB)

8 Filename: multidb.ini
This configuration file describes parameters for multitenant database containers.
Section: readonly_parameters
This section contains a blacklist of parameters to prevent configuration changes.
Blacklist parameters can be configured on all layers of the HANA System (SYSTEM, HOST,
DATABASE).
A default configuration blacklist comprises the following file/section/parameter combinations:
Parameter: auditing configuration
Description: Prevents configuration of the specified parameters of the section [auditing
configuration]
When set to asterisk, all parameters of the section [auditing configuration]
are read-only.
Values: Asterisk or comma-separated list of one or more of the following value:
default_audit_trail_type,
emergency_audit_trail_type,
alert_audit_trail_type,
critical_audit_trail_type
Default: default_audit_trail_type,
emergency_audit_trail_type,
alert_audit_trail_type,
critical_audit_trail_type
Related information: Prevent Changes to System Properties in Tenant Databases (Admin Guide)
Parameter: communication
Description: Prevents configuration of the specified parameters of the section
[communication]
When set to asterisk, all parameters of the section [communication] are
read-only.
Values: Asterisk or comma-separated list of one or more parameters of the section
[communication]
Default: Asterisk (*)

Parameter: execution
[execution]
When set to asterisk, all parameters of the section [execution] are read-
only.
[execution]
Default: max_concurrency
Parameter: global.ini/customizable_funcationalities
[customizable_functionalities] in the file global.ini.
When set to asterisk, all parameters of the section
[customizable_funcationalities] in the file global.ini are read-only.
[customizable_funcationalities] in the file global.ini
Parameter: global.ini/extended_storage
[extended_storage] in the file global.ini.
When set to asterisk, all parameters of the section [extended_storage] in
the file global.ini are read-only.
[extended_storage] in the file global.ini
Parameter: global.ini/persistence
[persistence] in the file global.ini.

Parameter: global.ini/persistence
When set to asterisk, all parameters of the section [persistence] in the file
global.ini are read-only.
[persistence] in the file global.ini
Default: basepath_datavolumes_es
basepath_logvolumes_es
basepath_databackup_es
basepath_logbackup_es
Parameter: global.ini/xb_messaging
[xb_messaging] in the file global.ini.
When set to asterisk, all parameters of the section [xb_messaging] in the
file global.ini are read-only.
[xb_messaging] in the file global.ini
Parameter: indexserver.ini/authentication
[authentication] in the file indexserver.ini.
When set to asterisk, all parameters of the section [authentication] in the
file indexserver.ini are read-only.
[authentication] in the file indexserver.ini
Default: SapLogonTicketTrustStore

Parameter: memorymanager
[memorymanager].
When set to asterisk, all parameters of the section [memorymanager] are
read-only.
[memorymanager]
Default: allocationlimit,
minallocationlimit,
global_allocation_limit,
async_free_threshold,
async_free_target
Parameter: multidb.ini/readonly_parameters
[readonly_parameters] in the file multidb.ini.
When set to asterisk, all parameters of the section [readonly_parameters]
in the file multidb.ini are read-only.
[readonly_parameters] in the file multidb.ini
Parameter: session
[session].
When set to asterisk, all parameters of the section [session] are read-only.
[session]
Default: maximum_connections, maximum_external_connections

Parameter: sql
Description: Prevents configuration of the specified parameters of the section [sql].
When set to asterisk, all parameters of the section [sql] are read-only.
Values: Asterisk or comma-separated list of one or more parameters of the
section [sql]
Default: sql_executors

9 Filename: nameserver.ini
This configuration file describes parameters for the nameserver service.
Section: auditing configuration
This section contains parameters that are related to auditing configuration.

The parameters are configured in the SYSTEM layer for the system database of a multiple-
container system.
Description: Enables (true)/disables (false) global auditing regardless of the enabled
state of the audit policies.
MDC systems:
In a multi-tenant database container system, the global auditing state for
the system database is set in the nameserver.ini file, and for the tenant
databases in the global.ini file.
Values: true, false
Default: false
Validity: MDC systems:
SAP Note 1991634
Section: password policy

This section contains parameters that are related to password policies.
container system.
See the descriptions in indexserver.ini.
Section: public_urls
This section contains parameters that are related to public URLs.
container system.
Parameter: http_url
Description: Defines a public URL for HTTP access to a SYSTEM database when the
parameter is set in the SYSTEM layer of a multi-tenant database container
system.
Values: http://<virtual_hostname>:80<instance>
Default: http://$(SAPLOCALHOST):80$(SAPSYSTEM)

Parameter: http_url
Validity: MDC systems only:
Related information: Configure HTTP(S) Access to Multitenant Database Containers (Admin
Guide)
Parameter: https_url
Description: Defines a public URL for HTTPS access to a SYSTEM database when the
parameter is set in the SYSTEM layer of a multi-tenant database container
system.
Values: https://<virtual_hostname>:43<instance>
Default: https://$(SAPLOCALHOST):43$(SAPSYSTEM)
Guide)
Section: sld
This section contains parameters that are related to System Landscape Directory.
Parameter: configpath
Description: Defines the path to the file slddest.cfg.
This file is a parameter for the call to sldreg.
Values: Absolute file path. Environment variables are note supported.
Default: /usr/sap/$(SAPSYSTEMNAME)/SYS/global
Related information: Change the Default SLD Data Supplier Configuration (Admin Guide)
Parameter: enable
Description: Enables (true) / Disables (false) the System Landscape Directory data
supplier
Values: true, false
Default: true

Parameter: force_interval
Description: Specifies the time interval in seconds at which the sldreg.xml file is sent to
the SLD even if the file has not changed.
If set to zero or a negative value, documents are sent to the SLD only once.
Values: Integer
Parameter: interval
Description: Specifies the time interval in seconds at which the sldreg.xml file is
generated. If a newly-generated document is the same as the previous
one, it is not sent to the SLD.
If set to zero or a negative value, documents are sent to the SLD only once.
Values: Integer
Default: 300
Parameter: lmstructurepath
Description: Defines the path of the directory lm_structure, which is used by SAP HANA
Lifecycle Management tools.
The tool hdblcm sets the parameter to
/hana/shared/$(SAPSYSTEMNAME)/lm_structure
Default: /usr/sap/$(SAPSYSTEMNAME)/SYS/lm_structure
Parameter: xmlpath
Description: Defines the path to the files sldreg.xml and sldreg.log
Default: $DIR_INSTANCE/$VTHOSTNAME/trace

Section: statisticsserver
This section contains parameters that are related to the statistics server.
Parameter: active
Description: Enables (true)/disables (false) the new embedded statistics server.
Values: true, false
Default: false (< SAP HANA Rev. 80)
Related information: The Statistics Service (Admin Guide)
SAP Note 1925684
Section: topology
This section contains parameters that are related to topology.
Parameter: size
Description: Sets an upper limit of the operating system shared memory that is
allocated for topology information in bytes.
The default value of 268435456 Bytes (256 MB) is sufficient for roughly 1
million tables.
The maximum value is 2147483648 (2 GB).
Default: 268435456 = 256 * 1024 * 1024 (256 MB)

10 Filename: statisticsserver.ini
This configuration file describes parameters for the “old” stand-alone statisticsserver service.
Section: memorymanager
This section contains parameters that are related to the memory manager of the “old” stand-
alone statistics server.
Parameter: allocationlimit
Description: Sets an upper limit of memory usable by the statistics server as a
percentage of the global allocation limit.
Caution: Do not forget the percentage character %.
The value depends on the size of the database (number of tables/views
and size of data) and on the size of the main memory.
Values: 0% to 100% (in theory)
Recommended: 5% to 20%.
In large systems even higher, for example, 25%.
Default: 5%
Section: statisticsserver_general
This section contains parameters that are related to the “old” stand-alone statistics server.
Parameter: active
Description: Turns on (true)/off (false) the collection of monitoring data by the
statistics server.
Values: true, false
Default: true
Related information: The Statistics Service (Admin Guide)
Section: statisticsserver_intervals
Parameter: Interval_purgehistory
Description: Sets a lifetime of collected statistical information in seconds.
When set to a positive value, the collected information will be deleted after
the specified lifetime elapsed.
When set to 0, the collected information will never be deleted.
Default: 86400 (seconds = 1 day)

Parameter: Interval_purgehistory
Section: statisticsserver_view%
Parameter: query
Description: Defines a query string to collect statistical information which is stored in
system views.
Values: String
Default: Not set

11 Filename: webdispatcher.ini
This configuration file describes parameters for the webdispatcher service.
Section: profile
This section contains parameters that are related to the profile of the webdispatcher service.
Parameter: icm/http/logging_n
Description: Defines properties of an HTTP access log, where n is a unique integer
number, for example, 0, 1, 2, etc.
Values: Comma-separated list of one or more of the following key-value-pairs:
PREFIX = the fully qualified path to (and the name of) the application to be
traced, for example, sap.hana.xs.admin
LOGFILE = the location of the log file used to store the trace information;
the location includes a variable for the application's name (access_log_app-
) and the year, month, and day (%y-%m-%d)
MAXSIZEKB = the maximum allowed size of the trace file in kilobytes
SWITCHTF = the time of the day when the new log file is created
(DAY/NIGHT)
LOGFORMAT = the format of the trace file content, for example: CLF
(common log format), CLFMOD (modified CLF), SAP (SAP log file format),
SAPSMD, ...
FLUSH = enable (1) or disable (0) the log flush mechanism
See the SAP Web Dispatcher Help Portal.
Restart required: No for SAP HANA revisions >= 110
Related information: Traces and Trace Configuration for Internal Web Dispatcher (Admin Guide)
Enable HTTP Tracing for an SAP HANA XS Application (Admin Guide)
Setting Up Logging for Inbound Requests (Web Dispatcher Guide)
Parameter: icm/http/mod_n
Description: Defines HTTP request and response header modification rules where n is a
unique integer number, for example, 0, 1, 2, etc.
Values: See the SAP Web Dispatcher Help Portal.
Related information: Modification of HTTP Requests (ICM Netweaver Guide)

Parameter: icm/http/trace_info
Description: Enable (true) / Disable (false) simple HTTP request and response tracing for
debugging purposes.
Trace entries will be written into webdispatcher_<…>_dev_webdisp
Values: true, false
Default: false
Parameter: icm/server_port_n
Description: Defines properties HTTP and HTTPS server ports, where n is a unique
integer number, for example, 0, 1, 2, etc.
PORT: Port number
PROT: Protocol (HTTP/HTTPS)
PROCTIMEOUT: Processing timeout in seconds
When no response has been sent or received after a request, the
corresponding HTTP(S) connection will be closed after the specified
processing timeout elapsed.
Default: icm/server_port_0 =
PROT=HTTP,PORT=80$(SAPSYSTEM),PROCTIMEOUT=600
icm/server_port_1 =
PROT=HTTPS,PORT=43$(SAPSYSTEM),PROCTIMEOUT=600
Guide)
Parameter: icm/ssl_config_n
Description: Defines properties of the SSL connection, where n is a unique integer
number, for example, 0, 1, 2, etc.
ID=ssl_config_main
CRED=SAPSSLS.pse
SNI_CREDS=<semicolon (';') separated list of database PSE files>
Guide)

Parameter: rdisp/trace
Description: Defines the level of the webdispatcher trace.
Trace entries will be written into the file webdispatcher_<…>_dev_webdisp
When set to 1, the trace level is low (few debug information)
When set to 3, the trace level is high (much debug information)
Values: 1, 2, or 3
Default: 1
Related information: Traces and Trace Configuration for Internal Web Dispatcher (Admin Guide)
Parameter: wdisp/filter_xs_internal_uri
Description: Denies (true) / Accepts (false) HTTP(S) access to internal URL prefixes
/sap/hana/xs/internal/…
This parameter is important when an external SAP Web Dispatcher is used
as reverse proxy or HTTP load balancer in front of the system.
Values: true, false
Default: true
Related information: Using SAP Web Dispatcher for Load Balancing with Tenant Databases
(Admin Guide)
SAP Note 1855097
SAP Note 2146931
Parameter: wdisp/sytem_n
Description: Defines properties of a backend system representing the XS Engine, where
n is a unique integer number, for example, 0, 1, 2, etc.
For multitenant database container systems (MDC), one wdisp/system_n
parameter is defined per tenant database. The suffix integer number must
be unique.
Note: The parameters are automatically generated during HANA installation
and must not be changed.
Values: Automatically generated.
See the SAP Web Dispatcher Help Portal.
Default: Automatically generated
Restart required: No. The parameters are automatically generated during startup and after a
parameter in the section [public_urls] has changed.

Parameter: wdisp/sytem_n
Related information: Configuring an External SAP Web Dispatcher for Tenant Databases (Admin
Guide)
SAP Note 1855097
Parameter: wdisp/system_auto_configuration
Description: Enables (true) / Disables (false, empty string, not available) the automatic
configuration of the web dispatcher
Values: true,
false for SAP HANA revisions >= 100,
empty string,
parameter not available for SAP HANA revisions < 100
Default: true
Guide)

12 Filename: xsengine.ini
This configuration file describes parameters for the XS engine service.
Section: application_container
This section contains parameters for the application container component of the XS engine,
which includes not only the XS application container, but also containers for C++ and
JavaScript applications.
Parameter: application_list
Description: Specifies the list of applications that are trusted by the XS. These libraries
may contain the implementations of xscfuncs.
Values: Comma-separated list of shared libraries
Default: libxsdxc, InformationAccess, libtrustmanager, libxsauthenticator,

libxsbase
Related information: SAP HANA XS Configuration Parameters (Admin Guide)
This section contains application-related authentication settings.
Parameter: logonticket_redirect_url
Description: Specifies the URL that is used to redirect a request from a client to a web
server that provides SAP logon tickets for SSO authentication.
When set to an empty string, this function is disabled
Values: URL string
Configure SSO with SAP Logon Tickets for SAP HANA XS Applications
(Admin Guide)

This section contains parameters for application-related communication settings.
Parameter: listenport
Description: Sets the port number on which the XS web server listens for requests.
Values: 5-digit integer with format 3<NN>07, where <NN> is the instance number
of the HANA System.
Default: 3$(SAPSYSTEM)07
Parameter: enforced_http_proxy
Description: Sets a URL of a proxy for outgoing HTTP connections, including fully
qualified domain name and port.
Overrides the outgoing proxy settings used for the HTTP client, for
example, defined in an HTTP/SMTP destination configuration or in an
httpclient.request(), and the proxy specified by the parameter
enforced_outbound_proxy
Values: URL string, including fully qualified domain name and port, separated by
colon delimiter (:), for example, myhost.mycompany.com:myport
Default: Not set or Empty String
Parameter: enforced_https_proxy
Description: Sets a URL of a proxy for outgoing HTTPS connections, including fully
qualified domain name and port.
Overrides the outgoing proxy settings used for the HTTPS client, for
example, defined in an HTTPS/SMTP destination configuration or in an
httpclient.request(), and the proxy specified by the parameter
enforced_outbound_proxy
Default: Not set or Empty String

Parameter: enforced_outbound_proxy
Description: Sets a URL of a proxy for outgoing connections with all protocols, including
fully qualified domain name and port. Protocols can be HTTP, HTTPS,
STMP, SOCKS
Default: Not set or empty string
Edit an HTTP Destination Runtime Configuration (Admin Guide)
Section: customer_usage
This section contains parameters for HANA application services that are used by the HANA
Web Dispatcher HTTP Tracing tool.
Parameter: <path_to_the_XS_application>
Description: The parameter name is a fully qualified path including the name of the XS
application to be traced.
The parameter value is a relative path of the HTTP tracing tool.
Note: The parameter value icm/HTTP/logging_n is the same as the key
defined in the webdispatcher.ini/profile section of the configuration
parameters. n must be a unique number.
Values: Relative path of the tracing tool, including slash (/) delimiters
Example: icm/HTTP/logging_<n> where <n> is a unique number
Default: Not applicable.
The parameter <path_to_the_XS_application> is set (or removed)
automatically when an administrator uses the XS Admin Tools to enable
(or disable) HTTP Tracing on the SAP Web Dispatcher for an application.
Enable HTTP Tracing for an SAP HANA XS Application (Admin Guide)
Section: debugger
This section contains parameters for XS JavaScript debugging tools.
Parameter: enabled
Description: Enables (true) / Disables (false) the XS JavaScript debugging functionality.
Values: true, false
Default: false

Parameter: enabled
Section: httpserver
This section contains parameters for the XS Web server.
The parameters are configured at the DATABASE level for a tenant database.
Parameter: developer_mode
Description: Enables (true) / Disables (false) debug information in HTTP(S) responses,
which avoids trace analysis.
Values: true, false
Default: False
Parameter: embedded
Description: Enables (true) / Disables (false) the execution of XS engine functions in an
embedded mode in the HANA indexserver process, rather than a separate
xsengine process.
To enable the embedded mode, edit daemon.ini, set the parameter
[xsengine] instances to 0, and restart both services indexserver and
xsengine.
Values: true, false
Default: false
Restart required: Yes. Adapt daemon.ini and restart both services indexserver and
xsengine.
Related information: Converting an SAP HANA System to Support Multienant Database
Containers (Admin Guide)
SAP Note 1849775
Parameter: login_screen_background_image
Description: Sets an URL path to an image file displayed as background in the logon
screen.

Parameter: login_screen_background_image
The image file must be publicly available, without the need of
authentication and authorization.
The recommende minimum resolution of the image is 1600 x 1200 pixels.
To query details from the server, y technical use has to be assigned to the
artifact /sap/hana/xs/selfService/user/selfService.sxxqlcc. The technical
user must be assigned to the role
sap.hana.xs.selfService.user.roles.USSExecutor.
Values: URL path, which is a slash-separated list of directory names beginning
with a slash and ending with a file name, for example,
/sap/hana/xs/ui/Image.jpg
Related information: User Self-Service Initialization Parameters (Admin Guide)
Parameter: max_message_size_mb
Description: Sets a maximum message body size of an HTTP(S) request or response in
megabytes (0 = unlimited
When the message body is compressed, the uncompressed size is
compared with the parameter max_message_size_mb.
When set to 0, the message size is not limited.
Default: 100 (megabytes)
Parameter: max_request_runtime
Description: Sets a maximum runtime of an HTTP request targeting an XSJS
application in seconds (0 = unlimited)
When set to 0, the runtime is not limited.
Activate and Execute a Replication Task (Admin Guide)

Parameter: maxsessions
Description: Sets a maximum number of authenticated sessions, where
unauthenticated sessions are not included.
The XS engine issues cookie strings for authenticated sessions to clients
and saves the cookie string at the server side. When the XS engine
receives a request with an associated cookie string, the request can be
assigned to the authenticated session.
When set to 0, no registered / authenticated sessions are available.
Default: 50000
Parameter: root_page
Description: Sets a path to a configurable HTML file to redirect HTTP(S) requests to
root “/” to the specified path.
When not specified, the built-in root page is displayed (“XS Engine up and
running”)
Values: URL path including HTML file
Default: Not specified
Parameter: sessiontimeout
Description: Sets a session timeout for XS HTTP sessions in seconds
Default: 900
Section: jsvm
This section contains parameters that are related to JavaScript virtual machine configuration.
Parameter: max_runtime_bytes
Description: Sets the maximum memory available for an XSJS request in bytes
Default: 256 * 1024 * 1024 (bytes = 256 megabytes)

Parameter: max_runtime_bytes
Parameter: max_runtime_bytes_follow_up
Description: Sets the maximum memory available for a follow-up XS jobs
Default: 1 * 1024 * 1024 * 1024 ( bytes = 1 gigabyte)
Parameter: max_runtime_follow_up
Description: Sets the maximum runtime in seconds for a follow-up XS job
Default: 2 * 60 * 60 (seconds = 2 hours)
Section: odata
This section contains parameters that are related to OData requests.
Parameter: trace_values
Description: Enables (true) / Disables (false) writing of values from the database into
the trace file.
Values: true, false

Default: false
Section: public_urls
This section contains parameters that are related to the public URLs.
The parameters are configured in the DATABASE layer for each tenant database.
Parameter: http_url
Description: Defines a public URL for HTTP access to a specific tenant database of a
multitenant database container (MDC) system.
This URL will be used for the automatic configuration of the web
dispatcher service.

Parameter: http_url
If more than one public URL for HTTP access is required for a tenant,
further parameters http_<other>_url can be added to the section
public_urls, where <other> is an arbitrary name.
Values: http://<virtual_hostname>:80<instance>
Default: http://$(SAPLOCALHOST):80$(SAPSYSTEM)
Guide)
Configuring an External SAP Web Dispatcher for Tenant Databases
(Admin Guide)
Converting an SAP HANA System to Support Multienant Database
Parameter: https_url
Description: Defines a public URL for HTTPS access to a specific tenant database of a
multitenant database container (MDC) system.
This URL will be used for the automatic configuration of the web
dispatcher service.
If more than one public URL for HTTPS access is required for a tenant,
further parameters http_<other>_url can be added to the section
public_urls, where <other> is an arbitrary name.
Values: https://<virtual_hostname>:43<instance>
Default: https://$(SAPLOCALHOST):43$(SAPSYSTEM)
Guide)
Configuring an External SAP Web Dispatcher for Tenant Databases (Admin
Guide)
Parameter: http_<other>_url
Description: Defines a public URL for HTTP access to a specific tenant database using a
further virtual hostname.
The name <other> is arbitrary, for example, webdispatcher.
Values: http://<further_virtual_hostname>:80<instance>
Default: Not set

Parameter: http_<other>_url
Validity: MDC Systems:
Guide)
Guide)
Parameter: https_<other>_url
Description: Defines a public URL for HTTPS access to a specific tenant database using a
further virtual hostname.
The name <other> is arbitrary, for example, webdispatcher.
Values: http://<further_virtual_hostname>:43<instance>
Default: Not set
Validity: MDC Systems:
Guide)
Guide)
Section: scheduler
This section contains parameters that are related to XS job scheduler, which can run XS
javascript or SQLScript background task at regular intervals.
Parameter: enabled
Description: Enables (true) / Disables (false) the XS scheduler
Values: true, false
Default: false
Maintain XS Job Details (Admin Guide)
Description: Sets a default timeout in seconds for XS jobs that do not have a specified
timeout

Parameter: disable_jobs_after_restarts
Description: Sets a maximum number of XS job runs during restarts. After the
specified number of restarts, the XS jobs will not run any more.
When set to 0, the number of XS job runs is unlimited
Default: 5

13 Filename: wlreplayer.ini
This configuration file describes parameters for the Replayer service.
This section contains parameters that are related to the profile of the Replayer service.
.local to select only local network interfaces, for example, 127.0.0.1
Default: .global
Related information: Start the Replayer Service (Admin Guide)

Important Disclaimers on Legal Aspects

This document is for informational purposes only. Its content is subject to change without
notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES,
EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR
PURPOSE.
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are
only examples and are not intended to be used in a productive system environment. The
Code is only intended to better explain and visualize the syntax and phrasing rules of certain
coding. SAP does not warrant the correctness and completeness of the Code given herein,
and SAP shall not be liable for errors or damages caused by the usage of the Code, unless
damages were caused by SAP intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of
accessibility criteria as of the date of publication; it is in no way intended to be a binding
guideline on how to ensure accessibility of software products. SAP specifically disclaims any
liability with respect to this document and no contractual obligations or commitments are
formed either directly or indirectly by this document.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the
reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or
"working days") is used. If when referring to members of both sexes, however, the third-
person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the
right to use the masculine form of the noun and pronoun. This is to ensure that the
documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are
intended to serve as a hint about where to find related information. SAP does not warrant the
availability and correctness of this related information or the ability of this information to serve
a particular purpose. SAP shall not be liable for any damages caused by the use of related
information unless damages have been caused by SAP's gross negligence or willful
misconduct. Regarding link classification, see: http://help.sap.com/disclaimer.

Copyright
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE or an SAP affiliate company. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational
purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in
Germany and other countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.

Frequently Used Config Parameters in SAP HANA 1 2

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Frequently Used Config Parameters in SAP HANA 1 2

Transféré par

Droits d'auteur :

Formats disponibles

Frequently Used Configuration Parameters in SAP HANA

 SAP HANA Platform Software

SAP HANA Platform 2

SAP HANA Platform 3

Section: sld .......................................................................................... 136

SAP HANA Platform 4

1.2 SAP HANA Guides

SAP HANA Platform 5

Section: auditing configuration

SAP HANA Platform 6

SAP HANA Platform 7

SAP HANA Platform 8

SAP HANA Platform 9

SAP HANA Platform 10

SAP HANA Platform 11

SAP HANA Platform 12

SAP HANA Platform 13

SAP HANA Platform 14

SAP HANA Platform 15

SAP HANA Platform 16

SAP HANA Platform 17

SAP HANA Platform 18

SAP HANA Platform 19

SAP HANA Platform 20

SAP HANA Platform 21

SAP HANA Platform 22

SAP HANA Platform 23

SAP HANA Platform 24

SAP HANA Platform 25

SAP HANA Platform 26

SAP HANA Platform 27

SAP HANA Platform 28

SAP HANA Platform 29

SAP HANA Platform 30

SAP HANA Platform 31

SAP HANA Platform 32

SAP HANA Platform 33

SAP HANA Platform 34

SAP HANA Platform 35

SAP HANA Platform 36

SAP HANA Platform 37

SAP HANA Platform 38

SAP HANA Platform 39

During a backup operation, an administrator can override the default

Multi-tenant database container systems:

SAP HANA Platform 40

SAP HANA Platform 41

SAP HANA Platform 42

SAP HANA Platform 43

Caution: Legacy mode is deprecated since SPS 03 and is not supported

Values: Positive integer or zero ( 0 .. 256 )

Restart required: Yes

Validity: All SAP HANA revisions

SAP HANA Platform 44

SAP HANA Platform 45

SAP HANA Platform 46

SAP HANA Platform 47

SAP HANA Platform 48

SAP HANA Platform 49

SAP HANA Platform 50

SAP HANA Platform 51

SAP HANA Platform 52

Parameter: partition_<partition number>_<usage type>__<param name>