ASM diskgroup space
Job details
| Name: |
ASM diskgroup space |
| Platform: |
Oracle |
| Category: |
Capacity |
| Description: |
Checks the maximum number of processes. |
| Long description: |
|
| Version: |
1.1 |
| Default schedule: |
15m |
| Requires engine install: |
No |
| Compatibility tag: |
.[type=‘instance’ & databasetype=‘oracle’] |
Parameters
| Name |
Default value |
Description |
| used_alarm_threshold |
95 |
ASM diskgroup used percent to trigger alarm |
| used_warning_threshold |
90 |
ASM diskgroup used percent to trigger warning |
Job Summary
- Purpose: The purpose of this job is to monitor the available space on ASM diskgroups in Oracle databases.
- Why: This job is important to ensure that there is sufficient space on the ASM diskgroups to prevent any potential issues related to disk space shortages which could lead to database performance degradation or system downtime.
- Manual Checking: You can check this manually in the database by issuing the following SQL command:
select name as name, round(total_mb) total, round(free_mb) free, abs(round((free_mb/total_mb)*100)-100) usedpct from v$asm_diskgroup order by 4 desc
Details of Monitoring
- “ASM diskgroup space” is measured to track the usage percentage.
- Adequate threshold levels are set to raise warnings and alarms to prompt timely interventions:
- Warning is triggered when a diskgroup’s usage reaches the “used_warning_threshold” (default 90%).
- Alarm is triggered when usage reaches the “used_alarm_threshold” (default 95%).
Implementation and Automation
- The job scans Oracle ASM diskgroups, compatible with both physical standby databases and instances without schemas that utilize ASM.
- Automated tasks run every 15 minutes as per the default schedule configured in the job settings.
- Javascript used in the value engine assists in generating the appropriate status and message based on the disk usage percentages computed.
Output Handling
- Status messages are dynamically generated to reflect current diskgroup usage scenarios:
- If usage thresholds are exceeded, respective messages are appended indicating which diskgroup is affected and its current usage percentage.
- A general success message reflects the total count of diskgroups if no thresholds are breached.
Reporting Framework
- Reports on ASM diskgroup status form part of the dbWatch report template.
- A detailed report includes a table summarizing the status per diskgroup, aiding in visual representation and quicker assessments.
- Scheduled to update every hour, ensuring up-to-date information is always available.
- Report Template Version: Version 2, titled “ASM diskgroup status”, intended for continual checks on ASM diskgroup space conditions.
The thorough automation and reporting integrated into this dbWatch Control Center job significantly streamline the process of monitoring critical database resources, ensuring operational efficiency and preemptive troubleshooting.