S/4 HANA Monitoring

Large and mid-market companies continue to adopt SAP to run their firms. The powerful SAP platform runs every aspect of a large enterprise from mission-critical lines of business all the way to administrative and support services. For these firms, high availability is paramount; a system outage or performance degradation can cost millions of dollars.

System monitoring is a daily routine activity and this document provides a systematic step by step procedure for Server Monitoring. It gives an overview of technical aspects and concepts for proactive system monitoring.

To Perform SAP HANA Database Administration and monitoring features, SAP HANA Administration Console Perspective can be used.

Administrator Editor can be accessed in several ways −

1. From System View Toolbar − Choose Open Administration default button
2. In System View − Double Click on HANA System or Open Perspective

In Administration View: HANA studio provides multiple tabs to check configuration and health of the HANA system. Overview Tab tells General Information like, Operational Status, system usage, start time of first and last started service, system replication status, version, build date and time, Platform, hardware manufacturer, etc.

It also gives an overview of Used Memory, Peak Memory and its Allocation Limit.

From overview screen we also get information about used resident memory, total memory and physical memory.

Log volume size along with total disk usage and total disk size is also reflected in this screen.

None of the above used space should reach threshold.

To perform daily monitoring we need to perform below checks:

1. Check all services are running
2. Performance –> Threads
3. Performance –> Sessions
4. Performance –> Expensive Statement Trace
5. Performance –> Load

We need to check the load of below 4 parameters:

• CPU utilized
• DB Resident Memory
• Disk Used
• Memory Used

Below is load of CPU at given range of time. We need to make sure it doesn’t cross the threshold.

6. Volume

There are two type of volume present in HANA

Data Volume:

The data volume contains the data from the last completed savepoint.

Log Volume:

The log volume contains all changes on the data volume since the last completed savepoint.

Each log volume contains the file logsegment_<partition_ID>_directory.dat and one or more log segment files (logsegment_<partition_ID>_<segment_number>.dat).

Currently only one log partition is supported for each service, so the default file names are:

logsegment_000_directory.dat and logsegment_000_00000000.dat, logsegment_000_00000001.dat, logsegment_000_00000002.dat and so on.

Log segment files are overwritten depending on the log mode. The log mode determines how logs are backed up. Log volumes only grow if there are no more segment files available for overwriting.

Storage location of data file and log file are at:

7. Configuration –> global.ini
   1. ini contains information like:
8. 1. 1. Basepath_databackup
      2. Basepath_datavolume
      3. Basepath_logbackup
      4. Basepath_logvolume
      5. Cache
      6. Crash dump

Few other .ini files are listed below. We can check them if faced

1. ini
2. ini
3. ini
4. ini
5. ini
6. ini
7. ini
8. Trace Configuration

We can configure trace as per our landscape requirement.

1. Database
2. SQL
3. End to End trace
4. Performance trace
5. User specific trace
6. Expensive statement trace.

In below table we have explained each trace, it’s default status and purpose of the trace.

Locating the Trace/Diagnostic Files

Diagnosis files include log and trace files, as well as a mixture of other diagnosis, error, and information files. In the event of problems with the SAP HANA database, you can check these diagnosis files for errors.

You can access diagnosis files on the Diagnosis Files tab of the Administration editor as shown in below screenshot.

Locating the Trace/Diagnostic Files

Diagnosis files include log and trace files, as well as a mixture of other diagnosis, error, and information files. In the event of problems with the SAP HANA database, you can check these diagnosis files for errors.

You can access diagnosis files on the Diagnosis Files tab of the Administration editor as shown in below screenshot.

High Availability:

SAP HANA offers different kinds of high availability mechanisms, supporting a broad range of recovery scenarios from various faults. One of the feature is System Replication.

System Replication: SAP HANA replicates all data to a secondary SAP HANA system (standard SAP HANA feature). Data is constantly pre-loaded on the secondary system to minimize the recovery time objective (RTO)

In our case our production system is in High Availability. So we need to make sure replication is always active.

If we go inside Landscape, then go inside System Replication. There we can see list of host and its secondary host name.

We must assure replication status is active every time.

Related Content:

https://wiki.scn.sap.com/

http://help.sap.com