Oracle

Agent Check

Overview

Get metrics from Oracle Database servers in real time to visualize and monitor availability and performance.

Setup

Installation

In order to use the Oracle integration, either install the Oracle Instant Client libraries, or download the Oracle JDBC Driver. Due to licensing restrictions we are unable to include these libraries in our agent, but you can download them directly from Oracle.

Steps for the JDBC Driver

• Download the jar file
• Add the path to the downloaded file in your $CLASSPATH, or add it to the check configuration file under jdbc_driver_path, as in the sample oracle.yaml.

Steps for the Instant Client

Go to the download page

You will need to install the Instant Client Basic and SDK packages.

After you have installed the Instant Client libraries, on linux you may have to ensure that the runtime linker can find the libraries. For example, using 'ldconfig:

    # Put the library location in an ld configuration file.

sudo sh -c "echo /usr/lib/oracle/12.2/client64/lib > \
    /etc/ld.so.conf.d/oracle-instantclient.conf"

    # Update the bindings.

sudo ldconfig

Alternately, update your LD_LIBRARY_PATH to include the location of the Instant Client libraries. For example:

mkdir -p /opt/oracle/ && cd /opt/oracle/

    # Download Oracle Instant Client (example dir: /opt/oracle).

unzip /opt/oracle/instantclient-basic-linux.x64-12.1.0.2.0.zip
unzip /opt/oracle/instantclient-sdk-linux.x64-12.1.0.2.0.zip

export LD_LIBRARY_PATH=/opt/oracle/instantclient/lib:$LD_LIBRARY_PATH

Note: Agent 6 uses upstart or systemd to orchestrate the datadog-agent service. Environment variables may need to be added to the service configuration files at the default locations of /etc/init/datadog-agent.service (Upstart) or /lib/systemd/system/datadog-agent.service (systemd). See documentation on Upstart or systemd for more information on how to configured these settings.

After installing either the JDBC Driver or the Instant Client

Finally, create a read-only datadog user with proper access to your Oracle Database Server. Connect to your Oracle database with an administrative user (e.g. SYSDBA or SYSOPER) and run:

-- Enable Oracle Script.
ALTER SESSION SET "_ORACLE_SCRIPT"=true;

-- Create the datadog user. Replace the password placeholder with a secure password.
CREATE USER datadog IDENTIFIED BY <password>;

-- Grant access to the datadog user.
GRANT CONNECT TO datadog;
GRANT SELECT ON GV_$PROCESS TO datadog;
GRANT SELECT ON gv_$sysmetric TO datadog;
GRANT SELECT ON sys.dba_data_files TO datadog;

Note: If you’re using Oracle 11g, there’s no need to run the following line:

ALTER SESSION SET "_ORACLE_SCRIPT"=true;

Configuration

Edit the oracle.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to point to your server and port, set the masters to monitor. See the sample oracle.d/conf.yaml for all available configuration options.

Configuration Options:

• server (Required) - The IP address or hostname of the Oracle Database server.
• service_name (Required) - The Oracle Database service name. To view the services available on your server, run the following query: SELECT value FROM v$parameter WHERE name='service_names'.
• user (Required) - If you followed the instructions above, set this to the read-only user datadog. Otherwise set it to a user with sufficient privileges to connect to the database and read system metrics.
• password (Required) - The password for the user account.
• tags (Optional) - A list of tags applied to all metrics collected. Tags may be simple strings or key-value pairs.

Validation

Run the Agent’s status subcommand and look for oracle under the Checks section.

Data Collected

Metrics

Events

The Oracle Database check does not include any events at this time.

Service Checks

The Oracle Database integration includes the service check oracle.can_connect which will verify the database is available and accepting connections.

Troubleshooting

Need help? Contact Datadog Support.

Mistake in the docs? Feel free to contribute!