Frequently Used Configuration Parameters in SAP HANA

Frequently Used Configuration Parameters in SAP HANA
 SAP HANA Platform Software
Target Audience
■ Consultants
■ Administrators
■ Others
Public
Document version 1.3 – 2017/06/30
Contents
1 Introduction ............................................................................................ 5
1.1 About This Document ................................................................................. 5
1.2 Parameter Management: Tools and Resources ............................................. 5
1.3 SAP HANA Guides ....................................................................................... 5
2 Filename: global.ini ................................................................................. 6
Section: auditing configuration ......................................................................... 6
Section: authentication .................................................................................... 8
Section: backup ................................................................................................ 8
Section: communication ................................................................................. 13
Section: cross_database_access ...................................................................... 21
Section: cryptography..................................................................................... 22
Section: customizable_functionalities .............................................................. 23
Section: executed_statement .......................................................................... 24
Section: execution .......................................................................................... 26
Section: expensive_statement ........................................................................ 29
Section: ha_dr_provider_<classname>............................................................. 36
Section: inifile_checker ................................................................................... 37
Section: internal_hostname_resolution ........................................................... 40
Section: memorymanager ............................................................................... 40
Section: memoryobjects ................................................................................. 44
Section: multidb ............................................................................................. 49
Section: persistence ....................................................................................... 50
Section: public_hostname_resolution .............................................................. 59
Section: resource_tracking .............................................................................. 60
Section: spark_configuration........................................................................... 64
Section: storage ............................................................................................. 66
Section: system_information .......................................................................... 68
Section: system_replication ............................................................................ 68
Section: system_replication_communication ................................................... 81
Section: system_replication_hostname_resolution ........................................... 83
Section: table_placement ............................................................................... 84
Section: threads ............................................................................................. 85
Section: trace ................................................................................................. 86
Section: traceprofile% .................................................................................... 89
3 Filename: attributes.ini .......................................................................... 92
Section: global ............................................................................................... 92
4 Filename: daemon.ini ............................................................................ 93
Section: compileserver ................................................................................... 93
Section: indexserver ....................................................................................... 93
Section: indexserver.c..................................................................................... 94
SAP HANA Platform 2

Section: indexserver.<tenantSID> .................................................................... 94

Section: nameserver ....................................................................................... 94
Section: preprocessor ..................................................................................... 94
Section: sapwebdisp / webdispatcher .............................................................. 95
Section: scriptserver ....................................................................................... 95
Section: statisticsserver .................................................................................. 95
Section: xsengine ........................................................................................... 95
5 Filename: esserver.ini ............................................................................ 96
Section: row_engine ....................................................................................... 96
6 Filename: executor.ini ........................................................................... 98
Section: pythontrace ...................................................................................... 98
7 Filename: indexserver.ini ..................................................................... 101
Section: authentication ................................................................................ 101
Section: authorization .................................................................................. 102
Section: cache .............................................................................................. 102
Section: calcengine ....................................................................................... 104
Section: distribution ..................................................................................... 105
Section: execution ........................................................................................ 106
Section: import_export ................................................................................. 108
Section: joins ............................................................................................... 109
Section: load_trace....................................................................................... 111
Section: mergedog ....................................................................................... 112
Section: optimize_compression ..................................................................... 116
Section: parallel ........................................................................................... 117
Section: partitioning ..................................................................................... 118
Section: password policy .............................................................................. 120
Section: pythontrace .................................................................................... 127
Section: queueserver .................................................................................... 129
Section: repository ....................................................................................... 130
Section: search ............................................................................................. 130
Section: session............................................................................................ 132
Section: smart_data_access .......................................................................... 137
Section: sql .................................................................................................. 139
Section: sql_client_network_io ..................................................................... 144
Section: sqlscript .......................................................................................... 144
Section: sqltrace........................................................................................... 145
Section: table_redist .................................................................................... 149
Section: trace ............................................................................................... 155
Section: traceprofile% .................................................................................. 156
Section: transaction...................................................................................... 156
Section: unload_trace ................................................................................... 158
Section: result_cache.................................................................................... 159
SAP HANA Platform 3

8 Filename: multidb.ini ........................................................................... 160

Section: readonly_parameters ...................................................................... 160
9 Filename: nameserver.ini ..................................................................... 165
Section: auditing configuration ..................................................................... 165
Section: password policy .............................................................................. 165
Section: public_urls ...................................................................................... 165
Section: sld .................................................................................................. 166
Section: statisticsserver ................................................................................ 168
Section: topology ......................................................................................... 169
10 Filename: statisticsserver.ini .............................................................. 170
Section: memorymanager ............................................................................. 170
Section: statisticsserver_general ................................................................... 170
Section: statisticsserver_intervals ................................................................. 171
Section: statisticsserver_view% ..................................................................... 171
11 Filename: webdispatcher.ini .............................................................. 172
Section: profile............................................................................................. 172
12 Filename: xsengine.ini ....................................................................... 177
Section: application_container ...................................................................... 177
Section: authentication ................................................................................ 177
Section: communication ............................................................................... 178
Section: customer_usage .............................................................................. 179
Section: debugger ........................................................................................ 179
Section: httpserver ....................................................................................... 180
Section: jsvm ............................................................................................... 183
Section: odata .............................................................................................. 185
Section: public_urls ...................................................................................... 185
Section: scheduler ........................................................................................ 187
13 Filename: wlreplayer.ini..................................................................... 188
Section: communication ............................................................................... 188
Important Disclaimers on Legal Aspects .................................................. 189
Coding Samples ............................................................................................ 189
Accessibility ................................................................................................. 189
Gender-Neutral Language ............................................................................. 189
Internet Hyperlinks ...................................................................................... 189
Copyright ............................................................................................... 190
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 1.0. In general, configuration parameter values need not be changed because the
default values are designed to meet the demands of most situations.
This document is distributed with SAP Note 2036111 Configuration parameters for the SAP HANA
system. Check this note for information on the latest version of this document.
The content of this document 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.
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 Parameter Management: Tools and Resources

There are a number of other very helpful resources available related to managing
configuration parameters.
1. Firstly, a 10-minute tutorial video by the SAP HANA Academy is available published
in the SAP Community: Configuring SAP HANA Parameters.
2. The frequently asked questions SAP Note gives a very comprehensive technical
introduction to this subject: 2186744 - FAQ: SAP HANA Parameters.
3. The collection of SQL tools available in SAP Note 1969700 SQL Statement Collection for
SAP HANA includes a set of scripts for managing configuration parameters:
HANA_Configuration_Parameters_*. This runs a detailed parameter check which
compares current values, default values and recommended values and gives
references to other SAP Notes for more detailed information.
1.3 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: critical_audit_trail_type
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
SAP HANA Platform 7

Description: Enables (true)/disables (false) global auditing regardless of the enabled
state of the audit policies.
Non-MDC (single container) systems:
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 Note 2122316 MVCC Garbage Collection Is Blocked During Data
Backup When Auditing Is Enabled
SAP Note 1991634 Performance problems when enabling native auditing in
SAP HANA Database
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.
SAP HANA Platform 8

Parameter: log_backup_parameter_file
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)_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)
SAP Note 2330743 DB13: Backup for Backint fails with error 'The following
INI file parameters must have different values'
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.
SAP HANA Platform 9

Parameter: data_backup_parameter_file
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)
SAP Note 2330743 DB13: Backup for Backint fails with error 'The following
INI file parameters must have different values'
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)
Related information: SAP Note 2000003 FAQ: SAP HANA
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
SAP HANA Platform 10

Parameter: enable_accumulated_catalog_backup
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
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)
SAP Note 2309812 Reset SYSTEM user Password - nameserver killed
SAP Note 2083715 Analyzing log volume full situations
SAP Note 2123153 [449] recovery strategy could not be determined
[110512] Backint during HANA Recovery
SAP Note 2243921 Error "[110013] Unexpected end of backup" when
running HANA hdbbackupdiag --check
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)
SAP Note 2154870 How-To: Understanding and defining SAP HANA
Limitations
SAP Note 1642148 FAQ: SAP HANA Database Backup & Recovery
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
Related information: SAP Note 1986958 Common issues / Configuration recommendations for
Symantec NetBackup for SAP HANA
SAP Note 1930978 Recovery of log backups from external backup tool fails
SAP Note 2168842 SAP HANA database recovery using HP Data Protector
9.0 failed due to an invalid line in the backint communication file
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

Parameter: parallel_data_backup_backint_channels
Related information: Multistreaming Data Backups with Third-Party Backup Tools (Admin Guide)
SAP Note 2360533 Multistreaming Backint-based data backups sporadically
failing
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 The internal_network is unknown even if ‘.internal’ is
set
SAP Note 863362 Security checks in SAP EarlyWatch Alert, EarlyWatch
and GoingLive sessions
SAP Note 2183363 Configuration of SAP HANA internal network;

