Use the Top SQL Outliers health check in Mini DBA to review Oracle configuration, metadata, and monitoring signals before they become active alerts.
This health check tests a specific Oracle condition that Mini DBA can assess from configuration, metadata, or recent monitoring data.
The check turns an operational best practice into a repeatable Mini DBA review item so teams do not rely on memory or occasional manual audits.
Open the failed check in Mini DBA, identify the affected object or setting, confirm whether it is intentional, then correct the configuration or record an approved exception.
Keep a short note explaining why the check failed, what was changed, who owns the follow-up, and whether an exception was approved.
Prioritize it by blast radius. Fix it quickly when it affects a production workload, a shared server, or a customer-facing service; otherwise place it in the normal improvement backlog with an owner.
Prevent repeat failures by assigning an owner, documenting the expected configuration, and reviewing the check after upgrades, migrations, or major application releases.
Add this page to the operational runbook for Oracle environments where the check repeatedly fails. Record local thresholds, approved exceptions, escalation contacts, and the expected review interval so the next administrator can act quickly without rediscovering the same context.