ASM diskgroup space
Job details
Name: |
ASM diskgroup space |
Platform: |
Oracle |
Category: |
Capacity |
Description: |
Checks ASM diskgroups space statistics. |
Long description: |
Task checks ASM diskgroups for space statistics. |
Version: |
3.6 |
Default schedule: |
2,12,22,32,42,52 * * * |
Requires engine install: |
Yes |
Compatibility tag: |
.[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & _priv_read_v_asm_diskgroup = ‘1′] |
Parameters
Name |
Default value |
Description |
Warning level in percent |
10 |
Percent free space in diskgroup before warning. Example: 10.2 |
Warning level in GB |
20 |
Gigabytes free space in diskgroup before warning. Example: 10 |
Delete statistics older than (hours) |
336 |
Statistics older than this amount of days will be removed from repository |
Alarm level in percent |
5 |
Percent free space in diskgroup before warning. Example: 5.2 |
Alarm level in GB |
5 |
Gigabytes free space in diskgroup before warning. Example: 5 |
Ignore ASM diskgroups |
|
A comma separated list of diskgroup names to ignore. |
Job Summary
- Purpose: The purpose of this job is to monitor the space usage of ASM diskgroups in Oracle databases, providing early warnings and alarms based on defined thresholds to prevent potential storage issues.
- Why: This job is important to ensure that the database does not run into space-related issues which could affect its availability and performance. Adequate monitoring can help in proactive management of disk space, thus avoiding emergencies or unplanned downtime.
- Manual checking: You can check the ASM diskgroup space usage manually in the database by issuing this SQL command:
SELECT name, total_mb, free_mb, usable_file_mb FROM v$asm_diskgroup;
Job Details
- “ASM diskgroup space”: Monitors the space statistics of ASM diskgroups.
- It filters instances of Oracle databases that specifically have ASM enabled and where the user has read privileges on the v$asm_diskgroup view.
- Version and Vendor Info:
Monitoring Logic Implementation
- The procedure “diskgroup_check” collects data from the v$asm_diskgroup view.
- It executes conditionally based on thresholds for warning and alarm levels defined in GB and percent.
- Historical data older than a specified period (default 336 hours) is automatically purged.
- Filters can be applied to ignore certain diskgroups.
- Inserts performance data into a history table for trend analysis and future reference.
Maintenance and Error Handling
- The script provides mechanisms to handle unexpected errors during the execution of the monitoring job.
- It includes SQL commands for granting necessary database permissions crucial for the monitoring script to execute successfully.
- Automatically updates monitoring statuses and logs any exceptions encountered during its operations.
Conclusion
This job is crucial for maintaining the health of Oracle ASM environments. By efficiently monitoring and reporting on diskgroup capacities and their usage, it facilitates better database management and preemptive handling of potential storage issues.