SAP Note 2222200 FAQ: SAP HANA Network
SAP Note 1999797 The internal_network is unknown even if '.internal' is
set
SAP Note 1876398 Network configuration for System Replication in SAP
HANA
SAP Note 2242514 - After adding a host to SAP HANA landscape services of
the new host are not starting
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.
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)
SAP Note 2175672 Migration steps from manual SSL configuration for
internal communication to automatic configuration using system PKI
SAP Note 2287152 SAP HANA DB: IndexRebuild Failing With Unexpected
Exception

Parameter: ssl
SAP Note 2256091 Setup SSL for meta data channel in HANA System
Replication for SP7, SP8 and SP9
SAP Note 2166256 Manual Migration steps for Internal SSL when
migrating to HANA SPS09 or above
SAP Note 2250093 Encryption for XS Advanced activated in HANA revision
110
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.
SAP Note 2312071 SAP HANA SSL – missing option for SSLv2 client hello

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 AuthenticatiSAMLAuthenticator.cpp(00221):ERROR in
libxmlsec – HANA SAML
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:
SAP Note 2093286 Umstellung von OpenSSL auf CommonCryptoLib
SAP Note 2312071 SAP HANA SSL - missing option for SSLv2 client hello
SAP Note 2253695 Korrekturen in CommonCryptoLib 8.4.48
SAP Note 2230230 SSL encryption with commoncrypto makes HANA
System Replication slow
SAP Note 2300435 Crash in Indexserver due to wrong sslcryptoprovider.
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:
SAP Note 1995791 HLM: Updating SAP HANA – Troubleshooting
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

Parameter: sslInternalKeyStore
specific values at HANA System restart.
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

Parameter: sslInternalValidateCertificate
host.
In a tenant database, the parameter is read-only by default. The parameter
can only be changed in the system database.
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 AuthenticatiSAMLAuthenticator.cpp(00221):ERROR in
libxmlsec - HANA SAML
SAP Note 2175664 Migration of file system based X.509 certificate stores
to in-database certificate stores
Parameter: sslMaxProtocolVersion
Description: Sets the maximum available SSL protocol version.

Parameter: sslMaxProtocolVersion
Values: TLS10, TLS11, TLS12, MAX
Default: MAX
MDC systems:
Related information: SAP Note 2312071 SAP HANA SSL - missing option for SSLv2 client hello
SAP Note 2275993 SAP HANA SSL Problem analysis - SSL Record with a
Non-Supported Version Received
Parameter: sslMinProtocolVersion
Description: Sets the minimum available SSL protocol version
Values: SSL30, TLS10
Default: TLS10
MDC systems:
Related information: SAP Note 2312071 SAP HANA SSL - missing option for SSLv2 client hello
SAP Note 2275993 SAP HANA SSL Problem analysis - SSL Record with a
Non-Supported Version Received
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:
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.

Parameter: enabled
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.
“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’s Crypto Kernel receives FIPS 140-2 certificate (SCN)

Parameter: ccl_fips_enabled
information: Validated FIPS 140-1 and FIPS 140-2 Cryptographic Modules (external)
SAP Note 2180024 HANA & ABAP: New Option to Enable/Disable FIPS 140-
2 Certified Crypto Kernel
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 …
Related information: Change the SSFS Master Keys (Admin Guide)
Encryption Key Management (Security Guide)
SAP Note 863362 Security checks in SAP EarlyWatch Alert, EarlyWatch and
GoingLive sessions
SAP Note 2263561 HANA error: parameter mismatch (existence): //[]/ = ''
SAP Note 2193235 SAP HANA system replication is not working after a
change of the master key
SAP Note 1977221 How to handle HANA Alert 57: 'Secure store file system
(SSFS) availability'
SAP Note 2192873 How to change SSFS master key in HANA System
Replication
SAP Note 2183624 Potential information leakage using default SSFS master
key in HANA
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

Parameter: <feature>
MDC systems:
Related information: Disable Features on a Tenant Database (Admin Guide)
System Views:
SYS.M_CUSTOMIZABLE_FUNCTIONALITIES
SYS_DATABASES.
M_CUSTOMIZABLE_FUNCTIONALITIES
Section: executed_statement
This section contains parameters that are related to the collection of executed DDL statement
information.
Parameter: enable_ddl
Description: Enable (true) / Disable (false) the collection of executed DDL statement
information.
The recorded DDL statements and associated information can be queried
using the monitoring view M_EXECUTED_STATEMENTS.
Values: true, false
Default: true
Parameter: maxfiles
Description: Sets a maximum number of trace files (0 = trace file rotation disabled) for
each service and each host.
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 is reached, the oldest trace file is deleted and a new one is
opened.
When the parameter maxfiles is 1 and the maximum file size is reached,
the trace file is deleted and a new is one opened.
The size of the trace files depends on the parameter
[executed_statement] maxfilesize.
Values: Positive integer or zero (0 to 999)
Default: 10

Parameter: maxfiles
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, which are
approximately 10 MB.
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, the parameter maxfilesize is greater
than zero, and the maximum file size is reached, the trace file is deleted
and a new one is opened.
The maximum number of trace files for each service and each host
depends on the parameter [executed_statement] maxfiles.
Values: Positive integer and zero
Default: 10000000 (bytes = approximately 10 MB)
Parameter: trace_flush_interval
Description: Defines a number of traced DDL 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
[executed_statement] 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
[executed_statement] in_memory_tracing_records.
Default: 10

Related information: Expensive Statements Trace Options (Admin Guide)
Parameter: use_in_memory_tracing
Description: Controls target location of executed DDL statements information.
When set to true, executed statements information is stored in a memory
ring buffer. Each service has a separate ring buffer.
When set to false, executed statements information is stored in trace files.
The maximum number of executed statements trace files for each service
and each host depends on the parameter [executed_statement] maxfiles.
Memory ring buffers and trace files have cyclic behavior. When the ring
buffer is full or the maxium number of trace files reached, new executed
statements trace records overwrite the oldest ones.
Values: true, false
Default: true
Section: execution
This section contains parameters that are related to parallel execution.
Parameter: default_statement_concurrency_limit
Description: Sets a maximum target value for the average number of parallel job worker
threads for one statement and one operating system process.
When set to 0 or not specified, the HANA System automatically calculates a
default limit.
In general, specify the parameter default_statement_concurrency_limit so
that the value is less than, preferably, a fraction of the parameter
[execution] max_concurrency, and that the value is greater than, preferably,
a multiple of both parameters [execution] max_concurrency_hint and
[parallel] num_cores.
To get best values for a specific workload and hardware configuration,
careful tuning is required.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
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: default_statement_concurrency_limit
SAP Note 2222250 FAQ: SAP HANA Workload Management
SAP Note 2100040 FAQ: SAP HANA CPU
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 CPU cores than
physical CPU cores.
In general, SAP recommends to set a value that is less than or equal to the
number of available logical cores.
To get best values for a specific workload and hardware configuration,
careful tuning is required.
When the specified target 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.
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.
For each tenant database, fewer logical CPU cores are available than for a
single container system and the recommended values are appropriately
smaller.
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: Zero (=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)
SAP Note 2320604 Recommended Settings in HANA for SoH
Parameter: max_concurrency_hint
Description: Limits the number of jobs to create in a parallelization step during statement
execution. Multiple subsequent 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 threads is
further limited by the parameters [execution]
default_statement_concurrency limit and [execution] max_concurrency and
by the available CPU resources so that fewer job worker threads are
available to process jobs created for a statement.
When set to 0 or not specified, the effective limit is automatically calculated
by the HANA System.
SAP recommends that the parameters max_concurrency_hint 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.
In general, specify the parameter max_concurrency_hint so that the value is
less than, preferably, a fraction of the parameter [execution]
default_statement_concurrency_limit.In large systems with at least four
sockets, SAP recommends to set a value that is less than or equal to the
number of logical CPU cores per socket.
To get the best value for a specific workload and hardware configuration,
Default: 0
Related information: Configuring Workload Management (Admin Guide)

Parameter: max_concurrency_hint
SAP Note 2114710 FAQ: SAP HANA Threads and Thread Samples
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
SAP Note 2180165 FAQ: SAP HANA Expensive Statements Trace
SAP Note 2119087 How-To: Configuring SAP HANA Traces
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

Parameter: enable
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
Related information: SAP Note 2180165 FAQ: SAP HANA Expensive Statements Trace
SAP Note 2088971 How-To: Controlling the Amount of Records in SAP
HANA Monitoring Views
Parameter: maxfiles
Description: Sets a maximum number of trace files (0 = trace file rotation disabled)
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.
Default: 10

Parameter: maxfiles
The minimum value is the default value of 10000000 bytes, which are
approximately 10 MB.
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.
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>,

Parameter: object
<VIEW_1>
Values: String
SAP Note 2018947 Crash during database start up
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.
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_cpu_time
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).
SAP Note 1999997 FAQ: SAP HANA Memory
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.
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.
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
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
SAP Note 2112732 Pool/RowEngine/MonitorView allocates large amount
of memory
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
SAP Note 2196941 SAP HANA Software Replication Takeover Hook
Changes
Parameter: path
Description: Sets the file path for an HA/DR provider script.
is starting.
Default: N/A

