RMAN ARCHIVELOG backup status alert
Job details
| Name: | RMAN ARCHIVELOG backup status alert |
| Platform: | Oracle |
| Category: | Availability |
| Description: | Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
| Long description: | |
| Version: | 1.1 |
| Default schedule: | 1h |
| Requires engine install: | No |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’] |
Parameters
| Name | Default value | Description |
|---|---|---|
| hours_alarm_threshold | 96 | Backup expire time (in hours). |
| hours_warning_threshold | 48 | Backup expire time (in hours). |
Job Summary
- Purpose: The purpose of this job is to monitor the status and performance of the Oracle RMAN ARCHIVELOG backups, ensuring they have completed successfully and within a reasonable time frame.
- Why: This job is critically important because it ensures that ARCHIVELOG backups, which are crucial for Oracle database recovery procedures, are up-to-date and have not encountered errors. Frequent monitoring helps in early detection of failures or issues, which reduces the risk of data loss and downtimes.
- Manual checking: Monitoring this manually can be done within the database by issuing specific SQL commands to retrieve records from the RMAN backup job details. This allows DBAs to inspect the comprehensive backup status directly.
Job Details
- Technology: This monitoring job is specifically designed for instances running Oracle databases.
- Job Name: Oracle RMAN ARCHIVELOG backup
- Version: 1.1
- Entity: It operates as a scheduled task, automating the routine check of RMAN backup status and performance.
Backup Status Determination
- SQL Execution:
- The job leverages Oracle’s internal views (v$rman_backup_job_details) to assess the latest archival log backups.
Output Conditions
- Warns about backups ending with errors or warnings.
- Alerts when the last successful backup occurred beyond the predefined warning and alarm thresholds (in hours).
- Provides comprehensive status messages that combine information about both the latest RMAN backup and its relative performance and success.
Status Output Analysis
- The JavaScript engine is employed to interpret fetched SQL data and to evaluate the logic defining alert statuses: error, warning, and OK.
- Depending on combined conditions of the most recent backup statuses and their completion recency, it sets the appropriate alert level.
Alert Conditions
- Status 0: Backup is OK.
- Status 1: Issues exist that might not immediately affect backup integrity but will need investigation.
- Status 2: Urgent attention is required due to backup failures or other critical issues.
Dashboard and Reporting
- Description: Checks the RMAN ARCHIVELOG backup status and presented in a user-friendly table format.
- Default Schedule: The job is scheduled to run hourly by default, ensuring up-to-date status and timely detection of issues.
Implementation
- The job is installable on Oracle instances, particularly versions 12 and above, including physical standby configurations without the engine-specific features.
- It is compulsory for the setting (true) to ensure this job is auto-installed and readily part of the monitoring suite in applicable Oracle database environments.
Diagnostic and Support
- Provides clear messages generated per evaluated conditions helpful for troubleshooting.
- Encourages immediate technical support interaction in scenarios where the job reports unresolved or ambiguous statuses.