Oracle archive log destination space alert

Start Here

Manual Home Installation Windows Installation Linux Engine Container Linux Console Container Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Mode Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Performance History Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

The Archive Log Destination Space alert notifies you when its configured condition is met on Oracle instances so you can investigate and respond.

Screenshot pending: Mini DBA Oracle Archive Log Destination Space alert screenshot placeholder

Alert summary

Platform: Oracle
Alert category: Disk
Default enabled: true
Default evaluation frequency: Minute
Threshold label: % full
Unit: %

What Mini DBA checks

Mini DBA describes this alert as: Archive log destination running out of space If archive destination fills, the database will hang until space is freed Critical alert - requires immediate attention Mini DBA evaluates this alert once a minute so changes are detected quickly. Because duration is used, Mini DBA can avoid treating a single short spike as a full incident when the condition clears quickly.

How this alert helps

This alert protects storage and recovery capacity. It helps you find growth, retention, and backup conditions that can stop writes, break recovery objectives, or leave the server without enough working space for normal database activity.

When to enable it

Enable it on systems with recovery objectives and on any database where a missed backup or archive problem would require business escalation. Test and lab systems can use looser settings if they are recreated from source control or seed data.

Threshold guidance

Threshold meaning: % full. Major threshold: 90 %. Minor threshold: 85 %. Comparison direction: over. Duration is used, so prefer requiring the condition to persist before paging people for transient spikes. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.

Remediation for an active alert

Free space by removing safe-to-delete files, expanding the volume or tablespace, moving growth-heavy objects, correcting retention settings, or shrinking only after a documented one-off event. For recovery-related areas, verify that backups and log shipping or archiving are healthy before deleting anything.

Investigation workflow

Confirm the alert is still active and note the first seen time, affected instance, and severity.
Review the affected disk, tablespace, log stream, backup job, retention setting, and recent growth pattern in Mini DBA before changing configuration or ending sessions.
Compare the current value with the normal baseline for the same time of day or maintenance window.
Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding alert noise

Storage alerts should usually stay enabled even on quiet systems because the impact of missing them is high. Tune warning thresholds to leave enough time for approval, provisioning, and validation, especially when storage changes are handled by another infrastructure team.