Parameter: path
SAP Note 2196941 SAP HANA Software Replication Takeover Hook
Changes
Parameter: provider
Description: Sets the class name defined in an HA/DR provider script.
Note: All HA/DR provider scripts are loaded when the nameserver service is
starting.
Values: String
Default: N/A
SAP Note 2196941 SAP HANA Software Replication Takeover Hook Changes
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 2100052 How to disable parameter mismatch alert
SAP Note 1984641 Name server crash with system replication
SAP Note 2147247 FAQ: SAP HANA Statistics Server
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

Parameter: exclusion_[<inifilename>|*][/<LAYER>]
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/*
exclusion_nameserver.ini/SYSTEM =
landscape/*
exclusion_daemon.ini/HOST = */instances
exclusion_* = traceprofile_*
Related Monitoring INI File Parameter Changes (Admin Guide)
information: SAP Note 2100052 How to disable parameter mismatch alert
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

Parameter: replicate
Related information: Monitoring INI File Parameter Changes (Admin Guide)
SAP Note 1999880 FAQ: SAP HANA System Replication

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)
SAP Note 2183363 Configuration of SAP HANA internal network;
SAP Note 1999797 The internal_network is unknown even if '.internal' is set
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:
Related Information: SAP Note 1840954 Alerts related to HANA memory consumption
SAP Note 1862506 HANA: Statisticsserver runs out of memory (OOM) as of
SPS05
SAP Note 1943067 Recommended Configuration on SAP HANA for
Upgrading to Revision 67 or Higher
SAP Note 2058258 HANA database backup fails with "allocation failed"

error
SAP Note 2085811 SAP HANA SPS 09 Database Revision 90
SAP Note 2133638 HANA indexserver crashes due to an OOM in
UndoHandler during the startup
Limitations
SAP Note 2175606 HANA: How to set allocation limit for tenant databases
SAP Note 2318429 Memory allocation limit - SDS
SAP Note 1921253 Column Store error when clicking on Alerts in HANA
Studio
Parameter: gc_unused_memory_threshold_abs
Description: Sets an absolute threshold of unused memory in megabytes to start
proactive memory garbage collection. (-1 = disabled).
The size of unused memory is the difference between the sizes of
allocated and used memory.
When the size of unused memory exceeds the specified absolute
threshold value, the HANA System starts proactive memory garbage
collection.
When any of the parameters gc_unused_memory_threshold_abs and
gc_unused_memory_threshold_rel is set to -1, the proactive memory
garbage collection is disabled.
Default: 0 (megabytes)
Parameter: gc_unused_memory_threshold_rel
Description: Sets a relative threshold of unused memory in percent of used memory to
start proactive memory garbage collection. (-1 = disabled).
The size of unused memory is the difference between the sizes of
allocated and used memory. When the size of unused memory divided by
the size of used memory exceeds the specified relative threshold value,
the HANA System starts proactive memory garbage collection.
When any of the parameters gc_unused_memory_threshold_abs and
gc_unused_memory_threshold_rel is set to -1, the proactive memory
garbage collection is disabled.
Values: Positive integer, zero, or -1

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.
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 2100566 Frequently Asked Questions for Lenovo/IBM saphana
support script
SAP Note 2101244 FAQ: SAP HANA Multitenant Database Containers
SAP Note 2126889 SAP HANA: Studio and M_LICENSE shows that the
system is locked down though the system is running normal
SAP Note 2133638 HANA indexserver crashes due to an OOM in
UndoHandler during the startup
Limitations
SAP Note 2318429 Memory allocation limit - SDS
SAP Note 1984422 How-To: Analyzing SAP HANA Out-of-memory (OOM)
Dumps
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)

Parameter: oom_dump_time_delta
Default: 86400 (1 day)
Related information: SAP Note 1999997 FAQ: SAP HANA Memory
SAP Note 2289105 SAP HANA DB: Standstill Situation During OOM
Parameter: statement_memory_limit
Description: Sets a statement memory limit on one cluster node in gigabytes (0 or not
set = disabled)
The limit defines the maximum memory that can be temporarily used for
the execution of a statement on one node.
When a statement execution exceeds the specified memory limit, the
SAP HANA System will produce a compositelimit oom dump and the
statement execution will be aborted, but other tasks (threads, statement
executions) of the SAP HANA system are not affected.
Within the time period defined by the parameter oom_dump_time_delta,
the HANA System produces at most one dump file per service. The name
of the dump file contains the string “compositelimit oom”.
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 or missing, there is no limit on the memory consumed by a
single statement on one node.
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 2030423 Special Monitoring of HANA DB - Pilot Usage
SAP Note 2072856 SAP HANA DB: Disabling statement_memory_limit
Feature
SAP Note 2100010 SAP HANA: Popular Misconceptions

Parameter: statement_memory_limit
SAP Note 2122650 Hana Server Crashes with 'Composite limit violation
(OUT OF MEMORY) occurred' in SPS 08
Limitations
SAP Note 2164844 SAP HANA Database: Statement Memory Tracking not
working correctly
SAP Note 2250380 SAP DBTech JDBC: [2048]: column store error: process
parameters error
SAP Note 2289105 SAP HANA DB: Standstill Situation During OOM
SAP Note 2302903 HANA PlanViz "Memory Allocated" figure is higher than
the statement memory limit
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 2359773 SAP HANA can’t start up due to the error “Wrong
statement memory limit threshold”
Section: memoryobjects
This section contains parameters that are related to the configuration of memory objects.

Parameter: page_loadable_columns_limit
Description: Sets an absolute upper threshold value for the total memory size of page
loadable column resources per service in megabytes.
When the total memory size of page loadable column resources per
service exceeds the minimum of the two threshold values resulting from
the parameters
 page_loadable_columns_limit and
 page_loadable_columns limit_rel
(= effective upper threshold value), the HANA System automatically starts
unloading page loadable column resources from memory with first priority
based on an LRU strategy.
When set to a value larger than system memory size, e.g., 1047527424
(=999 Terabytes) or when unspecified, the absolute upper threshold is
unlimited.
SAP does not recommend to set the absolute upper threshold value to 0.
When the effective upper threshold value is less than the effective lower
threshold value, the HANA System does not unload page loadable column
resources from memory with first priority.
Default: 1047527424 (=999 Terabytes)
Related information: Managing cold data in SAP HANA database memory (SCN)
SAP Note 2111649 Configuration parameter for paged memory pool:
documentation for page_loadable_columns_limit and
page_loadable_columns_min_size
Parameter: page_loadable_columns_limit_rel
Description: Sets a relative upper threshold value for the total memory size of page
loadable column resources per service in percent of the process allocation
limit.
When the total memory size of page loadable column resources per
service exceeds the minimum of the two threshold values resulting from
the parameters
 page_loadable_columns_limit and
 page_loadable_columns_limit_rel
(= effective upper threshold value), the HANA System automatically starts
unloading page loadable column resources from memory with first priority
based on an LRU strategy
When set to 100, the relative upper threshold is unlimited.
When unspecified, the HANA System sets the relative upper threshold
value to 10.
SAP does not recommend to set the relative upper threshold value to 0.
When the effective upper threshold value is less than the effective lower

Parameter: page_loadable_columns_limit_rel
threshold value, the HANA System does not unload page loadable column
resources from memory with first priority
Values: Positive integer.
Default: 10
Parameter: page_loadable_columns_min_size
Description: Sets an absolute lower threshold for the total memory size of page
loadable column resources per service in megabytes.
When the total size of page loadable column resources per service falls
below the minimum of the two threshold values resulting from the
corresponding parameters
 page_loadable_columns_min_size and
 page_loadable_columns_min_size_rel
(= effective lower threshold value), the HANA System stops unloading
page loadable column resources from memory with first priority based on
an LRU strategy and switches to a weighted LRU strategy for all resources.
When set to a value larger than system memory size, e.g., 1047527424
(=999 Terabytes) or when unspecified, the absolute lower threshold is
unlimited.
SAP does not recommend to set the absolute upper threshold value to 0.
When the effective lower threshold value is greater than the effective
upper threshold value, the HANA System does not unload page loadable
column resources from memory with first priority
Values: Positive integer or zero.
Default: 1047527424 (=999 Terabytes)
Related information: Managing cold data in SAP HANA database memory (SCN)
SAP Note 2111649 Configuration parameter for paged memory pool:
documentation for page_loadable_columns_limit and
page_loadable_columns_min_size
Parameter: page_loadable_columns_min_size_rel
Description: Sets a relative lower threshold for the total memory size of page loadable
column resources per service in percent of the process allocation limit.
When the total size of page loadable column resources per service falls
below the minimum of the two thresholds values resulting from the
parameters
 page_loadable_columns_min_size and

Parameter: page_loadable_columns_min_size_rel
 page_loadable_columns_min_size_rel
