OracleDB

Configuration

Oracle Driver

Instana can not provide automatic Oracle monitoring for licensing reasons, because the driver jar may not be distributed by anybody except Oracle.

When the agent starts and discovers an OracleDB where the driver has not been supplied, the Instana agent will log this message:

Cannot monitor OracleDB without the driver ojdbc7-12.1.0.2.jar
For license reasons it cannot be provided by Instana
and needs to be manually obtained and added to the agent

To add the driver to the agent, add it to this location:

<agent_install_dir>/system/com/oracle/jdbc/ojdbc7/12.1.0.2/ojdbc7-12.1.0.2.jar

You can obtain the mentioned driver at http://www.oracle.com/technetwork/database/features/jdbc/default-2280470.html

Required DB Permissions

For the sensor to be able to connect to Oracle and monitor the metrics and configuration, the user needs to have read permissions for the following tables:

V$PARAMETER, V$SYSSTAT, V$VERSION, V$SYS_TIME_MODEL, V$SESSION, V$SYSTEM_WAIT_CLASS, V$INSTANCE, DBA_TABLESPACE_USAGE_METRICS, DBA_DATA_FILES

Sensor configuration

Please supply the credentials to the Instana agent in order to monitor OracleDB in it’s Configuration file:

Local

com.instana.plugin.oracledb:
  password: ''
  user: '' # default 'sys as sysdba'
  port: '' # default '1521'
  databaseSID: '' # default 'orcl'
  poll_rate: '' # default is 1 (seconds)

Remote

com.instana.plugin.oracledb:
  remote: # we support listing multiple DBs here!
    - host: ''
      port: '' # default '1521'
      user: '' # default is 'sys as sysdba'
      password: ''
      databaseSID: ''
      availabilityZone: '' # default is 'Remote Monitoring'
      poll_rate: '' # default is 1 (seconds)

The configured remote OracleDB instance will then be shown as a separate box in the specified availabilityZone.

Metrics collection

Configuration data

  • Version
  • SID
  • Started At
  • CPU Count
  • Max Sessions
  • DB Block Size

Performance metrics

  • DB Time per Second
  • Time Waited per Second
  • SQL Execution
  • SQL Parse
  • User Calls Commit Rollbacks
  • Buffer Cache
  • Sessions
  • Tablespace Usage

Health Signatures

For each sensor, there is a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.

Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any given entity.

For information about built-events for the OracleDB sensor, see the Built-in events reference.