Oracle Database

Observe, analyze and optimize the usage, health and performance of your database

Extension

Free trial Documentation

Product information
Release notes

Overview

Dynatrace automatically detects all applications and microservices deployed in your system and how your system uses Oracle Database.

Dynatrace diagnoses anomalies in real time with AI and pinpoints the root cause in slow-performing or erroneous SQL statements. Deep code-level insights combined with cloud-native database server monitoring help you ensure a robust production environment.

The Oracle Database extension complements the client-side database usage insights by providing server-side observability starting with availability and performance statistics, down to individual SQL statements and log insights.

Use cases

Understand all database dependencies of your applications, which database statements are executed, and their performance.
Improve the performance of your application by reducing or optimizing typical database patterns like the 1+N query problem
Understand the resource impact that your applications have on your database.
Understand the impact that resource shortages or other database issues have on your application by observing the database server itself.
Manage and analyze DB audit logs to spot invalid login attempts
Track the health and performance of Oracle Database servers (either standalone or multi-tenant)
Track the most time consuming queries performance
Speed up application-problem diagnosis when issues are caused by the database

Get started

This extension is a remote extension, which runs from an ActiveGate in your environment, connecting to each Oracle Database to be monitored. A series of queries on different views are run, and data is sent back to Dynatrace.

Get started for Oracle Database clients:

If the application that connects to the Oracle Database server runs on a virtual machine or bare-metal, install OneAgent on it to get started.

If the application that connects to the Oracle Database server runs as a workload in Kubernetes or OpenShift, set up Dynatrace on Kubernetes or OpenShift.

Activate the following OneAgent features to get full tracing insight:

Node.js Oracle DB
PHP Oracle

Get started with Oracle Database servers:

If your Oracle Database server runs on a virtual machine or bare-metal, install OneAgent on it to get started with system performance metrics.

Activate the remote Oracle Database extension to get full insight into the Oracle Database server's health and performance combined with metrics and events. The extension collects data by directly querying the database's performance views and thus requires a connection to the database.

A dedicated user account is recommended for monitoring. For convenience, user creation scripts can be found here. These scripts will create a user with the CREATE_SESSION role and SELECT permissions on the following performance views:

CDB_DATA_FILES
CDB_TABLESPACE_USAGE_METRICS
CDB_TABLESPACES
CDB_TEMP_FILES
GV_$ARCHIVE_DEST
GV_$ARCHIVE_DEST_STATUS
V_$ASM_DISK_STAT
V_$ASM_DISKGROUP_STAT
V_$BACKUP_SET_DETAILS
GV_$CLUSTER_INTERCONNECTS
GV_$CONTAINERS
V_$CONTAINERS
GV_$CON_SYS_TIME_MODEL
GV_$CON_SYSSTAT
GV_$DATABASE
V_$DATABASE
V_$DATABASE_BLOCK_CORRUPTION
GV_$DATAFILE
V_$DATAFILE
GV_$DATAGUARD_STATUS
GV_$INSTANCE
GV_$INSTANCE_PING
GV_$LIBRARYCACHE
V_$LOG
GV_$METRIC
GV_$METRICGROUP
GV_$PARAMETER
GV_$PDBS
GV_$PGASTAT
V_$RECOVER_FILE
V_$RECOVERY_FILE_DEST
GV_$RESOURCE_LIMIT
V_$RMAN_BACKUP_JOB_DETAILS
GV_$SESSION
V_$SESSION
GV_$SGASTAT
GV_$SQL
V_$SQL
GV_$SQLAREA
V_$SQL_PLAN
GV_$SQL_PLAN
V_$SQL_PLAN_STATISTICS_ALL
GV_$SYSSTAT
GV_$SYSTEM_EVENT
GV_$SYSTEM_WAIT_CLASS
V_$TABLESPACE
V_$TEMPFILE

Alternatively, the SELECT_CATALOG_ROLE can be assigned to the monitoring user.

To monitor a multitenant Oracle DB setup, ensure the extension points to the CDB. PDB discovery and monitoring will occur automatically. In this case, explicit permissions to access data across all containers are needed:

alter user <your_username> set container_data=all container = current;

These privileges are already included in the user creation scripts.

Users of the Databases App who want to make use of Query Execution Plans, will also need to provide permission for the V$SQL_PLAN, V$SESSION, V$SQL_PLAN_STATISTICS_ALL and V$SQL views. These permissions are included in the user creation scripts. See the execution plan monitoring section below for more details.

Finally, activate log monitoring to get full log insight.

Note:
With the TopN feature set, the extension reports the most time consuming queries on the Oracle Instance entity page, in a card called "Logs". Enabling this feature may expose sensitive data in the reported queries.

Details

This extension package contains:

Topology and relationship definitions for RAC Clusters, Backup Jobs, Databases, Instances, ASM Disks, and ASM Disk Groups.
A Classic and New Dashboard offering a monitoring overview for Oracle Database environment.
Alerts for failed backups, unavailable PDBs, unavailable instances, high tablespace usage, and more.
A Unified Analysis page for the above-mentioned topology

Compatibility information

The following Oracle versions are supported:

Oracle DB 12.2+

The following architectures are supported:

Oracle standalone servers
Oracle Multitenant (CDB/PDB)
- Configure monitoring for CDB to detect all PDBs
Oracle AWS RDS
Oracle RAC
- Configure monitoring for the SCAN listener to detect all instances and databases.

Log Management and Analytics

Audit log files tracking

Check log file's location

SELECT name, value FROM v$parameter WHERE name = 'audit_trail';

OS means that the audit logs are stored locally in the file.

SELECT value FROM v$parameter WHERE name = 'audit_file_dest';

specifies the log file's location

Add LogAgent security rules

Configure LogAgent's security rules to allow access to local files, by adding the oracle.json file under :

on Linux/UNIX: /var/lib/dynatrace/oneagent/agent/config/logmodule
on Windows: %PROGRAMDATA%\dynatrace\oneagent\agent\config\logmodule

{
    "@version": "1.0.0",
    "allowed-log-paths-configuration": [
        {
            "directory-pattern": "/u01/app/oracle/admin/oracle_standalone/adump/",
            "file-pattern": "*.aud",
            "action": "INCLUDE"
        }
    ]
}

Agent restart is not required, this config will be applied within 1 minute.

Configure custom log source and log ingest rules

Custom log source

Use the log file location fetched via the query executed in the first step, e.g. /u01/app/oracle/admin/oracle_standalone/adump/*.

Log ingest rules

An example configuration that includes only ORA-01017 that reports invalid username or password logon attempts could be configured using: Log content is any of: (.*)RETURNCODE:\[(\d+)\] "1017 AND Log source is any of: /u01/app/oracle/admin/oracle_standalone/adump/*

Accessing logs

Logs collected the way described above can be accessed using following DQL query: fetch logs | filter matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*").

Metrics extraction

Log processing rule

Configure log processing rule to extract log attributes out of the log content:

Rule name: preferred name
Matcher: matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*")
Processor definition:

PARSE(content, "
  DATA ' RETURNCODE:['INT']' SPACE '\"' INT:ora.returncode LD") |
PARSE(content, "
  DATA ' USERID:['INT']'SPACE CSVDQS:ora.userid LD") | 
PARSE(content, "
  DATA ' USERHOST:['INT']'SPACE CSVDQS:ora.userhost LD")

Metric extraction

Extract metrics from log entries to enable alerting:

Metric key: e.g.log.oracle.invalid_credentials
Matcher: matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*")
Metric measurement: Occurence of logs records
Dimensions: specify the log attributes to be used as metric dimensions

Execution Plan Monitoring

For SaaS customers with access to the Databases app, the execution plan monitoring functionality is also available when analyzing statement performance.

For this feature to work, the DBMS_XPLAN package needs to be available, and the user configured in the Dynatrace extension needs to have permissions to call the DISPLAY_CURSOR function. As per the official documentation this means that SELECT or READ permissions are required on the following views:

V$SQL_PLAN
V$SESSION
V$SQL_PLAN_STATISTICS_ALL
V$SQL

In addition to this, the SELECT permission is also required for V$SQL_PLAN.

Sensitive data masking

Query performance tracking may expose sensitive data in reported statements. Consequently, Dynatrace provides an optional mechanism that allows masking selected attributes. Details are available in the official documentation.

The configurations below present and example of how the sensitive data can be masked within the statements tracked.

create new processing rule under Settings -> Log Monitoring -> Processing
- Processor definition: USING(INOUT content) | FIELDS_ADD(content: REPLACE_PATTERN(content, "(\"'\"):p1 (LD):p2 (\"'\"):p3", "${p1}${p2|sha1}${p3}"))
or create/modify your custom extension to distribute such rules in your environment:

logProcessingRules:
  - ruleName: TopN statements masking
    query: event.group="query_performance"
    enabled: true
    ProcessorDefinition:
      rule: |
        USING(INOUT content) | FIELDS_ADD(content: REPLACE_PATTERN(content, "(\"'\"):p1 (LD):p2 (\"'\"):p3", "${p1}${p2|sha1}${p3}"))
    RuleTesting:
      sampleLog: |
        {
          "event.group": "query_performance",
          "content": "/*dt:ownQuery*/SELECT DECODE(name, 'sessions', value) AS sessions_limit, DECODE(name, 'processes', value) AS processes_limit FROM v$parameter WHERE name IN('sessions', 'processes')"
        }

Please adjust this rule to match your use case.

Licensing

The metrics collected through this extension consume Dynatrace Davis Data Units (see DDUs for metrics).

A rough estimation of the amount of DDUs consumed by metric ingest can be obtained through the following formula:

(55 * number of instances * 525.6) + (7 * number of databases * 525.6) + (8 * number of backup jobs per year * 0.005) + (5 * number of ASM disks * 525.6) + (3 * number of ASM disk groups * 525.6)

For logs, regular DDU consumption for log monitoring applies. Depending on your licensing model, refer either to DDU consumption for Log Management and Analytics or DDUs for Log Monitoring Classic.

FAQ

How does this Dynatrace extension collect data from my databases?

This extension will run from your Dynatrace ActiveGates and connect to the configured databases. Once the connection has been established, the extension will regularly run queries on the database to gather performance and health metrics, reporting the results back to Dynatrace.

Only SELECT queries are executed to collect data, and the vast majority of these will be selecting GV$ or V$ views. To see exactly which queries are executed, please download the extension yaml artifact by going to Release notes, opening a release and pressing the Download version button.

How often are these monitoring queries executed?

From version 3.2.0 onwards, query execution frequency is controlled by the configuration variables query-interval and heavy-query-interval. Most of the queries executed by the extension will run every query-interval minutes (with a default of 1 minute), while the queries under

asm (detailed)
tablespaces
tablespaces (detailed)
Blocked sessions
TopN

will run every heavy-query-interval minutes (with a default of 5 minutes).

For older versions, most queries run every minute, with exceptions for the heavy queries mentioned above, which run every 5 minutes.

How do I adjust query timeout?

By default, the extension's monitoring queries will timeout after 10 seconds. For a couple of selected queries, the long-running-query-timeout variable allows you to specify, in seconds, the timeout for the queries in the following feature sets:

asm (detailed)
tablespaces
tablespaces (detailed)
TopN

What is the difference between `Feature set` and `Feature set (detailed)`

The following feature sets have both a regular version and a detailed versions. These can be enabled or disabled in accordance to your specific use-case:

asm and asm (detailed)
- Due to the high license consumption associated with monitoring thousands of ASM disks, the asm feature set captures only ASM disk group data, while the asm (detailed) feature set captures data for all disks. Both feature sets can be enabled at the same time.
waitEvents and waitEvents (detailed)
- To control license consumption, the waitEvents feature set will collect wait time metrics aggregated by wait class, while the waitEvents (detailed) feature set collects metrics for the top 20 wait events.
tablespaces and tablespaces (detailed)
- Due to high the CPU consumption caused by joining tablespace metrics with datafile data, the tablespaces feature set does not collect the com.dynatrace.extension.sql-oracle.tablespaces.allocatedSpace metric coming from CDB_DATA_FILES (which tablespaces (detailed) does). Furthermore, the tablespaces feature set only collects data for tablespaces with more than 50% used space (as reported by CDB_TABLESPACE_USAGE_METRICS), while the tablespaces (detailed) feature set collects metrics for all tablespaces. Only one of these feature sets should be enabled at any given time.

Why am I missing Dataguard metrics?

For some of the Dataguard metrics, not seeing any data is the correct behavior and it means the Data guard deployment is working as expected. The following metrics will only show datapoints in case there are issues which need further investigation:

NOLOGGING activity will record a metric datapoint whenever there are operations executed against the database which will not generate redo log records. This requires investigation because from a Data guard perspective the mechanism is completely bypassed when such activity occurs, leaving the standby vulnerable until these files are manually refreshed.
Dataguard severe events will record a metric datapoint whenever Data guard reports a fatal or severe event. In such a situation, the metric dimensions will carry the event message/description which should be further investigated on the Database instance.
Archive destination status will record a metric datapoint whenever the Database's archive destinations are reporting an Invalid or Error status. The metric dimensions will show a description of the status as well as point to the archive destination which reported the error.

Why am I missing CPU usage metrics?

The com.dynatrace.extension.sql-oracle.cpu.backgroundTotal and com.dynatrace.extension.sql-oracle.cpu.foregroundTotal metrics are collected from the GV$METRIC view filtering by metric group name System Metrics Long Duration (Group ID 2). Since metrics for this group are only populated at the CDB level, these two metrics will only be collected when the extension is configured to connect to the CDB and not the PDB.

If you are missing these two metrics, please double-check your connection configuration and ensure that the extension configuration is pointing to the CDB.

Why do I see duplicate entities?

When monitoring RAC setups, node discovery is done automatically based on the data collected from the GV$ views. The monitoring configuration should be configured only for the listener in front of the cluster, and not for each individual cluster node. If you are seeing duplicate clusters or nodes, please ensure that you have configured the extension to connect to the cluster listener, and not to each individual node.

Also, confirm that the extension is configured to connect to the CDB, and not the individual PDBs.

Why am I not seeing my databases?

When there is no data at all for a whole database, the most likely scenario is that there was some problem in the connection between the ActiveGate and the database server to be monitored.

First, ensure that the connection details (hostname/IP, port, service name/SID) were correctly configured and that the user account provided to the extension has the permissions to establish a session.
Next, confirm that a connection can be established from the ActiveGate server to the Database server, and that there are no firewalls blocking the connection. Use the Dynatrace DB connection check tool, to ensure the JDBC can establish a connection.

If you are missing data only for a specific metric, or set of metrics, it may be a problem related to the permissions granted to the user account. Please ensure that all the required permissions highlighted on the Hub tile are provided. The ActiveGate logs will also indicate if an error occurred during the execution of monitoring query.

In some cases, a missing metric might indicate the extension was not properly configured (CDB vs. PDB, for example). Given that some metrics work on the CDB level, not the PDB – it can cause confusion. Please double-check your connection configuration and ensure that the extension configuration is pointing to the CDB, as mentioned above.

Where do I look for diagnostic logs?

You can find detailed error messages in the ActiveGate logs. Most logs can be found under the ActiveGate logs directory on the server itself.

Alternatively, directions on how to collect diagnostics remotely which include relevant logs, is described in the documentation here.

Troubleshooting

To troubleshoot this extension, use the guide(s) in the Dynatrace Community

Provided by

Dynatrace

Resources

Documentation More Information

Support

By Dynatrace

Dynatrace support center

Subscribe to new releases

Copy to clipboard

Extension content

Content typeNumber of items included

screen layout

list screen layout

screen logs cards

screen message cards

document dashboard

metric metadata

screen actions

screen chart groups

screen entities lists

screen custom cards

generic type

screen metric tables

dashboards

screen properties

metric query

generic relationship

log metric

alerts

screen dql table

Feature sets

Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.

Feature setsNumber of metrics included

Metric name	Metric key	Description	Unit
Cluster topology	com.dynatrace.extension.sql-oracle.cluster_topology	A state metric whose dimensions represent all Oracle clusters and their linked instances and hosts	NotApplicable
Database topology	com.dynatrace.extension.sql-oracle.database_topology	A state metric whose dimensions represent all Oracle instances and their linked databases	NotApplicable
Instance status	com.dynatrace.extension.sql-oracle.status	A state metric representing the details of the connected Oracle instance.	State
Database status	com.dynatrace.extension.sql-oracle.db_status	A state metric representing details of the connected Oracle database.	State

Metric name	Metric key	Description	Unit
Total size	com.dynatrace.extension.sql-oracle.tablespaces.totalSpace	Total size of tablespace, including extensibility. This covers both allocated an unallocated space as large as the tablespace can expand.	Byte
Free space	com.dynatrace.extension.sql-oracle.tablespaces.freeSpace	Total free space available in the tablespace, in bytes. This includes space that is currently allocated and available for reuse and space that is currently unallocated.	Byte
Used space	com.dynatrace.extension.sql-oracle.tablespaces.usedSpace	Total space in use within the tablespace, in bytes.	Byte
Allocated space	com.dynatrace.extension.sql-oracle.tablespaces.allocatedSpace	Total space in use within the tablespace, in bytes.	Byte
Tablespace usage	com.dynatrace.extension.sql-oracle.tablespaces.usage	The percentage of tablespace in use, relative to the total size (including extensibility).	Percent

Metric name	Metric key	Description	Unit
Instance ping	com.dynatrace.extension.sql-oracle.rac.instance_ping	Represents the current inter-instance ping of 8K messages as provided in GV$INSTANCE_PING.	MicroSecond
-	com.dynatrace.extension.sql-oracle.rac.interconnects	-	-

Metric name	Metric key	Description	Unit
Connection management time	com.dynatrace.extension.sql-oracle.queries.connectionManagement.count	Time spent on performing session connect and disconnect calls	MicroSecond
PL SQL exec time	com.dynatrace.extension.sql-oracle.queries.plSqlExec.count	Time spent on running the PL/SQL interpreter	MicroSecond
SQL exec time	com.dynatrace.extension.sql-oracle.queries.sqlExec.count	Time spent on executing SQL	MicroSecond
SQL parse time	com.dynatrace.extension.sql-oracle.queries.sqlParse.count	Time spent on parsing SQL	MicroSecond
DB Time	com.dynatrace.extension.sql-oracle.queries.dbTime.count	Time spent on performing Database user-level calls	MicroSecond
DB CPU	com.dynatrace.extension.sql-oracle.queries.cpuTime.count	CPU time spent on performing database user-level calls	MicroSecond

Metric name	Metric key	Description	Unit
Free space	com.dynatrace.extension.sql-oracle.asm.disk.free_mb	Free disk space available on this Oracle ASM Disk	MegaByte
Total space	com.dynatrace.extension.sql-oracle.asm.disk.total_mb	Total disk space available on this Oracle ASM Disk	MegaByte
Used space	com.dynatrace.extension.sql-oracle.asm.disk.usage	Percentage of disk space used on this Oracle ASM Disk	Percent
Reads	com.dynatrace.extension.sql-oracle.asm.disk.reads.count	Number of reads from this Oracle ASM Disk	Count
Writes	com.dynatrace.extension.sql-oracle.asm.disk.writes.count	Number of writes to this Oracle ASM Disk	Count

Metric name	Metric key	Description	Unit
Free space	com.dynatrace.extension.sql-oracle.asm.disk_group.free_mb	Free disk space available on this Oracle ASM Disk Group	MegaByte
Total space	com.dynatrace.extension.sql-oracle.asm.disk_group.total_mb	Total disk space available on this Oracle ASM Disk Group	MegaByte
Used space	com.dynatrace.extension.sql-oracle.asm.disk_group.usage	Percentage of disk space used on this Oracle ASM Disk Group	Percent

Metric name	Metric key	Description	Unit
Total size	com.dynatrace.extension.sql-oracle.tablespaces.totalSpace	Total size of tablespace, including extensibility. This covers both allocated an unallocated space as large as the tablespace can expand.	Byte
Free space	com.dynatrace.extension.sql-oracle.tablespaces.freeSpace	Total free space available in the tablespace, in bytes. This includes space that is currently allocated and available for reuse and space that is currently unallocated.	Byte
Used space	com.dynatrace.extension.sql-oracle.tablespaces.usedSpace	Total space in use within the tablespace, in bytes.	Byte
Tablespace usage	com.dynatrace.extension.sql-oracle.tablespaces.usage	The percentage of tablespace in use, relative to the total size (including extensibility).	Percent

Metric name	Metric key	Description	Unit
PGA aggregate limit	com.dynatrace.extension.sql-oracle.memory.pga.size.pgaAggregateLimit	Limit on the aggregate PGA memory consumed by the instance	Byte
PGA aggregate target	com.dynatrace.extension.sql-oracle.memory.pga.size.pgaAggregateTarget	Target aggregate PGA memory available to all server processes attached to the instance	Byte
PGA memory used	com.dynatrace.extension.sql-oracle.memory.pga.used	PGA memory consumed by work areas	Byte
Allocated PGA	com.dynatrace.extension.sql-oracle.memory.pga.allocated	Current amount of PGA memory allocated by the instance	Byte
Shared pool free	com.dynatrace.extension.sql-oracle.memory.sga.cacheBuffer.sharedPoolFree	Amount of free system global area (SGA) memory available in shared pool	Percent
Redo log space wait time	com.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoLogSpaceWaitTime.count	Total elapsed time of waiting for redo log space request	MilliSecond
Redo size increase	com.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoSizeIncrease.count	Total amount of redo generated in bytes	Byte
Redo write time	com.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoWriteTime.count	Total elapsed time of the write from the redo log buffer to the current redo log file	MilliSecond
Logical reads	com.dynatrace.extension.sql-oracle.memory.sessionLogicalReads.count	The sum of "db block gets" plus "consistent gets"	Count
Physical reads	com.dynatrace.extension.sql-oracle.memory.physicalReads.count	Total number of data blocks read from disk	Count
Physical reads direct	com.dynatrace.extension.sql-oracle.memory.physicalReadsDirect.count	Number of reads directly from disk, bypassing the buffer cache	Count
Sorts in memory	com.dynatrace.extension.sql-oracle.memory.memorySorts.count	Number of sort operations that were performed completely in memory and did not require any disk writes	Count
Sorts on disk	com.dynatrace.extension.sql-oracle.memory.diskSorts.count	Number of sort operations that required at least one disk write	Count
Library cache hit ratio	com.dynatrace.extension.sql-oracle.memory.libraryCacheHitRatio	Library cache hit ratio	Percent

Metric name	Metric key	Description	Unit
CPU cores	com.dynatrace.extension.sql-oracle.cpu.cores	Number of CPU cores	Count
Background CPU usage (per second)	com.dynatrace.extension.sql-oracle.cpu.backgroundTotal	CPU usage of background processes in centi seconds per second	Unspecified
Foreground CPU usage (per second)	com.dynatrace.extension.sql-oracle.cpu.foregroundTotal	CPU usage of foreground processes in centi seconds per second	Unspecified

Metric name	Metric key	Description	Unit
Physical bytes read	com.dynatrace.extension.sql-oracle.io.bytesRead.count	Total size in bytes of disk reads by all database instance activity including application reads, backup, recovery, and other utilities	Byte
Physical bytes written	com.dynatrace.extension.sql-oracle.io.bytesWritten.count	Total size in bytes of all disk writes for the database instance including application activity, backup, recovery, and other utilities	Byte
Total wait time	com.dynatrace.extension.sql-oracle.io.wait.count	Total time spent in all wait states except for Idle class	MilliSecond

Metric name	Metric key	Description	Unit
Datafile status	com.dynatrace.extension.sql-oracle.datafile.status	State metric representing the status of Datafiles and Tempfiles across containers (database and any PDBs).	NotApplicable
Datafile number of corrupted blocks	com.dynatrace.extension.sql-oracle.datafile.corrupted_blocks	Metric representing the number of corrupted blocks reported by V$DATABASE_BLOCK_CORRUPTION for each Datafile	Count

Metric name	Metric key	Description	Unit
Number of wait events by wait class	com.dynatrace.extension.sql-oracle.wait.count	Total number of waits by wait class, excluding 'Idle' events	Count
Seconds waited by wait class	com.dynatrace.extension.sql-oracle.wait.time.count	Total amount of time waited by wait class, excluding 'Idle' events	MicroSecond

Metric name	Metric key	Description	Unit
FRA Usage	com.dynatrace.extension.sql-oracle.fra.usage	The percentage disk utilization in the fast recovery area.	Percent
FRA limit	com.dynatrace.extension.sql-oracle.fra.limit	Maximum amount of disk space (in bytes) that the database can use for the fast recovery area. This is the value specified in the DB_RECOVERY_FILE_DEST_SIZE initialization parameter.	Byte
FRA used	com.dynatrace.extension.sql-oracle.fra.used	Amount of disk space (in bytes) used by fast recovery area files created in current and all previous fast recovery areas. Changing fast recovery areas does not reset SPACE_USED to 0.	Byte
FRA reclaimable	com.dynatrace.extension.sql-oracle.fra.reclaimable	Total amount of disk space (in bytes) that can be created by deleting obsolete, redundant, and other low priority files from the fast recovery area	Byte