(= effective lower threshold value), the HANA System stops unloading
page loadable column resources from memory with first priority based on
an LRU strategy, and switches to a weighted LRU strategy for all resources.
When set to 100, the relative lower threshold is unlimited.
When unspecified, the HANA System sets the relative lower threshold
value to 5.
SAP does not recommend to set the relative lower threshold value to 0.
When the effective lower threshold value is greater than the effective
upper threshold value, the HANA System does not unload page loadable
column resources from memory with first priority.
Default: 5 (percent of the process allocation limit)
Parameter: unload_lower_bound
Description: Sets a lower threshold for the total size of swappable memory objects in
bytes.
When the total size falls below the lower threshold, the HANA System
stops unloading memory objects from memory.
Due to concurrent system activities, the total size of swappable memory
objects may be temporarily less than the pre-defined threshold.
When set to 0, the SAP HANA system automatically controls the unloading
of memory objects.
Example: 1.649.267.441.664 (1.5 TB)
Default: 0
SAP Note 2127458 FAQ: SAP HANA Loads and Unloads
SAP Note 1993128 SAP HANA: column store table unloads and unloading
behavior of Memory Objects Container
SAP Note 1970537 SAP HANA recovery triggers "Out Of Memory" when
unload_lower_bound is set
Parameter: unload_upper_bound
Description: Sets an upper threshold for the total size of swappable memory objects in
bytes. When that total size exceeds the upper threshold, the HANA System
starts unloading memory objects from memory based on priority and least

Parameter: unload_upper_bound
recent usage.
Due to concurrent system activities, the total size of swappable memory
objects may be temporarily greater than the pre-defined threshold.
When set to 0, the SAP HANA system automatically controls the unloading
of memory objects.
Example: 1.649.267.441.664 (1.5 TB)
Default: 0
Related information: SAP Note 2301382 Increased Used Memory Size due to
Pol/PersistenceManager/PersistentSpace/DefaultLPA/Page (Rev. 110 –
122.05)
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 unless the memory objects are non-
swappable.
When set to 0 or not set, the unloading of memory objects based on
retention period is disabled. The SAP HANA System automatically controls
unloading data from memory.
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 (disabled)
Related information: SAP Note 2058284 Table loads traced into the unload file
SAP Note 1977207 How to handle HANA Alert 55: Columnstore unloads
Parameter: unused_retention_period_check_interval
Description: Sets a check interval for unused memory objects in seconds.
After the specified check interval elapsed, the HANA System searches
memory objects that have not been used for the period of time specified
by the parameter unused_retention_period and should be unloaded from
memory.
When set to 0 or missing, the HANA System automatically determines a

Parameter: unused_retention_period_check_interval
check interval.
Default: 7200 (seconds = 2 hours)
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
Related information: SAP Note 2269429 Error: Create tenant options are not compliant with
current database isolation level
Parameter: mode
Description: Sets one of the modes (multidb, singledb)
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.
Default: 0
Related information: Add a Service to a Tenant Database (Admin Guide)
SAP Note 2101244 FAQ: SAP HANA Multitenant Database Containers
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.

Parameter: basepath_databackup
Default: $(DIR_INSTANCE)/backup/data
Related information: SAP HANA DATABASE BACKUP AND RECOVERY (SCN)
SAP Note 1645183 Changing log mode for SAP HANA DB after SPS2 to
SPS3 upgrade
SAP Note 1703435 Generating a copy of a running instance with database
snapshots
SAP Note 1749467 Copying SAP HANA From a Multiple- to a Single-Host
System
SAP Note 1900728 How to handle HANA Alert 35: 'Existence of Data
Backup'
SAP Note 2106799 backup could not be completed because of a
communication failure
SAP Note 2163068 'AttributeEngine:overflow in numeric calculation' error
after switching to Embedded Statisticserver
SAP Note 2224615 Error When Opening The Backup Configuration Tab
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 1900728 How to handle HANA Alert 35: ‘Existence of Data
Backup’
SAP Note 1703435 Generating a copy of a running instance with database
snapshots
SAP Note 1730930 Using antivirus software in an SAP HANA appliance
SAP Note 1766708 Root partition of Linux box gets full
Parameter: basepath_datavolumes_es

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:

Default: $(DIR_GLOBAL)/hdb/data_es
$(DIR_GLOBAL) is an HANA internal variable, not a shell environment
variable
MDC systems:
Related information: SAP Note 1766708 Root partition of Linux box gets full
Backup’
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_logbackup
Related information: SAP Note 1703435 Generating a copy of a running instance with database
snapshots
SAP Note 2090358 /hana_ssd has been full and HANA DB down
SAP Note 2224615 Error When Opening The Backup Configuration Tab
SAP Note 2163068 'AttributeEngine:overflow in numeric calculation' error
after switching to Embedded Statisticserver
SPS3 upgrade
SAP Note 2106799 backup could not be completed because of a
communication failure
SAP Note 1749467 Copying SAP HANA From a Multiple- to a Single-Host
System
SAP Note 1779221 Recovery of SAP HANA database fails
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)
Backup’
SAP Note 1730930 Using antivirus software in an SAP HANA appliance
SAP Note 1766708 Root partition of Linux box gets full
SAP Note 1816483 Restore when log backups are missing
Parameter: basepath_logvolumes_es

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)
SPS3 upgrade
Parameter: log_backup_timeout_s

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.
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)
SPS3 upgrade
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
Related information: SAP Note 1999998 FAQ: SAP HANA Lock Analysis
SAP Note 2215131 Alert Log Switch Wait Count Ratio
Parameter: log_buffer_size_kb

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 kB .. 16384 kB = 16 MB )
Default: 1024 ( kB = 1 MB )
SAP Note 2215131 Alert Log Switch Wait Count Ratio
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 2357713 SAP HANA DB: Log backup does not start when log
mode is changed from overwrite back to normal online
SPS3 upgrade

Parameter: log_segment_size_mb
Description: Sets a log segment size in megabytes.
The transaction log entries of the HANA System are stored in log buffers,
which are organized/grouped (?) in larger data units, called log segments.
Log segments are processed during backup, recovery, and restart. The
larger the log segments, the longer a restart may take.
Values: Positive integer ( 8 (megabytes) … 4096 (megabytes = 4 gigabyte) )
Default: global.ini: 1024 (megabytes = 1 gigabyte)
dpserver.ini: 8 (megabytes)
nameserver.ini: 64 (megabytes)
scriptserver.ini: 8 (megabytes)
xsengine.ini log: 8 (megabytes)
Restart required: No. Size changes affect only new segments.
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
Related information: SAP Note 2154870 How-To: Understanding and defining SAP HANA
Limitations
SAP Note 1999998 FAQ: SAP HANA Lock Analysis
SAP Note 2169283 FAQ: SAP HANA Garbage Collection
Parameter: savepoint_interval_s

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)
Related information: SAP Note 2100009 FAQ: SAP HANA Savepoints
SAP Note 1977291 Handle HANA Alert 28: 'Most recent savepoint
operation'
SAP Note 1999993 How-To: Interpreting SAP HANA Mini Check Results
SAP Note 1898505 How to handle alert "Check last save point time"
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
Related information: SAP Note 2127458 FAQ: SAP HANA Loads and Unloads
SAP Note 1889081 HANA DB: Growing memory consumption after restart
SAP Note 2107959 Potential data inconsistency after renaming column
store table

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
Related information: SAP Note 1809453 SAP HANA DB: Recovery of a system copy fails
SAP Note 1816483 Restore when log backups are missing
SAP Note 1820553 Incompatibility of data backup and DB configuration
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 SAP HANA SPS06: Network setup for external
communication
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 1928538 SAPControl request failes during the recovery
SAP Note 1906381 SAP HANA SPS06: Network setup for external
communication
SAP Note 1654560 SWPM troubleshooting for storage base copy/refresh
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: cpu_time_measurement_mode
Related information: SAP Note 2100040 FAQ: SAP HANA CPU
SAP Note 2205805 HANA Database doesn't come up after indexserver
restart
SAP Note 2277231 Questionably high DURATION values under on
_SYS_STATISTICS.HOST_LONG_RUNNING_STATEMENTS
Parameter: enable_tracking
Description: Enables (on) / disables (off) tracking of system resources.
For performance reasons, the system resource tracking is disabled by
default.
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)
restart
SAP Note 2207501 Long startup and high cpu usage when undocumented
parameter is set
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)

Parameter: load_monitor_granularity
Default: 10000
Related information: System View: M_LOAD_HISTORY_INFO
SAP Note 2222110 FAQ: SAP HANA Load History
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
SAP Note 2222110 FAQ: SAP HANA Load History
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)
restart
SAP Note 2207501 Long startup and high cpu usage when undocumented

Parameter: memory_tracking
parameter is set
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)
Related information: SAP Note 2114710 FAQ: SAP HANA Threads and Thread Samples
SAP Note 1941894 SAP HANA: Recommended settings for small systems
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
SAP Note 1941894 SAP HANA: Recommended settings for small systems
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_sample_interval
SAP Note 2277231 Questionably high DURATION values under on
_SYS_STATISTICS.HOST_LONG_RUNNING_STATEMENTS
SAP Note 2008396 ST-PI: E2E Datacollectors for HANA
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
Related information: System monitoring view
M_SERVICE_THREAD_SAMPLES
SAP Note 2177604 FAQ: SAP HANA Technical Performance Optimization
Service
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.
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)
SAP Note 2091113 Error 'Connection Failed: The test of the HANA SSO
ticket used to log onto the HANA DB has failed due to: [10]: invalid

