Archive status Check
Job details
| Name: | Archive status Check |
| Platform: | Oracle |
| Category: | Availability |
| Description: | Checks how many redolog files that are not archived. |
| Long description: | Checks how many redolog files that are not archived. |
| Version: | 2.9 |
| Default schedule: | * * * * |
| Requires engine install: | Yes |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & _priv_read_v_log = ‘1′ & _priv_read_v_instance = ‘1′ & _priv_read_v_parameter = ‘1′] |
Parameters
| Name | Default value | Description |
|---|---|---|
| max not archived | 3 | This is the maximum number of redolog groups that are allowed to have status “not archived” before a WARNING is triggered. If all redolog groups have status “not archived”, an ALARM is triggered. |
Job Summary
- Purpose: The purpose of this monitoring job is to check the archival status of Oracle redo log files.
- Why: This job is crucial to ensure that redo logs have been properly archived in Oracle database systems, which is key for data protection and recovery procedures. Monitoring these logs helps prevent data loss and maintains the database’s integrity in case of system failures.
- Manual checking: You can check the archival status manually in the database by executing the following SQL commands:
SELECT SEQUENCE#, archived, status FROM v$log WHERE THREAD# = (SELECT THREAD# FROM v$instance) ORDER BY SEQUENCE# ASC;Description and Implementation
The job, named “Archive status Check”, verifies the number of redo log files that have not been archived. A procedure is implemented to count how many redo logs remain unarchived and compares this number with a threshold (‘max not archived’). If the number of unarchived logs exceeds this threshold, a warning or alarm is triggered based on the count.
- Name: Archive status Check
- Description: Checks how many redolog files that are not archived.
- Version: 2.9
- Company: dbwatch.com
- Dependencies: This job has a self-dependency to check its own status and evaluate the archive conditions.
- Implemented Procedure: The implemented SQL procedure checks through “v$log”, “v$instance”, and “v$parameter” to ascertain the archival status, and tasks the dbWatch system to update the monitoring status based on the results.
Report Generation
The job also includes reporting templates that outline the configuration and status of the archivelogs along with initialization parameters related to archiving.
- Title: Archivelog configuration
- Description: Displays information about redo log files and their archiving configuration.
- Contents:
- Information on redo log group ID, status, file name, size, and archival status.
- Oracle initialization parameters relevant to the archival and recovery configurations.
SQL Extraction and Analysis
- “Archive status Check” conducts its analysis through a series of SQL queries:
- Validating the environment by checking privileges on necessary Oracle dictionary views.
- Counting redo logs that are not yet archived and comparing against predefined parameters to determine overall archival health.
- Generating user-readable output regarding the status of redo logs, whether they are fully archived, and details of any discrepancies or issues.
Conclusion
This dbWatch Control Center job is a comprehensive tool designed to monitor and report on the archival health of Oracle database redo log files. Ensuring that redo logs are properly archived is critical for recovery and auditing processes, making this job essential for database administration and operational integrity.