Oracle operations

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

Use the Oracle Operations page to review backup freshness, RMAN job history, Scheduler job state, Flash Recovery Area pressure, archive destination status, ASM disk group state, and redo log switch history for a monitored Oracle server. For the recoverability-focused workflow, see Oracle Backup And Jobs.

Screenshot pending: Mini DBA Oracle Operations screenshot placeholder

What Mini DBA shows

RMAN status, last successful backup time, and recent RMAN backup jobs from V$RMAN_BACKUP_JOB_DETAILS.
Oracle Scheduler job inventory and recent Scheduler failures from DBA_SCHEDULER_JOBS and DBA_SCHEDULER_JOB_RUN_DETAILS.
Flash Recovery Area capacity from V$RECOVERY_FILE_DEST and file-type usage from V$RECOVERY_AREA_USAGE.
Archive destination status from V$ARCHIVE_DEST_STATUS, including destination error and gap state.
ASM disk group capacity, redundancy, usable space, compatibility, and offline disk count from V$ASM_DISKGROUP when ASM is accessible.
Redo log switch history from V$LOG_HISTORY.

How to use it

Start with the summary row. A stale or missing RMAN backup is a recoverability risk even when the database is otherwise healthy. A recent failed RMAN job deserves separate attention because an older successful backup may still exist but the current backup schedule may be broken.

Use Scheduler Jobs to identify disabled, failed, or repeatedly retrying jobs. Use Scheduler Failures for recent failure details and hand the job name, error number, and additional info to the DBA or application owner.

Use Recovery Area and Archive Destinations together when archiving, backup, or Data Guard symptoms appear. The Recovery Area tab separates overall capacity from file-type usage so archived logs, backups, and flashback logs can be triaged separately. FRA pressure can stop archiving, and destination errors can break redo transport or recovery point readiness. If the database uses ASM, check ASM Disk Groups for low usable space or offline disks before treating storage symptoms as purely tablespace-level problems.

Alerts and AI

Oracle Operations feeds the Mini DBA AI Assistant with RMAN, Scheduler, FRA, ASM, archive destination, and redo evidence. The assistant can summarize likely operational risks and suggest a safe triage order.

Related alerts include RMAN Backup Age, RMAN Backup Failures, Failed Scheduler Jobs, Flash Recovery Area Usage, Redo Log Switches Per Hour, Data Guard Destination Errors, and Alert Log Errors.

Permissions

The monitoring login needs access to the backup, recovery, redo, and Scheduler views listed above. In the Oracle permissions modal, check Backup And Job Views, Data Guard Views, and ASM Views if ASM monitoring is required. For multitenant Oracle, a CDB/root common monitoring user gives Mini DBA the most complete operational view.