How to Use Oracle RMAN CONFIGURE Settings

RMAN (Recovery Manager) is essential for Oracle Database operations. In this article, we will explain how to use Oracle RMAN CONFIGURE to dramatically improve operational safety and efficiency through control file autobackup and backup optimization.

By optimizing settings with the RMAN CONFIGURE command, you can perform recovery with minimal effort in the event of a failure. This guide covers the standard recommended configuration procedures for 19c environments and explains how the “Backup Optimization” mechanism saves storage capacity.

Conclusion: Quick Setup Steps (To-Do List)
Background and Basics: Why Are These Settings Necessary?
1. What is Control File Autobackup?
2. What is Backup Optimization?
Implementation: Executing the CONFIGURE Command
1. Execution Example
Troubleshooting: Common ORA Errors and Solutions
Operational, Monitoring, and Security Notes
FAQ: Frequently Asked Questions
Summary

Conclusion: Quick Setup Steps (To-Do List)

Simply connect to RMAN and execute the following two lines to complete the recommended configuration.

Enable Control File AutobackupCONFIGURE CONTROLFILE AUTOBACKUP ON;
Enable Backup OptimizationCONFIGURE BACKUP OPTIMIZATION ON;
Verify SettingsSHOW ALL;

Background and Basics: Why Are These Settings Necessary?

What is Control File Autobackup?

The control file is the “heart” of the database, holding the physical structure and backup metadata. If this is lost, RMAN itself cannot locate the backup files. When Autobackup is enabled, RMAN automatically creates a copy of the control file whenever a BACKUP command is executed or the database configuration changes (such as adding a datafile).

What is Backup Optimization?

This feature prevents redundant backups of identical read-only datafiles or archived logs that have already been backed up. This reduces network load and backup storage consumption.

Implementation: Executing the CONFIGURE Command

Follow these steps to configure the settings. Execution requires SYSBACKUP or SYSDBA privileges.

Connect to RMAN: Start RMAN from the command prompt or terminal.
Input Configuration Commands: Change each parameter to ON.
Customize Destination/Format (Optional): Set this if you want to output to a location other than the default Fast Recovery Area (FRA).

Execution Example

In a CDB/PDB configuration, these are typically executed from the root container (CDB$ROOT).

-- 1. Connect to RMAN (Example using OS authentication)
-- $ rman target /

-- 2. Enable Control File Autobackup
-- Control files are automatically saved during backup execution or structural changes
CONFIGURE CONTROLFILE AUTOBACKUP ON;

-- 3. Enable Backup Optimization
-- Skips files that haven't changed or logs already backed up
CONFIGURE BACKUP OPTIMIZATION ON;

-- 4. Specify Destination Directory (Example: /u01/app/oracle/backup/)
-- %F is a required variable that generates a unique filename including DB ID and date
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/app/oracle/backup/%F';

-- 5. Verify configuration details
SHOW ALL;

Note: Specifying a format without %F will result in an error; it must be included. Additionally, avoid using the @ symbol in passwords as it may cause issues with connection string interpretation during operations.

Troubleshooting: Common ORA Errors and Solutions

Here are solutions for problems commonly encountered during configuration or execution.

Error Code	Cause	Verification/Action
ORA-19809	Insufficient capacity in Fast Recovery Area (FRA)	Check `V$RECOVERY_FILE_DEST` and either expand `DB_RECOVERY_FILE_DEST_SIZE` or delete old backups.
RMAN-06103	Failed to write autobackup	Verify OS permissions (write access for the `oracle` user) for the specified path.
RMAN-06445	`%F` missing from format string	Re-execute the `CONFIGURE ... FORMAT` clause ensuring it includes `%F`.

Operational, Monitoring, and Security Notes

Pros: Eliminates the need to back up control files individually and improves recovery success rates.
Cons/Pitfalls: When “Backup Optimization” is enabled, a file might not be backed up if it is considered “identical,” even if it is required to satisfy the Retention Policy.
How to Reset: To return individual settings to their defaults, use the CLEAR keyword.CONFIGURE CONTROLFILE AUTOBACKUP CLEAR;CONFIGURE BACKUP OPTIMIZATION CLEAR;

FAQ: Frequently Asked Questions

Q: When is the control file autobackup executed?

A: It is executed after a BACKUP or COPY command completes, and after successful database structural changes, such as adding a datafile.

Q: What if I want to force a backup even with optimization enabled?

A: Execute the BACKUP command with the FORCE option.

Example: BACKUP DATABASE FORCE;

Q: Can I change settings for each PDB individually?

A: No, most persistent RMAN settings via CONFIGURE operate globally for the entire CDB (at the instance level).

Summary

CONFIGURE CONTROLFILE AUTOBACKUP ON is a recommended basic setting for all Oracle environments.
Backup Optimization (OPTIMIZATION ON) contributes to storage efficiency.
Configuration status can be checked at any time using SHOW ALL.
Use the CLEAR command to return settings to their initial state.

This article targets Oracle Database 19c (screens and default values may vary for other versions).

[reference]
Oracle Database Backup and Recovery Reference, 19c