Oracle Database / Storage, Undo & Redo
Monitor an ASM rebalance before declaring storage maintenance stuck
A rebalance can take time while redistributing extents after a storage change. Inspect its reported state and progress.
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 group_number, operation, state, power, actual, sofar, est_work, est_rate, est_minutes FROM v$asm_operation;Read the result
On the ASM instance, rows describe current operations and estimates. Estimated time can change as work and resource pressure change.
Resolve and verify
Correlate progress with storage latency and the approved maintenance plan. Adjust power only through the ASM owner after evaluating foreground I/O impact.
Operational precautions
Do not restart ASM or remove disks to speed up a slow estimate. Rebalance changes can affect every dependent database.