Dynatrace Hub - Oracle Database latest releases

Oracle Database 4.1.3

Wed, 19 Aug 2026 10:24:23 +0000

🪲 Fixed in this version:

Fixed health charts for Oracle nodes in the Infrastructure and Operations app.

Oracle Database 4.1.1

Fri, 07 Aug 2026 11:33:05 +0000

✨ New in this version:

This extension is now using all rich visualization features of Grail within Infrastructure & Operations App.

🚀 Improved in this version:

Added container.name dimension to execution plan logs.
Added group.name dimension to ASM disk metrics.

🪲 Fixed in this version:

Fixed issue where a relationship between Oracle RAC nodes and OneAgent hosts would sometimes not be properly established.
Fixed missing edges between DB_DATABASE_ORACLE and DB_INSTANCE_ORACLE for RAC setups.

Oracle Database 4.0.6

Tue, 07 Jul 2026 13:13:21 +0000

🪲 Fixed in this version:

Fixed issue where log.sql-oracle.top_n_queries.* would sometimes not be collected.

Oracle Database 4.0.0

Thu, 28 May 2026 08:06:34 +0000

⚠️ Breaking changes:

⚠️ Possible breaking changes and warnings - PLEASE READ before upgrading to this version ⚠️:

This version requires a minimum Dynatrace version of 1.338.
This version includes a breaking change for 3rd gen environments:
- With the inclusion of OpenPipeline pipelines, any logs emitted by this extension will be processed by a dedicated OpenPipeline pipeline instead of the classic pipeline. This means that classic rules will no longer be used on logs emitted by the extension. Please be sure to migrate any you still need to OpenPipeline rules.
- Some field names are handled differently in OpenPipeline, e.g. capitalization. Please double-check any custom dashboards and alerts you have created for this extension.
- Any dynamic pipelines that were configured to route metrics or logs coming from this extension will no longer be used as data will be statically routed to the extension-shipped pipeline.
- Finally, you must opt-in to OpenPipeline configuration via Settings API – see documentation.

✨ New in this version:

Smartscape 2.0 topology support.

Oracle Database 3.9.6

Thu, 12 Mar 2026 11:13:34 +0000

🪲 Fixed in this version:

Updated entity links in Platform dashboard to point to the Infrastructure and Operations app.
Entity creation rules now explicitly filter out null dimension values.

Oracle Database 3.9.4

Tue, 03 Feb 2026 11:45:15 +0000

✨ New in this version:

Added the following metrics to the memory feature set:
- com.dynatrace.extension.sql-oracle.memory.consistentGetsFromCache.count
- com.dynatrace.extension.sql-oracle.memory.dbBlockGetsFromCache.count
- com.dynatrace.extension.sql-oracle.memory.physicalReadsCache.count

🚀 Improved in this version:

Updated the calculation for buffer cache hit ratio to reflect current Oracle documentation.

🪲Fixed in this version:

Fixed issue where RAC instance local IP address would not be properly reported on the right entity.

Oracle Database 3.9.2

Mon, 19 Jan 2026 10:27:21 +0000

🚀 Improved in this version:

The relationship between OneAgent host and Oracle instances now supports RAC instances as well. For local IP discovery to work correctly, the extension needs access to the UTL_INADDR.get_host_address function. Please see the official documentation for more information on how to assign these additional permissions.

⚠️This feature is available under the RAC feature set. If you have this feature set enabled and start seeing permission error warnings in the extension logs after updating the extension to the latest version, there is no cause for concern. No data is being lost, simply update the permissions as described above to take advantage of the new feature, or disable the RAC feature set if it is not relevant for your use case.
Added feature set descriptions and recommendations.

Oracle Database 3.8.1

Wed, 17 Dec 2025 09:21:36 +0000

✨ New in this version:

Added ALERT_TEMPLATES for anomaly detectors in the Davis Anomaly Detection app.

Oracle Database 3.7.9

Mon, 08 Dec 2025 15:29:20 +0000

For internal alignment reasons, versions 3.1.3 to 3.7.5 will no longer be available on the Hub for installation. For users currently on any of these versions there is no immediate need to take any action, as they will continue to work fine.

For users upgrading to the latest version from any of those versions, previous release notes are provided below:

Version 3.7.5

🪲 Fixed in this version:

Server version is now correctly set as an entity attribute for the instance entity type.
Fixed issue where requesting an execution plan from the Databases app could result in a 405.
Fixed issue where tablespace content type dimension would sometimes split properly in the Data Explorer.
Fixed tablespace charts showing wrong values for large timeframes.

Version 3.7.1

🚀 Improved in this version:

The dt.security_context parameter is now propagated to all entities created by the extension. When definition entity permissions based on dt.security_context ensure you set the Grail security context destination property to dt.security_context
The dt.security_context is now a dimension of all the log. metrics created by the extension.

🪲 Fixed in this version:

Fixed uptime metric chart in databases app not showing.
Fixed typo in the uptime metric name.

Version 3.6.2

✨ New in this version:

Added a new metric com.dynatrace.extension.sql-oracle.uptime.

🚀 Improved in this version:

The instance unavailable alert now relies on the new uptime metric instead of the status metric.
Reworked top statement charts in the Databases app.

Version 3.5.0

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

Version 3.4.2

🪲 Fixed in this version:

Fixed issue where backup data would be captured for too long in cases where the ActiveGate timezone did not match the database timezone.

Version 3.4.0

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

Version 3.3.4

🪲 Fixed in this version:

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

Version 3.3.3

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

Version 3.2.1

🪲 Fixed in this version:

Sorting SQL statements in the Databases app would retrieve duplicate results

Version 3.2.0

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

Version 3.1.3

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

Oracle Database 3.7.8

Thu, 04 Dec 2025 14:02:27 +0000

🪲 Fixed in this version:

Added internal metadata.

Oracle Database 3.7.7

Wed, 19 Nov 2025 15:13:28 +0000

🪲 Fixed in this version:

Fixed cluster wait events visualization in built-in Platform dashboard.

Oracle Database 3.7.6

Tue, 07 Oct 2025 10:30:35 +0000

🪲 Fixed in this version:

Cleaned up duplicate topology rule.

Oracle Database 3.1.0

Mon, 07 Oct 2024 15:00:33 +0000

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

Oracle Database 3.0.15

Wed, 28 Aug 2024 20:51:29 +0000

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

Oracle Database 3.0.7

Thu, 01 Aug 2024 12:55:55 +0000

⚠️ 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.

Oracle Database 2.5.1

Thu, 04 Jul 2024 13:22:30 +0000

⚠️ 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.

Oracle Database 2.5.0

Fri, 28 Jun 2024 13:46:04 +0000

⚠️ 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.

Oracle Database 2.4.3

Mon, 03 Jun 2024 16:33:03 +0000

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

Oracle Database 2.3.0

Mon, 20 May 2024 12:19:23 +0000

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

Oracle Database 2.2.3

Thu, 11 Apr 2024 21:02:54 +0000

🪲 Fixed in this version:

ASM Disks tiles in the dashboard were using outdated metric names