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

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.

Report Generation

The job also includes reporting templates that outline the configuration and status of the archivelogs along with initialization parameters related to archiving.

SQL Extraction and Analysis

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.