username or password: . (FWM 02133)' display while test the SAML SSO
authentication to HANA from CMC
SAP Note 2093286 Migration from OpenSSL to CommonCryptoLib
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.
SAP Note 2091113 Error 'Connection Failed: The test of the HANA SSO
ticket used to log onto the HANA DB has failed due to: [10]: invalid
username or password: . (FWM 02133)' display while test the SAML SSO
authentication to HANA from CMC
SAP Note 2093286 Migration from OpenSSL to CommonCryptoLib
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

Parameter: sslValidateHostNameInCertificate
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
Related information: SAP Note 1823580 issue with HANA scale out system using fibre channel
client
SAP Note 2006604 Troubleshooting issues with SAP HANA appliances
using HP IBRIX
SAP Note 2014225 Unforeseen tool usage leads to data corruption under
certain circumtances
SAP Note 2128188 SAP HANA DB: hdbrename fails with a configured
storage connector on SPS 09
SAP Note 2271741 Devices of Master Node get mounted on Worker Nodes
during Startup when Hana Storage API is used
SAP Note 2122359 adding host might fail when storage connector is used
Parameter: ha_provider_path
Description: Sets a path of an HA (High Availability) provider script.
Related information: SAP Note 2006604 Troubleshooting issues with SAP HANA appliances
using HP IBRIX
SAP Note 1874258 Upgrade with Fiber Channel Storage
Connector(FcClient) fails
SAP Note 2014225 Unforeseen tool usage leads to data corruption under
certain circumtances
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>

Parameter: partition_<partition number>_<usage type>__<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

Parameter: datashipping_logsize_threshold
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)
SAP Note 2332284 Data volume reclaim failed because of snapshot pages
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:

Parameter: datashipping_min_time_interval
Restart required: No restart or re-connect is required.
SAP Note 2300417 SAP HANA SPS 11 Database Maintenance Revision
112.02
SAP Note 2161033 System Replication Takeover after Upgrade to SPS09
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
SAP Note 2348397 Data volume sizes are different between primary and
secondary
Parameter: enable_data_compression

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”.
scenario:
Values: true, false
Default: false

Parameter: enable_full_sync
System Replication Details (Admin Guide)
SAP Note 2165547 FAQ: SAP HANA Database Backup & Recovery in an SAP
HANA System Replication Landscape
SAP Note 2356851 SAP HANA Dynamic Tiering Support for SAP HANA
System Replication
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

SAP Note 2372278 Log Full on Teritry System
System Replication
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:

Parameter: logshipping_async_buffer_size
Default: 67108864 = 64*1024*1024 (64 MB)
SAP Note 2086024 Indexserver failure when using asynchronous
replication
System Replication
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
SAP Note 2213325 Asynchronous Replication Buffer is Overloaded error

Parameter: logshipping_async_wait_on_buffer_full
SAP Note 2130914 Indexserver crashing on Primary Server during
replication
System Replication
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”.
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_replay_logbuffer_cache_size
Description: Sets a maximum size of the replay log buffer cache on the secondary
system in bytes when the operation mode is “logreplay”.
The cache stores log buffers that were shipped from the primary system to
the secondary system to be replayed on the secondary system. When the
total size of shipped log buffers that have not yet been replayed on the
secondary system exceeds the specified cached size, the (most/least

Parameter: logshipping_replay_logbuffer_cache_size
recently) shipped log buffers are written to disk and removed from the
cache. When needed for log replay, those log buffers have to be read from
disk. To avoid bad log replay performance due to disk I/O operations,
select a sufficiently high cache size.
When set to 0 on the secondary system, …
The parameter “logshipping_replay_logbuffer_cache_size” only takes
effect when the parameter “operation_mode” is set to “logreplay” on the
secondary system.
scenario:
Default: 1073741824 (bytes = 1 GB )
Parameter: logshipping_replay_push_persistent_segment_count
Description: Sets a maximum number of log segments on the secondary system to
store log buffers that were read from disk for log replay when the
operation mode is “logreplay”.
The log buffers are cached in those log segments during restart and re-
connect operations or after shipped replay log buffers were read from
disk. See the description of the parameter
“logshipping_replay_logbuffer_cache_size”.
The greater the parameter
logshipping_replay_push_persistent_segment_count, the easier the HANA
System can handle expensive log replay operations without letting wait
the disk I/O operations.
When set to 0 on the secondary system, …
The parameter “logshipping_replay_push_persistent_segment_count”
only takes effect when the parameter “operation_mode” is set to
“logreplay” on the secondary system.
scenario:
Default: 5

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:
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)
Related information:
SAP Note 2000003 FAQ: SAP HANA
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
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
Related information: SAP Note 1999880 FAQ: SAP HANA System Replication
System Replication
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
Validity: All SAP HANA revisions.
SAP Note 2286543 SAP HANA DB: System Replication Secondary Site
Crashes After NZD Upgrade
SAP Note 2330615 Indexserver Crash on Secondary Site with Enabled
Persistence Encryption
SAP Note 2365715 SAP HANA DB: Indexserver Crash with Exception
"Persistent object container migration not allowed in delta data shipping
mode" with System Replication Enabled
SAP Note 2063657 HANA System Replication takeover decision guideline
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:

Parameter: reconnect_time_interval
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
Related information: SAP Note 2159014 FAQ: SAP HANA Security
System
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.

Parameter: enable_ssl
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
SAP Note 2256091 Setup SSL for meta data channel in HANA System
Replication for SP7, SP8 and SP9
System
SAP Note 2159014 FAQ: SAP HANA Security
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

Related information: SAP Note 2183363 Configuration of SAP HANA internal network
SAP Note 2050537 Support for SAP HANA in SAP Landscape Management
SAP Note 1999797 The internal_network is unknown even if '.internal' is
set
SAP Note 2193098 FAQ: SAP HANA Infrastructure Troubleshooting
SAP Note 1876398 Network configuration for System Replication in SAP
HANA
System
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

Parameter: <system_replication_ip_address>
Related information: Configuring Hostname Resolution for SAP HANA System Replication (Admin
Guide)
SAP Note 2183363 Configuration of SAP HANA internal network
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)
SAP Note 2003863 Enable BPC HANA table distribution
SAP Note 2081591 FAQ: SAP HANA Table Distribution
SAP Note 1899817 SAP Business Suite on distributed SAP HANA database
(scaleout): Landscape redistribution
SAP Note 1908075 BW on SAP HANA: Table placement and landscape
redistribution
SAP Note 1715048 BW 7.30 new features for installation or migration
Parameter: same_num_partitions

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
SAP Note 2003863 Enable BPC HANA table distribution
SAP Note 1899817 SAP Business Suite on distributed SAP HANA database
(scaleout): Landscape redistribution
SAP Note 1908075 BW on SAP HANA: Table placement and landscape
redistribution
SAP Note 2334091 BW/4HANA: Table Placement and Landscape
Redistribution
SAP Note 1819123 BW on SAP HANA SP5: landscape redistribution
SAP Note 2129939 How to adjust parameters mismatch for system
replication
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.)
Related information: SAP Note 1847202 Impossible to execute a SAP EPM Add-in report with a
big amount of dimension members to be retrieved
SAP Note 1709026 SAP HANA DB: Crash of the indexserver due RTT issue
SAP Note 1901477 Stack overflow when restarting a HANA service
SAP Note 2081663 Indexserver crash with the error "unexpected high
number of rolling back DTX found"
SAP Note 2099859 SAP HANA DB: indexserver cannot start due to

Parameter: default_stack_size_kb
"unexpected high number of rolling back DTX found"
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.)
Related information: SAP Note 1847202 Impossible to execute a SAP EPM Add-in report with a
big amount of dimension members to be retrieved
SAP Note 1709026 SAP HANA DB: Crash of the indexserver due RTT issue
SAP Note 1901477 Stack overflow when restarting a HANA service
SAP Note 2081663 Indexserver crash with the error "unexpected high
number of rolling back DTX found"
SAP Note 2099859 SAP HANA DB: indexserver cannot start due to
"unexpected high number of rolling back DTX found"
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
Related information: SAP Note 2119087 How-To: Configuring SAP HANA Traces
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

Parameter: flushinterval
written to disk.
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 ( bytes = approximately 10 MB)
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).

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.
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
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.
Parameter: sql_user
Description: Sets a HANA SQL user to filter trace messages for a specific profile.
Values: String
Default: N/A

Parameter: sql_user

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 Wrong data results on persisted indexes
SAP Note 2160391 FAQ: SAP HANA Indexes

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.
When unspecified , 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 '0-7, 16-23'
assigns logical cores with indexes 0 to 7 and 16 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.
Values: Subset of positive integers between 0 and the maximum number of available
logical cores minus 1 where multiple integers are separated by commas and
hyphens.
Default: 0
Related information: Controlling CPU Consumption (Admin Guide)
Limitations

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.<tenantSID>
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

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
Related information: SAP Note 2020877 SAP HANA Database: Executor Pythontrace
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.
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 SAP HANA: standard behavior for SAP logon tickets

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
Related information: SAP Note 2014148 Guidelines for Using the Query Result Cache
Parameter: resultcache_enabled
Description: Enables (yes)/disables (no) the query result cache.

