Oracle Database

This page explains how to prepare a Oracle database for the connectivity to SAP Focused Run.

Currently the following monitoring application are supported for Oracle databases:

Preparations in the Managed Database

TaskActions
Install Oracle DatabaseOptionally install the latest Oracle DB and latest Patches from support.sap.com/swdc -> Databases -> Oracle

Create DB monitoring user and set connection credentials

 

No specific tasks are to do be performed for Oracle database. The SAP Host Agent can manage the connection to an Oracle DB by itself without additional credential.

In the case of connection problems, see SAP Host Agent Troubleshooting Guide (Oracle DB) page.

As of version 7.22 PL53, SAP Host Agent provides support for named logon to an oracle database system to execute read-only functions 
For details please refer to 3080093 - Manage Connect User Credentials for ORACLE databases in SAP Host Agent

Run Outside Discovery on the HostAs prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in Preparing Outside Discovery page.
Support of BR*tools based metricsPrerequisites: at least SAP Host Agent 7.22 PL57 and SAP Focused Run 3.0 monitoring content delivery version 17.
Monitoring of Oracle RAC 

Prerequisites:

  • at least SAP Host Agent 7.22 PL56 to be installed on all Oracle RAC hosts
Configuration steps:
  • create the http.server.settings file (2724592 - SAP Host Agent Outside Discovery ComputerSystem configuration --> http.server.settings permissions) under /usr/sap/hostctrl/exe/config.d folder on both hosts. There you have to maintain the following:

    OutsideDiscovery {​​​​​​​
        DatabaseDiscoveryMethod : databasesystem
        DatabaseOverride {​​​​​​​
            dbsystem : <dbtype>/<dbname>/<dbinstance>/<hostname> {​​​​​​​​​​​​​​
                set {​​​​​​​​​​​​​​​​​​​​​
                    no_addr_local_check {​​​​​​​​​​​​​​​​​​​​​
                        identicaldbhost : <virtual-hostname>*
                    }​​​​​​​​​​​​​​​​​​​​​
                }​​​​​​​​​​​​​​​​​​​​​
            }​​​​​​​​​​​​​​​​​​​​​
        }​​​​​​​​​​​​​​​​​​​​​
    }​​​​​​​​​​​​​​​​​​​​​
    * <virtual-hostname> should be = Logical host name for SAP Solution Manager mentioned in the SAP note 1738351.
    Remark: please do not use a scan listener hostname for that purpose!
  • Restart the Host Agent on both servers or execute  /usr/sap/hostctrl/exe/saphostctrl -function ReloadConfiguration.
  • Execute the Outside Discovery - as a result there should be one virtual DB linked to the physical DB containing both (all) instances.
  • Reconfigure the system monitoring by re-applying the database template or executing the Simple System Integration

Example of the configuration file for one DB running on two Oracle RAC nodes:

1 Oracle DB on host 1:
OutsideDiscovery {​​​​​​​​​​​​​​​​​​​​​
    DatabaseDiscoveryMethod : databasesystem
    DatabaseOverride {​​​​​​​​​​​​​​​​​​​​​
        dbsystem : ORA/ABC/ABC001/oraxdb01 {​​​​​​​​​​​​​​​​​​​​​
            set {​​​​​​​​​​​​​​​​​​​​​
                no_addr_local_check {​​​​​​​​​​​​​​​​​​​​​
                    identicaldbhost : orax-db
                }​​​​​​​​​​​​​​​​​​​​​
            }​​​​​​​​​​​​​​​​​​​​​
        }​​​​​​​​​​​​​​​​​​​​​
   }​​​​​​​​​​​​​​​​​​​​​
}​​​​​​​​​​​​​​​​​​​​​

 

1 Oracle DB on host 2:
OutsideDiscovery {​​​​​​​​​​​​​​​​​​​​​

    DatabaseDiscoveryMethod : databasesystem
    DatabaseOverride {​​​​​​​​​​​​​​​​​​​​​
        dbsystem : ORA/ABC/ABC002/oraxdb02 {​​​​​​​​​​​​​​​​​​​​​
            set {​​​​​​​​​​​​​​​​​​​​​
                no_addr_local_check {​​​​​​​​​​​​​​​​​​​​​
                    identicaldbhost : orax-db
                }​​​​​​​​​​​​​​​​​​​​​
            }​​​​​​​​​​​​​​​​​​​​​
        }​​​​​​​​​​​​​​​​​​​​​
   }​​​​​​​​​​​​​​​​​​​​​
}​​​​​​​​​​​​​​​​​​​​​

 

Remark: in case of multi DB installation, all relevant dbsystems must be maintained in this file!

Monitoring of Oracle Data Guardnot supported