(DI-2205) HANA Database

Owned by SNP
Last updated: May 31, 2022 by Marian Vidra
4 min read

This page describes how to add monitoring for a standalone SAP HANA database from a central monitoring installation. More details about the central monitoring system can be found in the chapter Install on central SAP system.

If HANA database is used as standard database for a central or remote SAP system, you might start the additional collector jobs with monitoring profiles HDB_5MIN and HDB_1DAY for HANA Database monitoring without adding a new extra system. More details about scheduling new collector jobs for mentioned monitoring profiles can be found in the chapter Create and schedule a Collector job.

Prerequisites for an external HANA Database monitoring

  • A valid connection user created within the monitored HANA database. For security and password management reasons, we recommend creating a new specific monitoring user (e.g. CBMON-<SID of the central monitoring system>).

  • A valid database connection defined in DBCON on the central monitoring system, as described on the page Create a Secondary HANA Connection.

    • A connection test for database connection can be done by executing report “ADBC_TEST_CONNECTION” or directly in transaction “DBACOCKPIT”.

    • If HANA Database monitored through a remote SAP system via RFC destination, a valid database connection needs to be defined in DBCON on the monitored remote SAP system.

Add a new system for standalone HANA Database

If you want to monitor a standalone HANA database as a separate system, you need to choose one of the following scenarios:

  1. Monitoring of standard HANA database through default DB connection on the central monitoring system

    1. HANA Database is the standard database of the central SAP system. No additional DB connection (DBCON) is needed, but the ‘DEFAULT’ DB connection can be used. You might use this scenario only when you don’t want to monitor the standard HANA database through the already monitored SAP system by starting the additional collector jobs as mentioned at the beginning.

  2. Monitoring of HANA database through a secondary DB connection on the central monitoring system

    1. HANA Database is not the standard database of the central SAP system. In this scenario, the secondary DB connection for the HANA database needs to be created on the central SAP system as described on the page Create a Secondary HANA Connection.

  3. Monitoring of HANA database on the remote SAP system connected via RFC destination

    1. HANA Database is installed on the remote SAP system. When adding a new system for HANA Database in this scenario, you need to define:

      1. working RFC Destination to be able to communicate with a remote SAP system.

      2. valid DB Connection name (DBCON) available on the remote SAP system to be able to communicate with HANA Database.

        • If HANA Database is the standard database of the remote SAP system, the default DB connection can be used as mentioned in scenario 1.

        • If HANA Database is not the standard database of the remote SAP system, the secondary DB connection has to be used as mentioned in scenario 2.

To add a new system for standalone HANA database monitoring, please follow these steps on the central monitoring system based on your selected scenario:

  1. Select the main system type HANA Database.

  2. Following screen appears for HANA system information.

  3. Enter System name (e.g. HANA_DB) and Description.

  4. Enter a valid DB Connection name based on selected (DI-2205) HANA Database.

  5. Press Check DB connection to make sure that DB connection works correctly.

    1. If any error occurred, press the button Open DBCO transaction next to the DB Connection field and maintain this connection according to the steps described on the page Create a Secondary HANA Connection.

    2. You can test this DB connection with a report ADBC_TEST_CONNECTION or directly in transaction DBACOCKPIT on the central SAP system.

  6. (Optional) If HANA Database is monitored from a central SAP system, keep the Destination field empty.

If you would like to monitor the HANA Database from a remote SAP system ((DI-2205) HANA Database), you need to enter valid RFC Destination (configured ABAP connection to a remote SAP system). If RFC Destination filled, please make sure that defined DB connection name exists on the remote SAP system. If not, you need to create a new DB connection for HANA database on this remote SAP system as described on the page Create a Secondary HANA Connection.

You might change the Timeout [s] value to set the maximum time in seconds for RFC connection ping.

  • When the RFC connection does not respond after the maximum time set here, then a red light icon in the monitoring pool is displayed (remote SAP system is not accessible).

  • Recommended value for RFC connection ping is at least 10 seconds (also for fast connections)

7. Confirm setup to add the system

8. The following screen appears with the auto-detected DB server(s). Make sure that the Monitor flag is selected and press Confirm.

9. After confirming the Database server(s), a new system for the standalone HANA database was added. You might start the monitoring of the standalone HANA database by clicking the Start default monitoring button in the menu bar. It starts the Collector jobs for HANA database monitoring.