Parameter: resultcache_enabled
Values: yes
no
Default: no
Related information: SAP Note 1980765 Operations with columns containing only one value may
lead to wrong data
SAP Note 2014148 Guidelines for Using the Query Result Cache
SAP Note 1833049 Query Result Cache Configuration in Distributed
Landscape
SAP Note 2081505 Exception thrown by
"RepositoryAccessor::getCalculationScenario"
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).
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),

Parameter: max_cache_size_kb
4194304 = 4 * 1024 * 1024 (4 GB)
Default: 1048576(1 GB)
Related information: For SAP BW systems, apply:
SAP Note 1856131 MultiProvider: Missing clean up of calc scenarios
SAP Note 1942407 Temporary CalcScenarios (*_cs) are not deleted
SAP Note 1988050 Creation of calculation scenarios hangs with 'SharedLock
Enter'
SAP Note 2000002 FAQ: SAP HANA SQL Optimization
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

Parameter: client_distribution_mode
Related information: SAP HANA SQL and System Views Reference (M_CONNECTIONS)
SAP Note 2200772 2200772
SAP Note 1715048 BW 7.30 new features for installation or migration
SAP Note 1743225 HANA: Potential failure of connections with scale out
nodes
SAP Note 1745057 SAP HANA DB: Studio connection to slave nodes fails
SAP Note 1774187 SAP HANA DB: GNav queries do not work in distr.
environment
SAP Note 1785171 SAP HANA DB: Revision 40 using Client Statement
Routing
SAP Note 1840954 Alerts related to HANA memory consumption
SAP Note 2035443 SAP HANA DB: Disconnect of connections after reaching
the idle_connection_timeout in distributed landscapes
SAP Note 2079372 SAP HANA - Statement Routing
SAP Note 2089411 Indexserver crash during CREATE PROCEDURE
SAP Note 2104520 BW InfoCube Compression Results in DB Errorcode 2048
SAP Note 2112849 Hana query only runs on the master node
SAP Note 2144290 SAP HANA SPS 08 Database Maintenance Revision 85.03
SAP Note 2276584 Activation of DSO fails with "Call was not routed to
master"
SAP Note 2358652 Unexpected Result or Unexpected “missing privilege”
Error on SAP HANA Scale-out System
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:

Related information: SAP Note 2222250 FAQ: SAP HANA Workload Management
SAP Note 2230379 SAP HANA SPS 10 Database Maintenance Revision
102.02
Limitations
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 (;)
Related information: SAP Note 2338738 Cannot load table from the specified path
SAP Note 2109565 Potential information disclosure relating to IMPORT
FROM statement in SAP HANA
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)

Parameter: enable_csv_import_path_filter
Related information: SAP Note 2338738 Cannot load table from the specified path
SAP Note 2109565 Potential information disclosure relating to IMPORT
FROM statement in SAP HANA
SAP Note 2211778 Cannot import search customization if SAP Business
One analytics powered by SAP HANA 1.1 PL6 is running on SAP HANA
revision 97
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 2233907 Minimizing the memory footprint of a HANA system.
SAP Note 1998599 How-To: Analyzing high SAP HANA Memory
Consumption due to Translation Tables
SAP Note 2200539 Index Syncpoint Mismatch When Viewing Data in Calc
View
Parameter: translator_hashmap_max_size

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)
Related information: SAP Note 1998599 How-To: Analyzing high SAP HANA Memory
SAP Note 2036494 Use of HASH-based translation tables
Parameter: translator_hashmap_min_size

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)
Related information: SAP Note 1998599 How-To: Analyzing high SAP HANA Memory
SAP Note 2036494 Use of HASH-based translation tables
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
Related information: SAP Note 2088971 How-To: Controlling the Amount of Records in SAP
Parameter: maxfiles
Default: 10
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: active
Related information: SAP Note 1970416 rcSQL=2048 (column store error and dump with
SAPSQL_ARRAY_INSERT_DUPREC)
SAP Note 2057046 FAQ: SAP HANA Delta Merges
SAP Note 2158223 Indexserver crash with BW on HANA and HANA
Revision 95
SAP Note 2105767 Check Delta Log for Statement Rollbacks
SAP Note 1909641 How to handle HANA Alert 10 - ‘Delta Merge
(mergedog) Configuration’
SAP Note 1914357 How to temporarily stop delta merge
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)
SAP Note 2098801 Threads blocked by long running delta merge
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: critical_merge_decision_func
SAP Note 2098801 Threads blocked by long running delta merge
SAP Note 1860493 Out of memory during import migration to HANA
SAP Note 2308083 Disk Size of Table CS_AUDIT_LOG_ Huge also after
Clearing
SAP Note 2200619 Inconsistent Main Entries in History Tables after
Migration to SAP HANA SPS9
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.
Limitations
SAP Note 2351926 Many "Delta Merge was not executed successfully"
Alerts For Secondary Site
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

Parameter: smart_merge_decision_func
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)
SAP Note 1914357 How to temporarily stop delta merge
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: 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

Parameter: token_per_table
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)
SAP Note 2112604 FAQ: SAP HANA Compression
SAP Note 2105761 High memory consumption by RANGE-partitioned
column store tables due to missing optimize compression
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)

Parameter: smart_decision_func
SAP Note 2112604 FAQ: SAP HANA Compression
SAP Note 2105761 High memory consumption by RANGE-partitioned
column store tables due to missing optimize compression
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 subsequent 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
fewer job worker threads are available to process jobs created for a
statement.
When not specified, the effective limit is automatically calculated by the
HANA System.
The value zero is not supported.
SAP recommends that the parameters num_cores and [execution]
max_concurrency_hint have equal values because the two values are used
in the same logical function, but affect different places in the code.
In general, specify the parameter num_cores so that the value is less than,
preferably, a fraction of the parameter [execution]
default_statement_concurrency_limit.
In large systems with at least four sockets, SAP recommends to set a value
that is less than or equal to the number of logical CPU cores per socket.
To get the best value for a specific workload and hardware configuration,

Parameter: num_cores
Default: Not set.
Validity: SAP HANA Revisions >= 80
Related information: Parameters that Control CPU (Admin Guide)
Limitations
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)
Limitations
SAP Note 2222217 How-To: Troubleshooting SAP HANA Startup Times
SAP Note 2317027 SAP HANA DB: Indexserver Crash due to Metadata
Inconsistency for Tables Containing Preload Columns
SAP Note 2331696 SAP Business One workaround for SAP HANA indexserver
crash during startup or exporting a table
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.

Parameter: dynamic_range_check_time_interval_sec
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.
Related information: SAP Note 2081135 Enable "Dynamic Range Partitioning" feature for
DataStore objects (advanced)
SAP Note 2044468 FAQ: SAP HANA Partitioning
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)
Related information: SAP Note 2081135 Enable "Dynamic Range Partitioning" feature for
DataStore objects (advanced)
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.

Parameter: split_history_parallel
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.
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.

Parameter: detailed_error_on_connect
Values: true, false
Default: false
SAP HANA revisions >= 97.03
MDC systems:
SAP Note 2216869 Security improvement of HANA authentication
SAP Note 2354866 "Could Not Save the Connection Data; Invalid User
Name or Password"
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.
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)
SAP Note 2238647 Lumira error 'Unable to connect to HANA' when new
users from HANA are attempting to access data model
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.

Parameter: last_used_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
the nameserver.ini file and for the tenant databases in the corresponding
Default: 6
SAP Note 1855211 Technical database user is repeatedly locked
Name or Password"
SAP Note 1925267 Forgot SYSTEM password
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:

Parameter: maximum_password_lifetime
"maximum_password_lifetime" for the system database is set in the
Values: Positiver integer
Default: 182 (days)
SAP Note 1817513 SAP Data Services (DS) crashes without error when
HANA Data Store is accessed.
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.
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)
SAP Note 863362 Security checks in SAP EarlyWatch Alert, EarlyWatch and
GoingLive sessions
SAP Note 2298750 SAP HANA Platform SPS 12 Release Note
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.

Parameter: maximum_unused_productive_password_lifetime
"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
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.

Parameter: minimum_password_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_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 (?),

Parameter: password_layout
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
Name or Password"
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
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_for_system_user
SAP Note 2249557 Unable to login using SYSTEM user after database
restore from SAP HANA Revision 95 to 102.1
SAP Note 2251556 SAP HANA SYSTEM user can now be locked for too
many failed logon attempts
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
Name or Password"
SAP Note 2134209 SAP IBP / S&OP Password Policy for SAP Managed
Systems
Section: pythontrace
This section contains parameters that are related to the tracing of the Python API.
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:

Parameter: level
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.
off, no, false
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.
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
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

