Page Comparison

Technical prerequisites

The monitoring system requires software to allow connectivity for the Oracle database (especially in heterogeneous landscapes). Specifically, the requirements are:

• SAP Kernel DBSL for Oracle DB

• Oracle Client Software on Application Servers (e.g. SAP Note 819829)

• Depending on the setup changes, application server restarts can be necessary

Prerequisites for an external Oracle database monitoring

• Server defined in SNP CrystalBridge® Monitoring requires a connection to the Oracle database.

• A valid connection user created within the monitored Oracle database. For security and password management reasons, we recommend creating a new specific monitoring user (e.g. CBMON-<SID of the central monitoring system>). More details about connection users can be found on the page Prerequisites for Oracle Connect User.

• A valid database connection defined in table DBCON on the monitored SAP system, as described on the page Create a Secondary connection to Oracle Database.

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

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

Add a new system for standalone Oracle database

Anchor
Scenarios Scenarios

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

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

   1. Oracle 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 Oracle database through the already monitored SAP system by starting the additional collector jobs as mentioned at the beginning.

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

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

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

   1. Oracle database is installed on the remote SAP system. When adding a new system for the Oracle 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 the Oracle database.

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

         • If the Oracle 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 Oracle database monitoring, please follow these steps on the central monitoring system based on your selected scenario:

1. Select the main system type Oracle database

   

2. Following screen appears for Oracle system information.

   

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

4. Enter a valid DB Connection based on the selected (DI-2305) Oracle Database.

   Anchor
   DB-Connection-for-Oracle DB-Connection-for-Oracle

   

5. Press Check DB connection

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

   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 the Oracle database is monitored from a central SAP system, keep the RFC Destination field empty.

7. Confirm the setup

The system will ask you to generate new KPIs specific to the Oracle database. If confirmed, please check the chapter Guide for KPI generator for Oracle system metrics before you continue into the Steps to complete the setup.

Info
If you don’t want to generate these KPIs at this point, you can skip this process and continue directly with the next steps to finish adding logic. There is a possibility to generate these KPIs manually later as described on the page Generate KPIs specific for Oracle database monitoring.

Anchor
Steps-to-complete-the-setup Steps-to-complete-the-setup

Steps to complete the setup

Regardless of whether new KPIs for Oracle database monitoring were generated or not, the following screen appears with the auto-detected Database server(s). Make sure that the Monitor flag is selected and press Confirm.

• There is automatically detected the IP Address for all database servers, which is used as a full network address of this server. This address might be adjusted in (DI-2305) System settings.

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

Info
If new KPIs for Oracle database monitoring were not generated, the collector job for profile XORA_5MIN will be not started.

Guide for KPI generator for Oracle system metrics

Anchor
Guide-for-KPI-generator-for-Oracle-system-metrics Guide-for-KPI-generator-for-Oracle-system-metrics

If the user decided on an option to generate new KPIs, the screen forthe KPI generator for Oracle system metrics is automatically displayed. There are two scenarios to generate new KPIs based on the previous configuration (whether Oracle database is monitored from a central or remote SAP system).

Generate KPIs directly from the central SAP system

Oracle system metrics are retrieved directly through configured DB connection from the central SAP system. For this scenario, the following screen is displayed and only a valid DB connection must be set.

To generate new KPIs for Oracle system metrics, please follow the steps described in the chapter (DI-2305) Generate KPIs specific for Oracle database monitoring and then go back (F3) from the KPI generator report and continue at Steps to complete the setup.

Generate KPIs from the remote SAP system through RFC destination

Oracle system metrics are retrieved through a remote SAP system via the configured valid RFC destination and DB connection (this DB connection must be defined on the remote SAP system). For this scenario, the following screen is displayed and a valid RFC Destination and DB connection must be set.

To generate new KPIs for Oracle system metrics from the remote SAP system, please follow the steps described in the chapter (DI-2305) Generate KPIs specific for Oracle database monitoring and then go back (F3) from the KPI generator report and continue at Steps to complete the setup.