Oracle Database / Storage, Undo & Redo
Check redo member paths and multiplexing health
A single redo member problem may be masked by another healthy member in the group. Identify affected paths before the remaining copy fails.
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#, status, type, member FROM v$logfile ORDER BY group#, member;Read the result
Member metadata and status show configured copies; a blank status is not an end-to-end storage health test. Correlate with alert-log errors.
Resolve and verify
Have the DBA validate the surviving members and storage layout, then repair redundancy through a supported change. Check that copies do not share one avoidable failure domain.
Operational precautions
Do not copy, rename or delete active redo members outside the documented database procedure.