Parameter: inactive_at_service_start
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.
Related information: SAP Note 2140653 Disable loading of asynchronious fullext indexes upon
database startup
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
Related information: SAP Note 2140653 Disable loading of asynchronious fullext indexes upon
database startup
SAP Note 2275523 Creating delivery Units in HANA Studio gives error:
"Cannot create Delivery Unit as content vendor is not defined for this
system".
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
SAP Note 1975448 Problems due to Late Materialization and chunk-wise
Data Processing
SAP Note 1858167 Internal error LateMatColumnSource
SAP Note 1935871 SAP HANA SPS 06 Database Maintenance Revisions
SAP Note 2330763 SAP IBP OD 5.0: Update of HANA parameters after
system change (HDB/AFL update)
SAP Note 2328173 SAP IBP OD 6.2: Update of HANA parameters after
SAP Note 2331876 SAP IBP OD 1608: Update of HANA parameters after
SAP Note 2374839 SAP IBP OD 1611: Update of HANA parameters after
SAP Note 2037733 SQL Statements for SAP HANA Configuration in SAP
Integrated Business Planning 4.0
SAP Note 2114015 S&OP 3.0 SP2 Patch 3 Installation Instructions
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
SAP Note 1975448 Problems due to Late Materialization and chunk-wise
Data Processing

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
Related information: SAP Note 1836774 SAP HANA Database: Database connection is hanging
SAP Note 1900261 How to handle HANA Alert 42: 'Long-Running Cursors'
SAP Note 1910159 How to handle HANA Alert 25: ‘Check number of
connections’
SAP Note 2035443 SAP HANA DB: Disconnect of connections after reaching
the idle_connection_timeout in distributed landscapes
SAP Note 2039052 DI connection times out on HANA, schema is changed to
SYSTEM
SAP Note 2136595 Runtime error DBIF_DSQL2_SQL_ERROR occurrent
during BW data load
SAP Note 2287190 SQL Connections Are Closed due to
"idle_connection_timeout" Although They Are Not Idle
SAP Note 2306375 DBSQL_SQL_ERROR Error with Infopackage load into
BW on Hana
SAP Note 2308459 Troubleshooting '10108' + '9300' errors in relation to
SAP HANA.
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)
Related information: SAP Note 2000003 FAQ: SAP HANA
Parameter: idle_connection_timeout_application_hdbstudio

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
Limitations
connections’
SAP Note 2298926 ERROR transaction error: exceed max
SAP Note 2358652 Unexpected Result or Unexpected “missing privilege”
Error on SAP HANA Scale-out System
connections’
Parameter: maximum_external_connections
Description: Sets a maximum number of connections that are created by user sessions.
Default: 65536

Parameter: maximum_external_connections
Limitations
connections’
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)
SAP Note 2298926 ERROR transaction error: exceed max
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
Related information SAP Note 2222200 FAQ: SAP HANA Network
SAP Note 1836774 SAP HANA Database: Database connection is hanging
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_intvl
SAP Note 2053504 System replication: Hanging client processes after a
takeover
SAP Note 2026457 Error in real-time services recycling - SAP Data Services
14.1
SAP Note 1410736 TCP/IP: setting keepalive interval
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
takeover
14.1
Parameter: tcp_keepalive_time
Description: Sets a time interval between the last packet sent and the first keep-alive
probe in seconds.
Default: 600
Related information SAP Note 1836774 SAP HANA Database: Database connection is hanging
14.1
takeover
SAP Note 1410736 TCP/IP: setting keepalive interval

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
Related information: SAP Note 2142945 FAQ: SAP HANA Hints
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
SAP Note 2195550 IQ error "column not found for query" HANA SDA
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

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
SAP Note 2123714 SAP HANA SPS 08 Database Maintenance Revision 85.02
SAP Note 2198480 FAQ: BW Open ODS View - Query Execution
SAP Note 2100962 FAQ: BW Near-Line Storage with HANA Smart Data
Access: Query Performance
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.

Parameter: calculation_view_unfolding
Values: true, false
Default: true
Related information: SAP Note 2177965 Using Parameter in Table Function Might Lead to
Indexserver Crash
SAP Note 2170436 Result filtered by comparing integral number and real
number in calculation views can differ as the execution mode
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)
Limitations
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
Related information SAP Note 1969700 SQL Statement Colelction for SAP HANA
SAP Note 2124112 FAQ: SAP HANA Parsing

Parameter: plan_cache_parameter_enabled
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.
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.

Parameter: plan_cache_size
Default: 2147483648 = 2 * 1024 * 1024 * 1024 (bytes = 2 Gigabytes)
Related information: System views:
M_SQL_PLAN_CACHE
M_SQL_PLAN_CACHE_OVERVIEW
SAP Note 1763592 HANA: Additional info – Software Update Manager 1.0
SP06
SAP Note 2124112 FAQ: SAP HANA Parsing
SAP Note 2293665 Frequently receive alert of "Plan cache size" ( Alert ID
58)
SAP Note 2040002 Size recommendation for the HANA SQL Plan Cache
SAP Note 2139017 Embedded Statistics Server migration failed while
creating STARTUPMIGRATIONSTEPIMPLEMENTOR procedure
SAP Note 1977253 How to handle HANA Alert 58 - 'Plan Cache Size'
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
Default: true
Related information: Restart Sequence (Admin Guide)
SAP Note 2246594 SAP HANA DB: Index Server Crashes While Loading
Table With Paged Attributes
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 HANA: Additional info – Software Update Manager 1.0
SP06
SAP Note 1844237 SAP HANA: Additional information – Software Update
Manager 1.0 SP08
Limitations
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.
Related information: SAP Note 2142945 FAQ: SAP HANA Hints
SAP Note 2275220 SAP HANA DB: Crash in sub-plan sharing optimization

Parameter: subplan_sharing
for Revision 111
SAP Note 2002208 Indexserver crash in
ptime::qo_TrexSearch::get_join_attr_name
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
Related information: SAP Note 2222200 FAQ: SAP HANA Network
SAP Note 2088971 How-To: Controlling the Amount of Records in SAP HANA
Monitoring Views
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
Related information: SAP Note 2222200 FAQ: SAP HANA Network
SAP Note 2088971 How-To: Controlling the Amount of Records in SAP HANA
Monitoring Views
SAP Note 2081065 Troubleshooting SAP HANA Network
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

Parameter: typecheck_procedure_input_param
an error.
When set to false and type checks fail, the SQLScript procedure prints a
warning in the indexserver trace.
Values: true, false
Default: false
Related information: SAP Note 2254543 Procedure/Function call doesn't allow input string
parameter if it's longer than the length defined
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

Parameter: details
 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
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: flush_interval
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.
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: object
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:
 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.

Parameter: trace
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

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
Related information: SAP Note 2140530 HANA all_moves_physical parameter is set however all
table moves are not physical
SAP Note 1950099 HANA landscape redistribution default configuration
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.
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
Related information: SAP Note 1958216 HANA landscape redistribution configuration
Parameter: balance_by_execution_count_weight

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
Related information: SAP Note 1958216 HANA landscape redistribution configuration
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_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
Related information: SAP Note 1950099 HANA landscape redistribution default configuration
SAP Note 1958216 HANA landscape redistribution configuration
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.
Default: 1

Parameter: balance_by_partnum_weight
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
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
Related information: SAP Note 2210025 HANA DB table reorganization for host removal will not
finish, status: REORG PENDING
Parameter: enable_merge
Description: Enables (true) / Disables (false) table merge operations during table
redistribution.
Values: true, false
Default: true
SAP Note 2143736 FAQ: SAP HANA Table Distribution for BW

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.
 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
SAP Note 1950099 HANA landscape redistribution default configuration
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
Related information: SAP Note 2222250 FAQ: SAP HANA Workload Management
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.
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)
Related information: SAP Note 2169283 FAQ: SAP HANA Garbage Collection
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)
SAP Note 2100010 SAP HANA: Popular Misconceptions
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

Parameter: lock_wait_timeout
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)
SAP Note 1858357 HANA DB: Analysis of wait situations
SAP Note 1969815 Differences between SAP HANA and Oracle in the SQL
area
SAP Note 1909707 How to handle HANA Alert 16: ‘Lock Wait Timeout
Configuration'
SAP Note 2079396 How to handle HANA Alert 49: 'long-running blocking
transaction'
SAP Note 1724865 ST-SER 701_2010_1: Corrections for SAP HANA Checks
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.
The table SYS.TRANS_TOKEN_HISTORY contains information for time-
travel queries.
Default: 1000000
Related information: SAP Note 1910610 Truncated History Table
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.

Parameter: transaction_history_size_limit
Default: 10240 (MB = 10 GB)
Related information: SAP Note 1910610 Truncated History Table
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: maxfiles
Default: 10

