Setting Up Database Monitoring for Oracle RAC

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Database Monitoring provides deep visibility into your Oracle databases by exposing query samples to profile your different workloads and diagnose issues.

The Agent collects telemetry directly from the database by logging in as a read-only user.

Before you begin

Supported Oracle versions
11g, 12c, 18c, 19c, 21c
Supported Agent version
Performance impact
The default Agent configuration for Database Monitoring is conservative, but you can adjust settings such as the collection interval and query sampling rate to better suit your needs. For most workloads, the Agent represents less than one percent of query execution time on the database and less than one percent of CPU.

Database Monitoring runs as an integration on top of the base Agent (see benchmarks).
Proxies, load balancers, and connection poolers
The Agent must connect directly to the host being monitored. The Agent should not connect to the database through a proxy, load balancer, or connection pooler. Each Agent must have knowledge of the underlying hostname and should stick to a single host for its lifetime, even in cases of failover. If the Datadog Agent connects to different hosts while it is running, the values of metrics will be incorrect.
Data security considerations
See Sensitive information for information about what data the Agent collects from your databases and how to ensure it is secure.


Complete the following to enable Database Monitoring with your Oracle database:

  1. Create the Datadog user
  2. Install the Agent
  3. Configure the Agent
  4. Install or verify the Oracle integration
  5. Validate the setup

Create the Datadog user

If you already have the legacy Oracle integration installed, the user already exists, and you can skip this step.

Create a read-only login to connect to your server and grant the required permissions:


Install the Agent

See the DBM Setup Architecture documentation to determine where to install the Agent. The Agent doesn’t require any external Oracle clients.

For installation steps, see the Agent installation instructions.

Configure the Agent

Configure the Agent for each RAC node by following the instructions for self-hosted Oracle databases.

You must configure the Agent for each Real Application Cluster (RAC) node, because the Agent collects information from every node separately by querying V$ views. The Agent doesn’t query any GV$ views to avoid generating interconnect traffic. The collected data from each RAC node is aggregated in the frontend.

  - server: '<RAC_NODE_1>:<PORT>'
    service_name: "<CDB_SERVICE_NAME>" # The Oracle CDB service name
    username: 'c##datadog'
    password: '<PASSWORD>'
    dbm: true
    tags:  # Optional
      - rac_cluster:<CLUSTER_NAME>
      - 'service:<CUSTOM_SERVICE>'
      - 'env:<CUSTOM_ENV>'
  - server: '<RAC_NODE_2>:<PORT>'
    service_name: "<CDB_SERVICE_NAME>" # The Oracle CDB service name
    username: 'c##datadog'
    password: '<PASSWORD>'
    dbm: true
    tags:  # Optional
      - rac_cluster:<CLUSTER_NAME>
      - 'service:<CUSTOM_SERVICE>'
      - 'env:<CUSTOM_ENV>'

The Agent connects only to CDB. It queries the information about PDBs while connected to CDB. Don’t create connections to individual PDBs.

Set the rac_cluster configuration parameter to the name of your RAC cluster or some user friendly alias. The rac_cluster filter helps you select all RAC nodes in the DBM Oracle Database Overview dashboard. You can set an additional filter for the database of interest.

Install or verify the Oracle integration

First-time installations

On the Integrations page in Datadog, install the Oracle integration for your organization. This installs an Oracle dashboard in your account that can be used to monitor the performance of your Oracle databases.

Existing installations

For an existing installation, verify that your configuration is located in the conf.d/oracle-dbm.d/ directory. You may need to migrate the legacy configuration from the conf.d/oracle.d/ directory.

Use the following command to migrate the Oracle integration from the legacy integration to the new one:

cp /etc/datadog-agent/conf.d/oracle.d/conf.yaml /etc/datadog-agent/conf.d/oracle-dbm.d/conf.yaml

Deactivate the legacy integration:

mv /etc/datadog-agent/conf.d/oracle.d/conf.yaml /etc/datadog-agent/conf.d/oracle.d/conf.yaml.bak

Deactivating the legacy integration prevents sending the system metrics twice.

Since the Agent doesn’t require an external Oracle client, remove the jdbc_driver_path configuration parameter from the new parameter file /etc/datadog-agent/conf.d/oracle-dbm.d/conf.yaml.

Validate the setup

Run the Agent’s status subcommand and look for oracle under the Checks section. Navigate to the Dashboard and Databases page in Datadog to get started.

Custom queries

Database Monitoring supports custom queries for Oracle databases. See the conf.yaml.example to learn more about the configuration options available.

Running custom queries may result in additional costs or fees assessed by Oracle.

Further reading

Documentation, liens et articles supplémentaires utiles: