Oracle Database / Storage, Undo & Redo
ORA-15041: investigate ASM disk group space exhaustion
A disk group can be unable to allocate a file even when raw free bytes appear sufficient. Redundancy and failure-group requirements affect usable capacity.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT name, type, total_mb, free_mb, required_mirror_free_mb, usable_file_mb FROM v$asm_diskgroup_stat;Read the result
Run with authorized access in the appropriate ASM context. USABLE_FILE_MB accounts for redundancy considerations and differs from raw FREE_MB.
Resolve and verify
Review disk balance, offline disks and actual growth demand with the ASM owner. Add supported capacity or remove only approved obsolete content through managed tools.
Operational precautions
Do not remove ASM files by guesswork or treat raw free space as fully allocatable application space.