Restore of Control File from Autobackup

You may need to restore the Oracle database control file in the following cases:

If you want to restore the database to a new location where the control file does not exist.
If the database control file is lost or corrupted.

If you use Veeam Plug-in for Oracle RMAN and want to restore the Oracle database control file from autobackup, the autobackup format must be set to the SBT_TAPE device type.

To check if persistent configuration for the control file autobackup format is set to the SBT_TAPE device type, you can run the SHOW ALL or SHOW CONTROLFILE AUTOBACKUP FORMAT commands in the RMAN console. If the persistent configuration is set, you don't need to set the control file autobackup format before the restore command. If it is not set, you must run the SET CONTROLFILE AUTOBACKUP command before the restore process. For more information, see Example 1. Restoring Control File if Persistent Configuration Setting Is NOT Set.

If you do not have the autobackup file name for the restore script, you can restore using the creation date of the autobackup file. For more information, see Example 3. Restoring Control File Without Autobackup File Name.

Note

To restore the control file from autobackup, the database must be in the NOMOUNT state.

Examples

Example 1. Restoring Control File if Persistent Configuration Setting Is NOT Set

If the persistent configuration for the control file autobackup format is NOT set to the SBT_TAPE device type, you must set the autobackup format before running the control file restore. To do this, run the following script:

RUN {

ALLOCATE CHANNEL channel0 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginforOracleRMAN/libOracleRMANPlugin.so';

SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F_RMAN_AUTOBACKUP.vab';

RESTORE controlfile FROM 'c-4097408439-20200410-00_RMAN_AUTOBACKUP.vab';

}

EXIT;

Example 2. Restoring Control File if Persistent Configuration Setting Is Set

If persistent configuration for the control file autobackup format is set to the SBT_TAPE device type, you can restore with the following script:

RUN {

ALLOCATE CHANNEL channel0 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginforOracleRMAN/libOracleRMANPlugin.so';

RESTORE controlfile FROM 'c-4097408439-20200410-00_RMAN_AUTOBACKUP.vab';

}

EXIT;

Example 3. Restoring Control File Without Autobackup File Name

If you do not have the autobackup file name to include in the restore script, you can set RMAN to search for the autobackup file within a certain time period. In this case, you must set the database ID (DBID) before you restore. To learn how to find DBID, see this Oracle article.

Using the example below you can search for the autobackup file that was created yesterday. If such autobackup file is not detected, RMAN will search for autobackup files that were created earlier, up to 30 days ago.

Keep in mind that the example below is applicable only if persistent configuration for the control file autobackup format is set to the SBT_TAPE device type.

RUN {
ALLOCATE CHANNEL channel0 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginforOracleRMAN/libOracleRMANPlugin.so';
RESTORE until time 'sysdate-1' CONTROLFILE FROM AUTOBACKUP maxdays 30;
}
EXIT;

Once the autobackup file is detected, RMAN uses it to restore the control file.