Database (generic)

This chapter describes how to add monitoring for a standalone database from a central monitoring installation. For more information about the central monitoring system, see the chapter Installing CrystalBridge® Monitoring. Currently, the following database systems are supported to be monitored as standalone databases with configured database connection:

  • HANA: check dedicated system type existing for HANA database.

  • Oracle: check dedicated system type existing for Oracle database.

  • DB6

  • SAP MaxDB

  • MSSQL

  • Sybase ASE

NOTE For this database system type, there is the predefined monitoring profile DB_1HOUR, but the specific collector job for this profile is not automatically started by start default monitoring functionality. All collector jobs for DB related monitoring must be scheduled manually. For more information, refer to the chapter Scheduling the Monitoring of KPIs.

Prerequisites for external database monitoring

  • A valid connect user has been created within the monitored database. For security and password management reasons, we recommend creating a new specific monitoring user, e.g. CBMON-<system ID of the central monitoring system>.

  • A valid database connection has been defined in the table DBCON on the central monitoring system according to the steps described in the chapter Creating a Secondary Database Connection.

    • A connection test for the database connection can be performed by executing the report ADBC_TEST_CONNECTION or via transaction DBACOCKPIT.

    • If the database is monitored through a remote SAP system via RFC destination, a valid database connection must be defined in the table DBCON on the monitored remote SAP system.

Adding a New System for a Standalone Database

To monitor a standalone database as a separate system, choose one of the following scenarios:

  • Monitoring the standard database through the default database connection on the central monitoring system

    The database is the standard database of the central SAP system. No additional database connection (DBCON) is needed, but the database connection DEFAULT can be used.

  • Monitoring the database through a secondary database connection on the central monitoring system

    The database is not the standard database of the central SAP system. In this scenario, the secondary database connection for the database on the central SAP system has to be created.For more information, refer to the chapter Creating a Secondary Database Connection.

  • Monitoring the database on the remote SAP system connected via RFC destination

    The database is installed on the remote SAP system. When adding a new system for the database in this scenario, the following has to be defined:

    • A working RFC destination to communicate with a remote SAP system.

    • A valid database connection name (DBCON) available on the remote SAP system to communicate with the database.

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

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

Based on your selected scenario, on the central monitoring system, proceed as follows to add a new system for standalone database monitoring:

  1. Start transaction /DVD/MON.

  2. In the main toolbar, click Add system.

  3. Select the main system type Database (generic).

  4. Click Confirm.

  • The screen DB system appears.

  1. In the System name field, enter a custom system name.

  2. In the Description field, enter a suitable custom description.

  3. In the DB connection field, enter a valid database connection name based on the selected scenario.

  4. Click Check DB connection to ensure that the database connection works correctly.

  5. If any error occurs, click Open DBCO transaction next to the database connection field and maintain this connection according to the steps described in the chapter Creating a Secondary Database Connection.

  6. Test the database connection by executing the report ADBC_TEST_CONNECTION or via transaction DBACOCKPIT on the central SAP system.

  7. Optional: If the database is monitored from a central SAP system, leave the RFC destination field empty.

    NOTE

    If you want to monitor the database from a remote SAP system (see scenario 3 above), you must enter a valid RFC destination in order to provide a configured ABAP connection to a remote SAP system. If you fill out the RFC destination field, ensure that the defined DB connection name exists on the remote SAP system. If not, you must create a new database connection for the database on this remote SAP system as described in the chapter Creating a Secondary Database Connection.

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

    • If the RFC connection does not respond after the maximum time set here, a red light icon is displayed in the list of monitored systems. This icon indicates that the system is not accessible.

    • The recommended value for the RFC connection ping is at least 10 seconds (also for fast connections).

  8. Click Confirm to add the system.

  • A screen appears with the auto-detected database server(s).

  1. Ensure that the Monitor flag is selected.

  2. Click Confirm.

The system automatically detects the IP address for all database servers, which is used as the full network address of this server. If necessary, the address can be adjusted in the system settings.

After confirming the database server(s), the new system for the standalone database is added.

There is a predefined monitoring profile with the name DB_1HOUR, but the specific collector job for this profile is not automatically started by start default monitoring functionality. All collector jobs for DB related monitoring must be scheduled manually as described in chapter Scheduling the Monitoring of KPIs.