Oracle Expiring Passwords Alert


Use the Expiring Passwords alert in Mini DBA to monitor Oracle instances and make this condition visible before it becomes a wider database incident.

Screenshot pending: Mini DBA Oracle Expiring Passwords alert screenshot placeholder

Alert Summary

  • Platform: Oracle
  • Alert category: General
  • Default enabled: false
  • Default evaluation frequency: Hour
  • Threshold label: Days until expiry
  • Unit: days

What Mini DBA Checks

Mini DBA describes this alert as: User passwords expiring soon Password expiration can cause application outages Notify application owners to update passwords The default evaluation frequency is Hour, so the alert is intended to be close enough to operational reality for live triage.

Why This Alert Is Helpful

This alert helps administrators notice security-sensitive events before they become routine background noise. Failed authentication, expiring passwords, or audit issues can indicate access problems, misconfiguration, or active probing.

When To Enable It

Enable it on production, shared, regulated, and externally reachable environments. You can use lower severity in isolated development systems, but keeping the signal visible helps catch account and permission drift early.

Threshold Guidance

Threshold meaning: Days until expiry. Major threshold: 3 days. Minor threshold: 7 days. Comparison direction: "under". Use higher thresholds on batch-heavy, development, or intentionally bursty systems where brief pressure is expected. Use lower thresholds on latency-sensitive production systems, small instances with little headroom, and services with strict recovery or availability commitments.

Remediation For An Active Alert

Review the affected principals, source hosts, and recent access changes. Rotate or unlock accounts only after confirming ownership, remove stale permissions, investigate repeated failures, and document any security exception with an expiry date.

Investigation Workflow

  1. Confirm the alert is still active and note the first seen time, affected instance, and severity.
  2. Review the affected principal, source host, authentication path, recent permission change, and audit trail in Mini DBA before changing configuration or ending sessions.
  3. Compare the current value with the normal baseline for the same time of day or maintenance window.
  4. Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding Alert Noise

If the alert creates repeated noise, review whether it is enabled on the correct instances, whether maintenance windows are configured, and whether the minor and major routes match the real business impact. Keep enough history to prove the new setting before changing it broadly.

Related Pages