Parameter: maxfiles
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 (MB = approximately 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

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

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.
[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 Performance problems when enabling native auditing
in SAP HANA Database
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
SAP Note 2303938 Wrong DB name in System Landscape Directory

Parameter: enable
SAP Note 2082466 Known issues in SAP HANA Platform lifecycle
management (hdblcm)
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
Related information: SAP Note 2303938 Wrong DB name in System Landscape Directory
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

Parameter: xmlpath
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 ABAP adjustments for the new Embedded Statistics
Server
SAP Note 2238254 After an upgrade to HANA Maintenance Revision
102.01, the statisticsserver is disabled.
SAP Note 2136896 SAP HANA DB: HANA cannot start due to disabling
password for _SYS_STATISTICS user
SAP Note 2006652 SAP HANA Statistics Server - Switch to Embedded
Statistics Service fails
SAP Note 2139017 Embedded Statistics Server migration failed while
creating STARTUPMIGRATIONSTEPIMPLEMENTOR procedure
SAP Note 2239843 Error: Collector_Host_Sql_Plan_Cache: invalid column
name: AVG_CHILD_THREAD_COUNT
SAP Note 2091256 HANA Statistics Server - Embedded Statistics Server is
deactivated automatically
SAP Note 2055049 Statistics Server Disabled After Upgrading From SP7 to
SP8
SAP Note 2234421 After Migrating From HANA 97.02 To 102 The
Embedded Statistics Server Is Deactivated
SAP Note 2170779 SAP HANA DB: Big Statistics Server Table
STATISTICS_ALERTS_BASE Leads to Performance Impact on the System
SAP Note 2093572 SAP HANA Migration from Multi-Node to Single-Node
SAP Note 2235033 Embedded Statistics Server disabled due to metadata
mismatch
SAP Note 2215093 After upgrading the HANA Database the statisticsserver
does not work
SAP Note 1917938 Migration of the statistics server for Revision 74 or

Parameter: active
higher
SAP Note 2092033 Embedded Statistics Service Migration Guide
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)
SAP Note 1977101 How to handle HANA Alert 12: 'Memory usage of name
server'

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.
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%
SAP Note 2058258 HANA database backup fails with "allocation failed"
error
SAP Note 1921253 Column Store error when clicking on Alerts in HANA
Studio
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)
SAP Note 2257745 Wrong magic number in file error in statisticsserver
trace

Parameter: active
SAP Note 1933112 statistics server crash frequently
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)
Related information: SAP Note 2182031 ReplicationError with state INFO with event ID... in the
statistics server trace file in Hana
SAP Note 1929538 HANA Statistics Server - Out of Memory
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)
SAP Note 2201212 SAP Web Dispatcher HTTP Tracing
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/redirect_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
Related information: SAP Note 1990354 Changes in internal HANA Web Dispatcher as of HANA
SP9
SAP Note 2012562 Tracing HTTP information for problem analysis
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/server_port_n
SAP Note 1004684 Abort of large content import and transport
SAP Note 1158626 P4 connection to ICM on machine with multiple IPs fails
Parameter: icm/ssl_config_n
Description: Defines properties of the SSL connection, where n is a unique integer
ID=ssl_config_main
CRED=SAPSSLS.pse
SNI_CREDS=<semicolon (';') separated list of database PSE files>
Guide)
Parameter: is/http_show_detailed_errors
Description: Defines properties of the SSL connection, where n is a unique integer
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

Parameter: rdisp/trace
Related information: Traces and Trace Configuration for Internal Web Dispatcher (Admin Guide)
SAP Note 66047 - Screen processor: Trace for error analysis
SAP Note 2161176 Alerting of ABAP shortdumps to CCMS
SAP Note 1767151 CCMS: sapccm4x agent fails after ABAP instance (re-
)start
SAP Note 1453112 CCMS agent and kernel patches
SAP Note 16513 - File system full - what can you do?
SAP Note 112 - T Trace and error information in the "dev_" files
SAP Note 2030976 DP: crash during startup with trace level 2 with non-
unicode kernel
SAP Note 1515602 Trace level increases spontaneously
SAP Note 1370207 Creating work process trace files
SAP Note 1787226 How to change the trace level of Internet
Communication Manager (ICM)
SAP Note 634006 Note on the preclarification of ICM messages
SAP Note 2209809 Message server status is empty
SAP Note 2192284 About Error "NiStrToAddrMask: invalid character in "
SAP Note 1990354 Changes in internal HANA Web Dispatcher as of HANA
SP9
SAP Note 114075 tp cannot be started via RFC
SAP Note 189762 DB2/390: Switch on the trace of the JCL submission
service
SAP Note 162250 DB2/390: DDIC corrections (3.0F,3.1H,3.1I,4.0B)
SAP Note 625305 Profile parameters for the error analysis buffer
SAP Note 1934037 Work process termination when writing DB metadata to
the developer trace
SAP Note 1505012 Trace options of DBSL for Oracle
SAP Note 670398 More tracing for Internationalization, NLS, RSCP,...
SAP Note 1132430 Runtime error SORT_AS_TEXT_DEST_TOO_SHORT
SAP Note 492254 TEXTENV_KEY_INVALID with the language key
SAP Note 875386 CPIC trace activation in SAP J2EE 6.40
SAP Note 1589548 JAVA server log files fill up at a rapid pace: setting the
trace files severity back to installation defaults
SAP Note 1633696 X.509 client authentication via SAP Web Dispatcher
SAP Note 1974723 JRFC trace grows very fast and fills up the system
SAP Note 2107491 JCo/JRFC traces grow and fill up the file system
SAP Note 573800 Reasons for trace files increasing in size
SAP Note 1729512 IBM i: Changes to profile parameters due to upgrade
SAP Note 821883 z/OS: SNA Communication with CICS/IMS Applications
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

Parameter: wdisp/filter_xs_internal_uri
Related information: Using SAP Web Dispatcher for Load Balancing with Tenant Databases
(Admin Guide)
SAP Note 1855097 SAP Web Dispatcher support for SAP HANA XS load
distribution and failover
SAP Note 2146931 Web Dispatcher – XSSRV – Initialization fails because
access to topology information is forbidden
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.
Related information: Configuring an External SAP Web Dispatcher for Tenant Databases (Admin
Guide)
SAP Note 1855097 SAP Web Dispatcher support for SAP HANA XS load
distribution and failover
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)
SAP Note 2360874 SAP Web Dispatcher - Crash If Cascading Web
Dispatchers Are Used

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)
SAP Note 2230072 Error in trace of HANA XSEngine: Attempt to load lib ''
failed. Lib is not allowed!
SAP Note 2083722 HANA Live Browser gives the error: "failed to load
resource: the server responded with a status of 500."
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 SAP HANA XS ENGINE poor database access
performance
SAP Note 2132353 503 Service not available for XS Engine after
conversion to multi-tenant database container system
SAP Note 1953205 Extreme app fails to retrieve data via
sap/sbo/platform/query service

Parameter: embedded
Parameter: login_screen_background_image
Description: Sets an URL path to an image file displayed as background in the logon
screen.
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)
SAP Note 2192925 SAP HANA DB: Formlogin Page Does Not Show
Configured Background Image
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 (MB)
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.

Parameter: max_request_runtime
Activate and Execute a Replication Task (Admin Guide)
SAP Note 1920406 Release Note SAP HANA Application Lifecycle
Management
SAP Note 2283805 Release Notes for SAP HANA Application Lifecycle
Management for SAP HANA SPS 12
Management SPS 08
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

Parameter: root_page
Default: Not specified
Parameter: sessiontimeout
Description: Sets a session timeout for XS HTTP sessions in seconds
Default: 900
Management
Management SPS 08
SAP Note 2160230 SAP DB Control Center - Support for SAP HANA
Multitenant Database Containers
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: 268435456 = 256 * 1024 * 1024 (bytes = 256 MB)

Parameter: max_runtime_bytes
Related information: SAP Note 1920406 Release Note SAP HANA Application Lifecycle
Management
Management SPS 08
SAP Note 2041330 CSV Upload Failure due to out of memory condition
Parameter: max_runtime_bytes_follow_up
Description: Sets the maximum memory available for a follow-up XS jobs
Default: 1073741824 = 1 * 1024 * 1024 * 1024 ( bytes = 1 GB)
Parameter: max_runtime_follow_up
Description: Sets the maximum runtime in seconds for a follow-up XS job
Default: 7200 = 2 * 60 * 60 (seconds = 2 hours)
Related information: SAP Note 2159899 Release Notes for SAP HANA Application Lifecycle

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.
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
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
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)

Parameter: https_<other>_url
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)
Parameter: sessiontimeout
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
© 2017 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 Configuration Parameters in SAP HANA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Frequently Used Configuration Parameters in SAP HANA

Uploaded by

Copyright:

Available Formats

Frequently Used Configuration Parameters in SAP HANA

 SAP HANA Platform Software

SAP HANA Platform 2

Section: indexserver.<tenantSID> .................................................................... 94

SAP HANA Platform 3

8 Filename: multidb.ini ........................................................................... 160

SAP HANA Platform 4

1.2 Parameter Management: Tools and Resources

1.3 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

SAP HANA Platform 40

SAP HANA Platform 41

SAP HANA Platform 42

SAP HANA Platform 43

SAP HANA Platform 44

SAP HANA Platform 45

SAP HANA Platform 46

SAP HANA Platform 47

SAP HANA Platform 48

SAP HANA Platform 49

During a backup operation, an administrator can override the default

SAP HANA Platform 50

SAP HANA Platform 51

Multi-tenant database container systems:

SAP HANA Platform 52

SAP HANA Platform 53

SAP HANA Platform 54

SAP HANA Platform 55