Skip to technology filters Skip to main content
Dynatrace Hub

Extend the platform,
empower your team.

Popular searches:
Home hero bg
Oracle DatabaseOracle Database
Oracle Database

Oracle Database

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

Extension
Free trialDocumentation
The Dynatrace OneAgent offers the highest fidelity data when it comes to application observability. Get started on the client side by instrumenting your applications and building an understanding of your database performance from their perspective.For each instrumented application that calls your database, understand the performance and execution dynamics of every executed statement.For the database server, the OneAgent provides key insights into infrastructure utilization, while the Oracle Database Extension complements this data with health and performance signals queried directly from Oracle.For each of your monitored Oracle Instances, the extension provides insights into SQL query execution hotspots by tracking the longest running queries.Backup jobs are tracked across all monitored Oracle Instances. This gives you a complete history of backups as well as automated alerting in case of any backup failures.The Overview Dashboard is provided by the extension as an entry point to Oracle entities monitored across all configurations of the extension. This is a useful starting point for any further troubleshooting and analysis.Sensitive data masking sample configuration
  • 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

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
  • 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.

While the extension supports connecting directly to a Pluggable Database (PDB), our recommended approach to monitor a multitenant Oracle DB setup is to point to extension the CDB. PDB discovery and monitoring will occur automatically. In this case, explicit permissions to access data across all containers may be 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.

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.

Please note that the execution plan monitoring feature may sometimes not work as expected for RAC deployments. This will be fixed as soon as possible.

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

Why am I missing Data guard 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.
Dynatrace
DocumentationMore Information
By Dynatrace
Dynatrace support center
Subscribe to new releases
Copy to clipboard

Extension content

Content typeNumber of items included
screen layout
7
screen logs cards
4
list screen layout
7
screen message cards
2
metric metadata
98
screen actions
16
screen chart groups
28
screen entities lists
15
generic type
6
screen metric tables
8
screen custom cards
2
screen properties
6
dashboards
1
metric query
5
log metric
12
alerts
8
generic relationship
10
screen dql table
2

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 nameMetric keyDescriptionUnit
Cluster topologycom.dynatrace.extension.sql-oracle.cluster_topologyA state metric whose dimensions represent all Oracle clusters and their linked instances and hostsNotApplicable
Database topologycom.dynatrace.extension.sql-oracle.database_topologyA state metric whose dimensions represent all Oracle instances and their linked databasesNotApplicable
Instance statuscom.dynatrace.extension.sql-oracle.statusA state metric representing the details of the connected Oracle instance.State
Database statuscom.dynatrace.extension.sql-oracle.db_statusA state metric representing details of the connected Oracle database.State
Metric nameMetric keyDescriptionUnit
Datafile statuscom.dynatrace.extension.sql-oracle.datafile.statusState metric representing the status of Datafiles and Tempfiles across containers (database and any PDBs).NotApplicable
Datafile number of corrupted blockscom.dynatrace.extension.sql-oracle.datafile.corrupted_blocksMetric representing the number of corrupted blocks reported by V$DATABASE_BLOCK_CORRUPTION for each DatafileCount
Metric nameMetric keyDescriptionUnit
PGA aggregate limitcom.dynatrace.extension.sql-oracle.memory.pga.size.pgaAggregateLimitLimit on the aggregate PGA memory consumed by the instanceByte
PGA aggregate targetcom.dynatrace.extension.sql-oracle.memory.pga.size.pgaAggregateTargetTarget aggregate PGA memory available to all server processes attached to the instanceByte
PGA memory usedcom.dynatrace.extension.sql-oracle.memory.pga.usedPGA memory consumed by work areasByte
Allocated PGAcom.dynatrace.extension.sql-oracle.memory.pga.allocatedCurrent amount of PGA memory allocated by the instanceByte
Shared pool freecom.dynatrace.extension.sql-oracle.memory.sga.cacheBuffer.sharedPoolFreeAmount of free system global area (SGA) memory available in shared poolPercent
Redo log space wait timecom.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoLogSpaceWaitTime.countTotal elapsed time of waiting for redo log space requestMilliSecond
Redo size increasecom.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoSizeIncrease.countTotal amount of redo generated in bytesByte
Redo write timecom.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoWriteTime.countTotal elapsed time of the write from the redo log buffer to the current redo log fileMilliSecond
Logical readscom.dynatrace.extension.sql-oracle.memory.sessionLogicalReads.countThe sum of "db block gets" plus "consistent gets"Count
Physical readscom.dynatrace.extension.sql-oracle.memory.physicalReads.countTotal number of data blocks read from diskCount
Physical reads directcom.dynatrace.extension.sql-oracle.memory.physicalReadsDirect.countNumber of reads directly from disk, bypassing the buffer cacheCount
Sorts in memorycom.dynatrace.extension.sql-oracle.memory.memorySorts.countNumber of sort operations that were performed completely in memory and did not require any disk writesCount
Sorts on diskcom.dynatrace.extension.sql-oracle.memory.diskSorts.countNumber of sort operations that required at least one disk writeCount
Library cache hit ratiocom.dynatrace.extension.sql-oracle.memory.libraryCacheHitRatioLibrary cache hit ratioPercent
Metric nameMetric keyDescriptionUnit
Sessions utilizationcom.dynatrace.extension.sql-oracle.limits.sessions_utilizationUtilization of sessions on the instance. This is a percentage of current utilization relative to the limit.Percent
Processes utilizationcom.dynatrace.extension.sql-oracle.limits.processes_utilizationUtilization of processes on the instance. This is a percentage of current utilization relative to the limit.Percent
Metric nameMetric keyDescriptionUnit
Total sizecom.dynatrace.extension.sql-oracle.pdb-total_sizeShows the disk space (in bytes) used by the PDB, including both data and temp files.Byte
Block sizecom.dynatrace.extension.sql-oracle.pdb-block_sizeThe current block size for the PDBByte
Diagnostic sizecom.dynatrace.extension.sql-oracle.pdb-diagnostic_sizeShows the current disk space usage (in bytes) of the diagnostic traces generated in the PDB.Byte
Audit files sizecom.dynatrace.extension.sql-oracle.pdb-audit_files_sizeShows the current disk space usage (in bytes) by Unified Audit files (.bin format) in the current PDB.Byte
Max sizecom.dynatrace.extension.sql-oracle.pdb-max_sizeShows 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 sizecom.dynatrace.extension.sql-oracle.pdb-max_diagnostic_sizeShows 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 sizecom.dynatrace.extension.sql-oracle.pdb-max_audit_sizeShows 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 nameMetric keyDescriptionUnit
Input bytescom.dynatrace.extension.sql-oracle.backup-input_bytesSum of all input file sizes backed up.Byte
Output bytescom.dynatrace.extension.sql-oracle.backup-output_bytesOutput size of all pieces generated.Byte
Elapsed secondscom.dynatrace.extension.sql-oracle.backup-elapsed_secondsNumber of elapsed seconds.Second
Compression ratiocom.dynatrace.extension.sql-oracle.backup-compression_ratioCompression ratio.Percent
Input bytes per secondcom.dynatrace.extension.sql-oracle.backup-input_bytes_per_secondInput read-rate-per-second.BytePerSecond
Output bytes per secondcom.dynatrace.extension.sql-oracle.backup-output_bytes_per_secondOutput write-rate-per-second.BytePerSecond
Auto - backup countcom.dynatrace.extension.sql-oracle.backup-autobackup_count_numberNumber of autobackups performed by this job.Count
Backup statecom.dynatrace.extension.sql-oracle.backup.stateA state metric representing the details of a Backup Job.State
Time since last backupcom.dynatrace.extension.sql-oracle.backup.time_sinceThe time elapsed since the last backup completed successfully.Minute
Metric nameMetric keyDescriptionUnit
Total sizecom.dynatrace.extension.sql-oracle.tablespaces.totalSpaceTotal size of tablespace, including extensibility. This covers both allocated an unallocated space as large as the tablespace can expand.Byte
Free spacecom.dynatrace.extension.sql-oracle.tablespaces.freeSpaceTotal 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 spacecom.dynatrace.extension.sql-oracle.tablespaces.usedSpaceTotal space in use within the tablespace, in bytes.Byte
Allocated spacecom.dynatrace.extension.sql-oracle.tablespaces.allocatedSpaceTotal space in use within the tablespace, in bytes.Byte
Tablespace usagecom.dynatrace.extension.sql-oracle.tablespaces.usageThe percentage of tablespace in use, relative to the total size (including extensibility).Percent
Metric nameMetric keyDescriptionUnit
CPU corescom.dynatrace.extension.sql-oracle.cpu.coresNumber of CPU coresCount
Background CPU usage (per second)com.dynatrace.extension.sql-oracle.cpu.backgroundTotalCPU usage of background processes in centi seconds per secondUnspecified
Foreground CPU usage (per second)com.dynatrace.extension.sql-oracle.cpu.foregroundTotalCPU usage of foreground processes in centi seconds per secondUnspecified
Metric nameMetric keyDescriptionUnit
FRA Usagecom.dynatrace.extension.sql-oracle.fra.usageThe percentage disk utilization in the fast recovery area.Percent
FRA limitcom.dynatrace.extension.sql-oracle.fra.limitMaximum 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 usedcom.dynatrace.extension.sql-oracle.fra.usedAmount 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 reclaimablecom.dynatrace.extension.sql-oracle.fra.reclaimableTotal amount of disk space (in bytes) that can be created by deleting obsolete, redundant, and other low priority files from the fast recovery areaByte
Metric nameMetric keyDescriptionUnit
Free spacecom.dynatrace.extension.sql-oracle.asm.disk.free_mbFree disk space available on this Oracle ASM DiskMegaByte
Total spacecom.dynatrace.extension.sql-oracle.asm.disk.total_mbTotal disk space available on this Oracle ASM DiskMegaByte
Used spacecom.dynatrace.extension.sql-oracle.asm.disk.usagePercentage of disk space used on this Oracle ASM DiskPercent
Readscom.dynatrace.extension.sql-oracle.asm.disk.reads.countNumber of reads from this Oracle ASM DiskCount
Writescom.dynatrace.extension.sql-oracle.asm.disk.writes.countNumber of writes to this Oracle ASM DiskCount
Metric nameMetric keyDescriptionUnit
Active Sessionscom.dynatrace.extension.sql-oracle.sessions.activeActive sessions countCount
Blocked Sessionscom.dynatrace.extension.sql-oracle.sessions.blockedBlocked sessions countCount
Total sessionscom.dynatrace.extension.sql-oracle.sessions.allTotal sessions countCount
User callscom.dynatrace.extension.sql-oracle.sessions.userCalls.countTotal number of logins, parses, or execute callsCount
Deadlockscom.dynatrace.extension.sql-oracle.sessions.deadlocks.countTotal number deadlocksCount
Metric nameMetric keyDescriptionUnit
Free spacecom.dynatrace.extension.sql-oracle.asm.disk_group.free_mbFree disk space available on this Oracle ASM Disk GroupMegaByte
Total spacecom.dynatrace.extension.sql-oracle.asm.disk_group.total_mbTotal disk space available on this Oracle ASM Disk GroupMegaByte
Used spacecom.dynatrace.extension.sql-oracle.asm.disk_group.usagePercentage of disk space used on this Oracle ASM Disk GroupPercent
Metric nameMetric keyDescriptionUnit
Instance pingcom.dynatrace.extension.sql-oracle.rac.instance_pingRepresents the current inter-instance ping of 8K messages as provided in GV$INSTANCE_PING.MicroSecond
-com.dynatrace.extension.sql-oracle.rac.interconnects--
Metric nameMetric keyDescriptionUnit
Number of wait events by wait classcom.dynatrace.extension.sql-oracle.wait.countTotal number of waits by wait class, excluding 'Idle' eventsCount
Seconds waited by wait classcom.dynatrace.extension.sql-oracle.wait.time.countTotal amount of time waited by wait class, excluding 'Idle' eventsMicroSecond
Metric nameMetric keyDescriptionUnit
Number of wait eventscom.dynatrace.extension.sql-oracle.wait.events.countTotal number of waits by wait event, excluding 'Idle' events. Only collects the top 20 most time consuming events.Count
Seconds waitedcom.dynatrace.extension.sql-oracle.wait.events.time.countTotal amount of time waited by wait event, excluding 'Idle' events. Only collects the top 20 most time consuming events.MicroSecond
Metric nameMetric keyDescriptionUnit
Physical bytes readcom.dynatrace.extension.sql-oracle.io.bytesRead.countTotal size in bytes of disk reads by all database instance activity including application reads, backup, recovery, and other utilitiesByte
Physical bytes writtencom.dynatrace.extension.sql-oracle.io.bytesWritten.countTotal size in bytes of all disk writes for the database instance including application activity, backup, recovery, and other utilitiesByte
Total wait timecom.dynatrace.extension.sql-oracle.io.wait.countTotal time spent in all wait states except for Idle classMilliSecond
Metric nameMetric keyDescriptionUnit
Dataguard severe eventscom.dynatrace.extension.sql-oracle.dataguard.severeEventsCounts 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 activitycom.dynatrace.extension.sql-oracle.dataguard.nologgingActivityCounts 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 statuscom.dynatrace.extension.sql-oracle.dataguard.archiveDestErrStatusCounts 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. differencecom.dynatrace.extension.sql-oracle.dataguard.seqDifferenceTracks 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 nameMetric keyDescriptionUnit
Connection management timecom.dynatrace.extension.sql-oracle.queries.connectionManagement.countTime spent on performing session connect and disconnect callsMicroSecond
PL SQL exec timecom.dynatrace.extension.sql-oracle.queries.plSqlExec.countTime spent on running the PL/SQL interpreterMicroSecond
SQL exec timecom.dynatrace.extension.sql-oracle.queries.sqlExec.countTime spent on executing SQLMicroSecond
SQL parse timecom.dynatrace.extension.sql-oracle.queries.sqlParse.countTime spent on parsing SQLMicroSecond
DB Timecom.dynatrace.extension.sql-oracle.queries.dbTime.countTime spent on performing Database user-level callsMicroSecond
DB CPUcom.dynatrace.extension.sql-oracle.queries.cpuTime.countCPU time spent on performing database user-level callsMicroSecond

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

🪲 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

Full version history

  1. Fixed double instance issue and thus the problem of missing metrics or Long running queries
  2. The Properties and tags sections have been supplemented with missing properties

Full version history

  1. Introduced backup tracking in a dedicated feature set. Backup jobs' metrics are available via a dedicated Unified Analysis page
  2. Improved status reporting via the Instance status metric and entity properties
  3. Fixed internal topology relationship definition

Full version history

  1. Improved metrics for the CPU. Metrics now show CPU usage in centisecond per second.
  2. Fixed situations where CDB was detected as PDB

Full version history

  1. Topology model extended to introduce container and pluggable databases, server instances and DB services
  2. Fill feature set's information about metrics
  3. Unify "device" attributes with product's naming conventions
  4. Connect gaps by default for CPU monitoring
  5. Remove dns_names attribute for "device"

Full version history

  • The interval for the Tablespaces group has been changed to 5 minutes
  • Dashboard has been unified and is now consistent with the other extensions
  • Disabled chart from Most time consuming queries section by default

Full version history

Renaming the dashboard and updating the tags

Full version history

Recyclebin is taken into account for free space calculation in tablespaces.

Full version history

Fixed incorrect definition of Oracle host entity related to most time consuming queries.

Full version history

Add a primary dimension definition to the extension alerts

Full version history

Fixed Management Zone filtering on Oracle Database extensions dashboard.

Full version history

  1. Added monitoring of most time consuming SQL Queries
  2. Introduce 5 minutes interval for most time consuming SQL Queries
  3. Improved the number of monitored instances shown

Full version history

  1. Change name of "used space" to "used space ratio". There was a duplicate
  2. Change tablespace used metrics from calculated to basic ones
  3. Calculated metrics not visible in feature set's details

Full version history

Version 1.0.4

  • Add a Oracle ASM query and featureset

Full version history

  • Removed column aliases incompatible with Oracle versions prior to 12.2
  • Use avg aggregation in host UA screen
  • Add featuresets

Full version history

Initial extension release

Dynatrace Hub
Certified PartnersGet data into DynatraceBuild your own app
All (714)Log Management and AnalyticsKubernetesAI/ML ObservabilityInfrastructure ObservabilitySoftware DeliveryApplication ObservabilityApplication SecurityDigital ExperienceBusiness Analytics
Filter
Type
Built and maintained by
Deployment model
SaaS
  • SaaS
  • Managed
Dynatrace Developer
Filter
Type
Built and maintained by
Deployment model
SaaS
  • SaaS
  • Managed

Discover recent additions to Dynatrace

Problems logo

Problems

Analyze abnormal system behavior and performance problems detected by Davis AI.

Logs logo

Logs

Explore all your logs without writing a single query.

Security Investigator logo

Security Investigator

Fast and precise forensics for security and logs on Grail data with DQL queries.

Business Flow logo

Business Flow

Track, analyze, and optimize your critical business processes.

Carbon Impact logo

Carbon Impact

Provides the information about site's carbon footprint

Davis Anomaly Detection logo

Davis Anomaly Detection

Detect anomalies in timeseries using the Davis AI

Analyze your data

Understand your data better with deep insights and clear visualizations.

Notebooks logo

Notebooks

Create powerful, data-driven documents for custom analytics and collaboration.

Dashboards logo

Dashboards

Transform complex data into clear visualizations with custom dashboards.

Automate your processes

Turn data and answers into actions, securely, and at scale.

Workflows logo

Workflows

Automate tasks in your IT landscape, remediate problems, and visualize processes

Jira for Workflows logo

Jira for Workflows

Create, query, comment, transition, and resolve Jira tickets within workflows.

Slack logo

Slack

Automate Slack messaging for security incidents, attacks, remediation, and more.

Secure your cloud application

See vulnerabilities and attacks in your environment.

Security Overview logo

Security Overview

Get a comprehensive overview of the security of your applications.

Third-Party Vulnerabilities logo

Third-Party Vulnerabilities

Detect vulnerabilities in real time, with context and automated risk assessment.

Code-Level Vulnerabilities logo

Code-Level Vulnerabilities

Detect vulnerabilities in your code in real time.

Attacks logo

Attacks

Get a real-time overview of all the attacks on your environment.

Are you looking for something different?

We have hundreds of apps, extensions, and other technologies to customize your environment

Leverage our newest innovations of Dynatrace Saas

Kick-start your app creation

Kick-start your app creation

Whether you’re a beginner or a pro, Dynatrace Developer has the tools and support you need to create incredible apps with minimal effort.
Go to Dynatrace Developer
Upgrading from Dynatrace Managed to SaaS

Upgrading from Dynatrace Managed to SaaS

Drive innovation, speed, and agility in your organization by seamlessly and securely upgrading.
Learn More
Log Management and Analytics

Log Management and Analytics

Innovate faster and more efficiently with unified log management and log analytics for actionable insights and automation.
Learn more