All
0 Results filtered by:
We couldn't find any results
You can search all listings, or try a different spelling or keyword. Still nothing? Dynatrace makes it easy to create custom apps.
Oracle DatabaseOracle Database
Observe, analyze and optimize the usage, health and performance of your database
Extension- 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
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.
Extension content
Content typeNumber of items included
screen logs cards
4
list screen layout
7
metric metadata
99
screen message cards
4
document dashboard
1
screen actions
16
screen chart groups
40
screen entities lists
15
screen dql table
12
screen metric tables
8
generic type
6
screen custom cards
2
screen properties
6
dashboards
1
metric query
5
log metric
12
alerts
9
screen layout
12
generic relationship
10
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 |
| Instance Uptime | com.dynatrace.extension.sql-oracle.uptime | The uptime of the Oracle instance in seconds. | Second |
| 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 |
|---|---|---|---|
| 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 |
| 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 |
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
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_contextparameter is now propagated to all entities created by the extension. When definition entity permissions based ondt.security_contextensure you set the Grail security context destination property todt.security_context - The
dt.security_contextis now a dimension of all thelog.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-filterwhich 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_metadatavariable 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_instanceand Oracle Listener PGI
🪲 Fixed in this version:
- Fixed
com.dynatrace.extension.sql-oracle.io.bytesRead.countandcom.dynatrace.extension.sql-oracle.io.bytesWritten.countbeing 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 frequencyheavy-query-interval. This fixes an issue where setting theheavy-query-timeoutvariable 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.seqprimary.archived.seqstandby.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-intervalandheavy-query-intervalto 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 toTablespaces (detailed)and the theTablespacesfeature set now contains a simpler, less resource-intensive query to monitor tablespaces. This query drops thecom.dynatrace.extension.sql-oracle.tablespaces.allocatedSpacemetric 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 theTablespacesfeature set. ⚠️
- ⚠️ When updating an existing configuration to the new version, the new
- 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_databaseentity.
ℹ️ 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.
Full version history
🪲 Fixed in this version:
- Added internal metadata.
Full version history
🪲 Fixed in this version:
- Fixed cluster wait events visualization in built-in Platform dashboard.
Full version history
🪲 Fixed in this version:
- Cleaned up duplicate topology rule.
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 theasmfeature 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. ⚠️
- ⚠️ When updating an existing configuration to the new version, the new
🚀 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
runsOntocalls. - OneAgent detected hosts,
dt.entity.host, now have asameAsrelationship with instances.
- The host entity,
- 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 thelog.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.
- A cluster entity,
- 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$ROOTis now detected as a container. Tablespaces and datafile charts for theCDB$ROOTare now show in theCDB$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
sessionsfeature set - Blocked session details are ingested as logs as part of the
Blocked sessionsfeature set. Records can be filtered byevent.group == "blocked_sessions"in the log query.
- Metrics for number of blocked sessions and deadlocks are part of the
- 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
TopNfeature 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_metadataattribute of the Oracle Instance entity and can be used in entity selectors (to facilitate tagging, for example).
- This parameter will populate the
🚀 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
eventdimension fromcom.dynatrace.extension.sql-oracle.wait.countandcom.dynatrace.extension.sql-oracle.wait.time.countto prevent inadvertently high DDU consumption. To replace the previous functionality a new feature set,waitEvents (detailed), was added with metricscom.dynatrace.extension.sql-oracle.wait.events.countandcom.dynatrace.extension.sql-oracle.wait.events.time.countwhich 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_METRICSwhich 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_cdbsql:com_dynatrace_extension_sql-oracle_pdb(replace withsql: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