RMAN backup status alert
Job details
| Name: | RMAN 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.21 |
| Default schedule: | 4h |
| 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 job monitors and reports on the status of Oracle RMAN backups.
- Why: This job is essential to ensure the safety and availability of database backups. Monitoring the status allows for timely responses if backups fail, complete with warnings or errors, or if they are not executed within expected time frames. This in turn helps maintain the integrity and reliability of the database.
- Manual checking: You can check the RMAN backup status manually in the database by issuing the following SQL commands:
bc.. select st, ttd, s, ob, ib from ( select to_char(start_time, ‘YYYY.MM.DD HH24:MI:SS’) as st, time_taken_display as ttd, status as s, round(output_bytes/1024/1024) as ob, round(input_bytes/1024/1024) as ib from v$rman_backup_job_details where input_type in (‘DB INCR‘,‘DB FULL‘) order by 1 desc ) where rownum = 1
Details Analyzed From Job Configuration
- Job Name: Oracle RMAN backup
- Version: 1.2
- Company: dbwatch.com
- Group: com.dbwatch.job
- Artifact ID: oracle_noschema_rman_backup
- Compatibility: The job is compatible with Oracle database instances, specifically those of version 12 and above, and where is_phy_standby or hasengine attributes are set accordingly.
- Visibility: Certain job properties, specifically those related to reading detailed RMAN status, are hidden from normal view, possibly for security or user interface clutter reduction.
- Category: The job falls under the category “Availability.”
- Execution and Alerts: Upon detection of an outdated backup or a backup with issues, the system goes into alert status based on predefined thresholds (96 hours for alarms, and 48 hours for warnings).
- Default Schedule: Runs every four hours.
SQL and JavaScript Execution Logic
- The job extracts detailed information from the Oracle view `v$rman_backup_job_details` about the most recent backup, including start time, duration, status, and the sizes of data processed.
- Status evaluations and alerting are handled by embedded JavaScript within the job.
- There are detailed error messages tailored based on whether backups are currently running, have completed with issues, or have failed.
Report Generation
- Report Title: RMAN Backup Status
- Report Description: Checks RMAN backup status
- Schedule Frequency for Reporting: Hourly
- Report Details:
- The report dynamically generates and displays a table containing the latest RMAN backup status information, elaborating on each relevant aspect like the start time, duration, status, input, and output sizes.
Conclusion
This job setup in dbWatch Control Center is crucial for ensuring the consistency and reliability of RMAN backups in Oracle database environments. Regular and automated monitoring accompanied by detailed reporting and alerts helps maintain high standards of data protection and operational readiness in enterprise database systems.