FREE_MB From V$ASM_DISKGROUP/V$ASM_DISK And V$ASM_ACFSVOLUMES/V$ASM_FILESYSTEM, Do Not Match
(Doc ID 1496935.1)
Last updated on SEPTEMBER 16, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
FREE_MB between view v$asm_diskgroup or v$asm_disk AND v$asm_acfsvolumes or v$asm_filesystem, do not match.
Example:
* v$asm_diskgroup: FREE_MB=3800 <-- TEMP_SUMP_ZONE disk group
* v$asm_disk: FREE_MB=3800 <-- TEMP_DUMP_ZONE_0000 (/dev/rdsk/c0d5s6) disk
* v$asm_acfsvolumes/v$asm_filesystem: FREE_MB=290795.086 <-- fs_name=/temp_dump_zone (vol_device=/dev/asm/voltemp-96)
The concern is that backups may fail because ASM may detect there is not sufficient space.
According to the documentation, free_mb from these v$asm* views report the same value:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |