Configuration

Hosts

You can check that the host(s) and processes in your SAP HANA system are running and the role of each host.

If you are monitoring an SAP HANA single-host system, the overview shows information about the role and status of that host.

If you are monitoring an SAP HANA multiple-host system, the currently active master is shown at the top of the table with a GREEN background, together with information about the roles and the status of the other hosts.

The following information is displayed:

Column	Description
Host	Displays the host name For SAP HANA multiple-host systems only: To change the configured role of the host, choose Configuration.
Host Active	Indicates whether or not the host is active.
Host Status	Indicates whether or not the host is running correctly.
Failover Status	An overview of servers that are active and servers on standby.
Failover Group	If a failover occurs, the server attempts to fail over to a host within the same group.
Nameserver Config Role	Displays the role of the nameserver as it has been configured: MASTER1, MASTER2, MASTER3, or slave nameserver. MASTER 2 and 3 are fallback master servers.
Nameserver Actual Role	The role of the nameserver as it is currently running: master or slave nameserver
Indexserver Config Role	The role of the indexserver as it has been configured: worker indexserver or standby
Indexserver Actual Role	The role of the indexserver as it is currently running: master indexserver, worker indexserver, or standby indexserver
Storage Partition	Displays the number of the `mnt000...` subdirectory used below the DATA and LOG directory.

To display or hide an overview of information about the connection, choose Show/Hide DBCON Information.

Trace Configuration

You can see the status of each trace, switch traces on and off, and change the options for each trace type.

Note

To change the options, you need the appropriate authorization. If you only have restricted authorization, the change options are not available.

More information: Authorizations for DBA Cockpit in Related Information

You can configure the following traces:

Table 1: Functions for Traces
Trace	Description
Database Trace	Default status: Active with default configuration Choose Change Database Trace. Select the desired trace level for the services or components that you are interested in. The higher the trace level, the more detailed the information collected by the database trace will be. Choose Save. Note Only database traces with the default configuration are overwritten by the database trace. If a database trace has a configuration other than the default, the non-default configuration is used for that database trace.
SQL Trace	Default: status: Inactive If the SQL trace is active, the database calls for the specified database or application users are traced. The trace data is stored in files starting with `sqltrace_<servername>`.
Performance Trace	Default: status: Inactive The performance trace traces system performance. You can configure the trace for a single specific database user and a single specific application user. To trace the execution plan in addition, choose Plan Execution. You can specify the trace duration. If you want to trace a specific scenario, ensure that you enter a time greater than the time the scenario needs to run. To trace general system performance, enter an appropriate time. After the specified duration, the trace stops automatically. Trace data is saved to the file you specify.
Expensive Statements Trace	Default: status: Inactive The expensive statements trace traces all statements that take longer than a time you specify. The traced data is written to a file called `<indexserver>_<servername>_expensive_statements.trc`.
SQLDBC Trace	Default: status: Inactive More information: SQLDBC Trace in Related Information
End-to-End Traces	Default: status: Active with default configuration The predefined end-to-end traces are used by applications to record the steps through all the available trace components (for example `indexserver` or `nameserver`) in a configuration. When an end-to-end trace is used, the traces for the trace components are written to files named `<servicename>_<servername>_<end-to-endtracename>.trc`.
User-specific Traces	If a user trace exists, the options User Trace and Delete User Trace are available. Otherwise these options are not available. If a user-specific trace is active, the traces for trace components (for example `indexserver` or `nameserver`) for a specific database or application user are written to files named `<servicename>_<servername>_<contextname>.trc`.

Tip For traces that are active by default, you can restore the default configuration from the configuration dialog.

SQLDBC Trace

SQL Database Connectivity (SQLDBC) is a runtime environment for the development of database applications and database interfaces.

SQLDBC consists of the runtime library libSQLDBC, the software development kit SQLDBC SDK and the tool sqldbc_cons. SQLDBC offers a range of trace options.

Using SQLDBC, applications can:

Access SAP HANA databases
Execute SQL statements
Edit data

Table 2: Functions for SQLDBC Trace
Action	Steps
To activate the SQLDBC trace	Select the required process. Choose one of the following options: SQL (Switch on SQL trace) SQL Statements (simplest trace, adequate for most analyses) Long (Switch on long trace) Method calls with call parameters (most comprehensive trace) Packet (Switch on packet trace) Communication packages Specify the size of the trace file. The trace files contain a file named sqldbctrace-<pid>.prt, where <pid> is the process ID. The trace files are overwritten cyclically.
To deactivate the trace	Select the process for writing to the trace and then select Switch Off.
To specify the size of the trace file	Choose Goto Maximum File Size .
To analyze and display the SQLDBC trace	Select the required trace file to analyze the trace and choose Display File.

INI Files

An overview of the database configuration files, which are also referred to as .ini files.

Table 3: SAP HANA Configuration Files
Task	How To...
To display the parameters in a configuration file	Expand its node. The parameter values are displayed for each available host used by the database.
To change a parameter value	If you have authorization, you can change the parameter values. You can change the values for each server individually. To change a parameter value, double-click it. In the dialog box, you can specify a value as follows: SYSTEM: Changes are applied system-wide to all servers. Host: Select a host. Changes are applied to this host only. Note The SYSTEM layer overwrites the DEFAULT layer. The HOST layer overwrites the SYSTEM layer for the current host. If the SAP HANA database is not distributed, the HOST layer is not displayed.

Volumes

This section provides an overview of information about volumes and disks in an SAP HANA insatallation.

For each volume and disk, there are two entries for each service. One entry shows the data size and the other the log size.

Backup Configuration

This section provides an overview of the configuration options for data and log backup, and for third-party backup tools.

Note

To work with the backup configuration functionality, you need the SAP HANA privileges BACKUP ADMIN and CATALOG READ.

More information: SAP HANA System Privileges in Related Information

Note The functionality offered in the Backup Configuration section is the same as the configuration functionality in the Backup Console in SAP HANA studio.

You can configure the following backup settings:

Setting	Description
Backint Settings: Backint Parameter File	The default configuration for a third-party backup tool is defined when the tool is installed. After a backup tool has been installed, you can back up and recover an SAP HANA database without making any further changes. However, you have the option to change some of the tool configuration settings. Note If the Backint agent is not installed, you cannot change the Backint parameter files. If required by the third-party backup tool, you can specify a Backint parameter file for data backup and for log backups. The content and syntax of the parameter files is tool-specific and defined by the tool vendor. For more information, see the documentation for the third-party backup tool. The parameter files for third-party backup tools are stored in the following path: `/usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/` Note If you do not store the Backint parameter files in this path, create a symbolic link pointing from this shared area to the actual location of the parameter files.
File-Based Data Backup Settings: Destination	Specify the default destination for file-based data backups. By default, data backups are written to: `$DIR_INSTANCE/backup/data` You can specify a different destination when you start a backup. Each SAP HANA service writes backup data to a separate file in the specified destination in the file system. Note For third-party backup tools (Backint for SAP HANA), the backup destination is always `/usr/sap/<SID>/SYS/global/hdb/backint` for both data backup and log backups. For third-party backup tools, you can only change the log backup interval.
File-Based Data Backup Settings: Limit Maximum File Size	Specify a size limit for the data backup files (if required). For file-based data backups, you may need to limit the maximum size of a single backup file. For example, due to file system limitations. If the size of a data backup file for a service exceeds a specific limit, SAP HANA splits the file into multiple smaller files.
Log Backup Settings: Destination Type	`file` backs up the database to files in the file system. Each SAP HANA service. writes backup data to a separate file in the specified destination in the file system. `Backint` backs up the database using a third-party backup tool. Each SAP HANA service starts the Backint agent and sends the backup data to the third-party backup tool. Note The `Backint` option is only available if a third-party backup tool is installed.
Log Backup Settings: Destination	Specify the destination for log backups. By default, file-based log backups are written to: `$DIR_INSTANCE/backup/log` This destination can be changed to another path in the file system or to a third-party backup destination. Log backup names are generated automatically. Unlike the data backup names, no parts of the log backup names are user-defined.
Log Backup Settings: Backup Interval	Specify the interval for log backups. The default value is 900 seconds. This is the interval at which the log segments are backed up when a commit has taken place. Specify an appropriate timeout for log backups that enables you to recover an SAP HANA database with a good Recovery Point Objective (RPO). Alternatively, you can configure the parameter `log_backup_timeout_s` in the `global.ini` configuration file. Note If the log segments become full before the interval, the logs are backed up anyway.