Metric name	Metric key	Description	Unit
Input bytes	com.dynatrace.extension.sql-oracle.backup-input_bytes	Sum of all input file sizes backed up.	Byte
Output bytes	com.dynatrace.extension.sql-oracle.backup-output_bytes	Output size of all pieces generated.	Byte
Elapsed seconds	com.dynatrace.extension.sql-oracle.backup-elapsed_seconds	Number of elapsed seconds.	Second
Compression ratio	com.dynatrace.extension.sql-oracle.backup-compression_ratio	Compression ratio.	Percent
Input bytes per second	com.dynatrace.extension.sql-oracle.backup-input_bytes_per_second	Input read-rate-per-second.	BytePerSecond
Output bytes per second	com.dynatrace.extension.sql-oracle.backup-output_bytes_per_second	Output write-rate-per-second.	BytePerSecond
Auto - backup count	com.dynatrace.extension.sql-oracle.backup-autobackup_count_number	Number of autobackups performed by this job.	Count
Backup state	com.dynatrace.extension.sql-oracle.backup.state	A state metric representing the details of a Backup Job.	State
Time since last backup	com.dynatrace.extension.sql-oracle.backup.time_since	The time elapsed since the last backup completed successfully.	Minute

Metric name	Metric key	Description	Unit
Number of wait events	com.dynatrace.extension.sql-oracle.wait.events.count	Total number of waits by wait event, excluding 'Idle' events. Only collects the top 20 most time consuming events.	Count
Seconds waited	com.dynatrace.extension.sql-oracle.wait.events.time.count	Total amount of time waited by wait event, excluding 'Idle' events. Only collects the top 20 most time consuming events.	MicroSecond

Metric name	Metric key	Description	Unit
Sessions utilization	com.dynatrace.extension.sql-oracle.limits.sessions_utilization	Utilization of sessions on the instance. This is a percentage of current utilization relative to the limit.	Percent
Processes utilization	com.dynatrace.extension.sql-oracle.limits.processes_utilization	Utilization of processes on the instance. This is a percentage of current utilization relative to the limit.	Percent

Metric name	Metric key	Description	Unit
Dataguard severe events	com.dynatrace.extension.sql-oracle.dataguard.severeEvents	Counts the number of fatal and severe Data guard events occurred in the last day. If this count is greater than 0, check its dimensions to take action for the specific events.	Count
NOLOGGING activity	com.dynatrace.extension.sql-oracle.dataguard.nologgingActivity	Counts the number of files which contain NOLOGGING activity in the last day. If the count is greater than 0 then the standby database is vulnerable; check the dimensions to find out which files must be refreshed on the standby.	Count
Archive destination status	com.dynatrace.extension.sql-oracle.dataguard.archiveDestErrStatus	Counts the number of invalid or errored statuses of archive destinations. If the count is greater than 0, use the dimensions to understand the status and destination it refers to.	Count
Seq. difference	com.dynatrace.extension.sql-oracle.dataguard.seqDifference	Tracks the difference in sequence number between the latest archived and applied redo log. Use this count along with the dimensions to identify gaps between the primary and archive destination.	Count

Metric name	Metric key	Description	Unit
Total size	com.dynatrace.extension.sql-oracle.pdb-total_size	Shows the disk space (in bytes) used by the PDB, including both data and temp files.	Byte
Block size	com.dynatrace.extension.sql-oracle.pdb-block_size	The current block size for the PDB	Byte
Diagnostic size	com.dynatrace.extension.sql-oracle.pdb-diagnostic_size	Shows the current disk space usage (in bytes) of the diagnostic traces generated in the PDB.	Byte
Audit files size	com.dynatrace.extension.sql-oracle.pdb-audit_files_size	Shows the current disk space usage (in bytes) by Unified Audit files (.bin format) in the current PDB.	Byte
Max size	com.dynatrace.extension.sql-oracle.pdb-max_size	Shows the maximum amount of disk space (in bytes) that can be used by data and temp files in the PDB. If the value is 0 then there is no limit.	Byte
Max diagnostic size	com.dynatrace.extension.sql-oracle.pdb-max_diagnostic_size	Shows the maximum amount of disk space (in bytes) that can be used by diagnostic traces generated in the PDB. If the value is 0 then there is no limit.	Byte
Max audit size	com.dynatrace.extension.sql-oracle.pdb-max_audit_size	Shows the maximum amount of disk space (in bytes) that can be used by Unified Audit files (.bin format) in the PDB. If the value is 0 then there is no limit.	Byte

Metric name	Metric key	Description	Unit
Active Sessions	com.dynatrace.extension.sql-oracle.sessions.active	Active sessions count	Count
Blocked Sessions	com.dynatrace.extension.sql-oracle.sessions.blocked	Blocked sessions count	Count
Total sessions	com.dynatrace.extension.sql-oracle.sessions.all	Total sessions count	Count
User calls	com.dynatrace.extension.sql-oracle.sessions.userCalls.count	Total number of logins, parses, or execute calls	Count
Deadlocks	com.dynatrace.extension.sql-oracle.sessions.deadlocks.count	Total number deadlocks	Count

Full version history

To have more information on how to install the downloaded package, please follow the instructions on this page.

ReleaseDate

Full version history

✨ New in this version:

Added an extra variable tablespace-filter which can be used to filter the tablespaces to be monitored.

🚀 Improved in this version:

Log data collected by the extension (top and blocking statements) now have the endpoint_metadata variable as an attribute.
Adjusted the way foreground and background CPU metrics are collected.

🪲 Fixed in this version:

Fixed Instance entities not showing correctly in the databases list view.

Full version history

🪲 Fixed in this version:

Fixed issue where backup metric is captured for too long in cases where the ActiveGate timezone does not match the database timezone.

Full version history

✨ New in this version:

Added out-of-the-box Platform dashboard for Oracle DB monitoring. This dashboard can be found under Ready-made dashboards in the Dashboards app.
Added SAME_AS relationship between sql:com_dynatrace_extension_sql-oracle_instance and Oracle Listener PGI.

🪲 Fixed in this version:

Fixed com.dynatrace.extension.sql-oracle.io.bytesRead.count and com.dynatrace.extension.sql-oracle.io.bytesWritten.count being switched.

Full version history

🪲 Fixed in this version:

Tablespace charts now show in the Databases app for RAC instances and as well as for non-RAC instances.

Full version history

✨ New in this version:

Added default alert template for Data Guard gap monitoring.

🚀 Improved in this version:

The failed backup alert template now uses a 5/3/5 alerting strategy to better fit with the collected data.

🪲 Fixed in this version:

The query under the asm (detailed) feature set runs with frequency heavy-query-interval. This fixes an issue where setting the heavy-query-timeout variable to more than 60s would cause this query to break.
- ⚠️ When updating an existing configuration to the new version, the ASM disk metrics will now be collected every 5 minutes by default. Alerts may need adjustment. This does not apply to ASM disk group metrics. ⚠️
To prevent hitting dimension tuple limits, the following dimensions were removed from the metric com.dynatrace.extension.sql-oracle.dataguard.seqDifference:
- primary.current.seq
- primary.archived.seq
- standby.applied.seq
Fixed issue where the ASM disk group name would sometimes not show on the Dynatrace ASM disk group entity.

Full version history

Fixed in this version:

Sorting SQL statements in the Databases app would retrieve duplicate results

Full version history

✨ New in this version:

Introduced two new monitoring configuration variables, query-interval and heavy-query-interval to control the extension's monitoring queries' execution frequency.
Added a new feature set Tablespaces (detailed) in order to better control the extension's resource consumption on the database. The current query for tablespaces monitoring has been moved to Tablespaces (detailed) and the the Tablespaces feature set now contains a simpler, less resource-intensive query to monitor tablespaces. This query drops the com.dynatrace.extension.sql-oracle.tablespaces.allocatedSpace metric and only monitors tablespaces with more than 50% used space.
- ⚠️ When updating an existing configuration to the new version, the new Tablespaces (detailed) feature set will be disabled by default. To continue collecting tablespace metrics as before enable this new feature set in existing configurations and disable the Tablespaces feature set. ⚠️
Added link to OneAgent monitored host to the Oracle DB Instance screen.

🪲 Fixed in this version:

Fixed bug where tablespace and datafile metrics were not properly associated with the sql-oracle_database entity.

ℹ️ This version requires ActiveGate version 1.301.0 or higher.

Full version history

🪲 Fixed in this version:

Fixed execution plan monitoring fetching sometimes not working for RAC setups.
Fixed ASM entities not being created for certain non-RAC setups.
Fixed OneAgent HOST to Oracle DB Instance entity SAME_AS relationship not being established properly.

ℹ️ This version requires ActiveGate version 1.293.0 or higher.

Full version history

✨ New in this version:

Added inter-instance ping metrics and charts for RAC setups
Added charts for cluster interconnects and cluster wait events to the cluster screen.

🚀 Improved in this version:

Adjusted the DataGuard severe events chart.

ℹ️ This version requires ActiveGate version 1.293.0 or higher.

Full version history

✨ New in this version:

New feature set asm (detailed) introduced in order to better control license consumption for ASM disks. ASM disk metrics are moved to this new feature set, while ASM disk group metrics remain in the asm feature set.
- ⚠️ When updating an existing configuration to the new version, the new asm (detailed) feature set will be disabled by default. To continue collecting ASM disk metrics enable this new feature set in existing configurations. ⚠️

🚀 Improved in this version:

Changed default dashboard to include ASM disk groups as well as ASM disks.

🪲 Fixed in this version:

Fixed Cluster instance name sometimes showing empty for RAC setups.
Fixed Dataguard metrics not being splittable by instance.
Fixed non-RAC Dataguard gaps metric chart always showing empty.

ℹ️ This version requires ActiveGate version 1.293.0 or higher.

Full version history

⚠️ Breaking changes:

New topology to accommodate for RAC setups:
- The host entity, sql:com_dynatrace_extension_sql-oracle_host, was dropped and its data is now shown on the Oracle Instance screen.
- The database-instance relationship was changed from runsOn to calls.
- OneAgent detected hosts, dt.entity.host, now have a sameAs relationship with instances.
Query performance metrics are now collected at the database/container level instead of at the instance level.
Top query log attributes are no longer collected as a rate, but rather as the value reported in SQLAREA. This will also change the value of the log.sql-oracle.top_n_queries. metrics.

✨ New in this version:

Oracle RAC setups are now supported. By configuring the extension to connect to a SCAN listener, Dynatrace will auto-detect the instances and databases without needing to individually configure endpoints for each instance.
- A cluster entity, sql:com_dynatrace_extension_sql-oracle_cluster, was added and will be active whenever a RAC setup is detected.
Query performance charts now show in the database screen as well as in the instance screen. In the case of RAC, metrics for all instances running that database will be shown.
On multitenant setups the CDB$ROOT is now detected as a container. Tablespaces and datafile charts for the CDB$ROOT are now show in the CDB$ROOT's database screen as opposed to in the instance screen.

