Effectively manage the space of the ASM disk group

ORA-15041: the direct and indirect impact of diskgroupspaceexhausted on your database environment? Disk Space Problems and ORA-15041 errors related to the ASM disk group

ORA-15041: the direct and indirect impact of diskgroup space exhausted on your database environment? Disk Space Problems and ORA-15041 errors related to the ASM disk group

ORA-15041: the direct and indirect impact of diskgroup space exhausted on your database environment?

Disk Space Problems and ORA-15041 errors related to the ASM disk group can have a serious impact on the database environment, as shown in

Database suspension/database crash

Archiving, backup, and recovery failed

Clone build latency

IO imbalance/IO failure

Performance decline

Best practices and proactive measures taken to manage the ASM disk groups and their space used to proactively avoid ORA-15041: diskgroup space exhausted.

Monitoring:

Continuous monitoring space usage is important. Below are a series of suggestions

Monitor disk groups and their disk space usage

Set a warning when the disk group and its disk usage reaches %

=> You can use Enterprise Manager and/or monitoring scripts that are queried Based on the v $ asm _ * view (for examples, see Note 470211.1)

Monitor whether there are any space-related errors or warnings in ASM alert. log.

=> This helps to add more space or clear space from the disk group as needed. Ideally, no disk in a disk group should have nearly 100% utilization.

Best practices:

In addition, the following best practices should be taken into account:

Monitor each disk, not the entire disk group.

All disks in the disk must be of the same size.

I/O loads must be evenly distributed to disks of the same size.

If there are different disks, try to add and delete disks in the disk group to obtain disks of the same size, or re-adjust the disk size if possible.

For normal redundancy and high redundancy disk groups, each fault group should have the same number of disks of the same size.

If you see imbalance at any time through monitoring (due to failed disk addition or other reasons), you can manually rebalance online.

Note: You can dynamically control the load that the rebalancing operation applies to the system by configuring the parallel (power) limit settings for rebalancing.

You can also run the "check all norepair" command on the disk group from time to time. In addition to space problems, if the disk group has any other problems, it will also be reported in ASM alert. log.

Recommended reading:

How to change the password of ASM sys

How to copy data files in ASM to the Operating System

Restoration After all Oracle 11g rac asm disks are lost

Oracle 11g from entry to proficient in PDF + CD source code

Installing Oracle 11g R2 using RHEL6 ASM

Oracle 10g manual creation of the ASM Database