Oracle Database / RMAN Backup & Recovery
Capture RMAN configuration before changing a failed job
A backup job can behave unexpectedly because of device, retention, encryption or channel configuration. Preserve current settings before editing them.
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.
SHOW ALL;Read the result
In RMAN, this reports persistent settings for the target database. Job scripts can override several defaults, so the output is not the whole execution context.
Resolve and verify
Compare the failed job's explicit commands and allocated channels with the intended media and policy. Correct the narrow configuration defect and run an approved bounded test.
Operational precautions
Configuration output can reveal infrastructure paths. Do not replace the entire configuration with values from another database.