Show TOC

Function documentationConfiguration Locate this document in the navigation structure

 

The Configuration section provides information about the configuration of the database and the storage.

Activities

Landscape

Note Note

The information in this section is only relevant for distributed systems and in particular, if failover servers are configured.

End of the note.

The Landscape section provides an overview of the hosts in the SAP HANA database with additional information on status and role. Here, you can check that your SAP HANA database is running and the status of its hosts and processes.

The following information is displayed:

  • Host

    Displays the host name

    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

    Displays the failover status so you can see which servers are active and which are 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

    Displays the role of the nameserver as it is currently running: master or slave nameserver

  • Indexserver Config Role

    Displays the role of the indexserver as it has been configured: worker indexserver or standby

  • Indexserver Actual Role

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

Services

Provides an overview of the status of the system services, including information about resource usage and possible bottlenecks.

You can restart, cancel, or configure a process.

To configure services, it is recommended that you use SAP HANA studio. When changes are made to services, the user name is recorded in the audit log.

The following information is displayed:

  • Host

    The name of the server on which the services are running. For distributed systems, more than one host is displayed.

  • Port number

    Ports used for internal communication by services and processes.

  • Service name

    For each server, the following services are displayed: Nameserver, preprocessor, index server, statistics server

  • Detail

    Indicates whether a server is a master server or normal. This is important for distributed system installed on more than one host.

  • Process ID

    The process ID at operating system level.

  • SQL Port Number

    The port specified by the JDBC connection.

  • Start Time

    Start time of the individual services. The start times displayed may differ from each other because the services can be started at different times on each server.

  • Process CPU(%)

    Current CPU usage for each service

  • Total CPU(%)

    Total CPU usage of the server

  • Process memory(GB)

    The amount of memory allocated to the individual processes.

  • Total Memory(GB)

    Current total used memory on the server.

Note Note

The Memory Process can be higher than the Memory Totals as Memory Process shows what has been allocated and the Memory Total is what is actually being used.

End of the note.
Trace Configuration

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

Note Note

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

End of the note.

  • Global Database Trace

    The global database trace configuration overrides the default configuration for the database traces.

    Default: status: Active with default configuration

    Note Note

    Only database traces with the default configuration are overwritten by the global database trace. If a database trace has a configuration other than the default, the non-default configuration is used for that database trace.

    End of the note.

  • SQL Trace

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

    Default: status: Inactive

  • Database Trace

    If the database trace is configured, the traces for the trace components (for example indexserver or nameserver) of the system are written to files named <servicename>.trc. By default, some of these traces are active.

    To see the output of the database trace, go to  Diagnostics   Database Trace  .

    Default: status: Active with default configuration

  • Performance Trace

    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.

    Default: status: Inactive

  • Expensive Statements Trace

    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.

    Default: status: Inactive

  • SQLDBC Trace

    To see the output of the SQLDBC trace, go to   Diagnostics   SQLDBC Trace  .

    Default: status: Inactive

  • End-to-End Traces

    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

    Default: status: Active with default configuration

  • User—specific Traces

    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.

    If a user trace exists, the options User Trace and Delete User Trace are available. Otherwise these options are grayed out.

Note Note

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

End of the note.
INI Files

Here you can find an overview of the database configuration files, which are also referred to as .ini files.

To display the parameters in a configuration file, expand its node.

The parameter values are displayed for each available host used by the database.

You can change the values for each server individually.

If you have authorization, you can change the values.

  1. To change a parameter value, double-click it.

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

End of the note.
Volumes

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