ℹ️ This version requires ActiveGate version 1.293.0 or higher.

Full version history

⚠️ This release requires ActiveGate version 1.293.0 or higher. Please check your version before upgrading.

🪲 Fixed in this version:

Fixed certain backup monitoring metrics not working for Oracle Database 12c.
Fixed Dataguard no logging query always showing empty results.
Changed unit from Count to Byte for some PDB metrics.

Full version history

⚠️ This release requires ActiveGate version 1.293.0 or higher. Please check your version before upgrading.

✨ New in this version:

Execution plan analysis is now available for the long running queries, and can be accessed by navigating to Databases app > Instances > Statement performance. This feature is only available for Dynatrace SaaS customers.

Full version history

✨ New in this version:

Blocked sessions and deadlock monitoring
- Metrics for number of blocked sessions and deadlocks are part of the sessions feature set
- Blocked session details are ingested as logs as part of the Blocked sessions feature set. Records can be filtered by event.group == "blocked_sessions" in the log query.
Datafile monitoring now includes number of corrupt blocks and datafile recovery status.
Alerts have been added around Data Guard for severe events, nologging activity, and archive destination status
Longest running query metrics are part of the TopN feature set
- This helps visualize trends over time before using the Logs card to identify individual SQL statements
New configuration parameter - endpoint metadata
- This parameter will populate the endpoint_metadata attribute of the Oracle Instance entity and can be used in entity selectors (to facilitate tagging, for example).

🚀 Improved in this version:

Out-of-the-box alerts have been adjusted to use current metrics
FRA and Tablespaces metric charts display values using the KiB/MiB/GiB (binary) unit scale. This is in-line with DBA expectations and Oracle Enterprise Manager. The raw values remain collected in Bytes.
Data guard chart cards only appear if data guard is enabled on the instance. This can be checked in the instance attributes.

Full version history

🚀 Improved in this version:

Dropped the event dimension from com.dynatrace.extension.sql-oracle.wait.count and com.dynatrace.extension.sql-oracle.wait.time.count to prevent inadvertently high DDU consumption. To replace the previous functionality a new feature set, waitEvents (detailed), was added with metrics com.dynatrace.extension.sql-oracle.wait.events.count and com.dynatrace.extension.sql-oracle.wait.events.time.count which report total waits and total wait time for the top 20 wait events. When updating monitoring configs to the new version, make sure you enable the new feature set if you want to continue getting event level details.

Full version history

🪲 Fixed in this version:

ASM Disks tiles in the dashboard were using outdated metric names

Full version history

🪲 Fixed in this version:

ASM Disk Groups & ASM Disks queries would not run due to syntax

Full version history

✨ New in this version:

Fast Recovery Area (FRA) occupation tracking
Tablespaces are monitored per container (CDB & PDB)
ASM Disk Groups monitored as their own entity, related to ASM Disks
Status of data & temp files are tracked per container (CDB & PDB)
Data guard monitoring
- Severe events
- Gap between primary and standby applied sequences
- Nologging activity counts
- Archive destination error status

🚀 Improved in this version:

Tablespace utilization is calculated against maximum possible size including auto-extents
Tablespace utilization is reflected from CDB_TABLESPACE_USAGE_METRICS which takes into account the underlying filesystem (same as Oracle Enterprise Manager)
Sessions & Processes utilization reported as % of the configured limit

Full version history

✨ New in this version:

The extension data is now usable with the Database Overview App
Backup Jobs register additional details based on their backup sets
The time since the last backup of a given type is now recorded as a metric

🚀 Improved in this version:

Query timeout configuration parameter is more clearly described

🪲 Fixed in this version:

Tablespaces chart on the Instance page showed a long metric expression name
Not all backups were detected and listed on the Instance page

Full version history

⚠️ Breaking changes:

Due to the topology changes mentioned below, your environment may create new entities to replace the ones created by older versions of the extension.

Any custom configuration relying on the following entity types will not work:

sql:com_dynatrace_extension_sql-oracle_cdb
sql:com_dynatrace_extension_sql-oracle_pdb (replace with sql:com_dynatrace_extension_sql-oracle_database)
sql:com_dynatrace_extension_sql-oracle_service

✨ New in this version:

Additional attributes reported for Oracle Instances
When the extension is configured to connect to the Container (CDB), all Databases (PDBs) are automatically monitored
A new alert has been added for backup job failures

🚀 Improved in this version:

The topology has been simplified:
- Oracle Instance now represents either a standalone instance or container
- IDs of these entities are more accurately calculated
- Oracle Database now represents either a standalone or pluggable database
- The Oracle CDB, Oracle PDB, and Oracle Service entities have been removed
Database backups are visible on the Instance details page
All entity lists support filtering
The Oracle Server details page displays data about Oracle processes if the host has a OneAgent deployed
All metrics have the tag "Oracle" which can be used in the Metrics menu

🪲 Fixed in this version:

Backups would not be detected if the process crashed before the first sub-job could complete
Backups would be aggregated if performed during the same session