По умолчанию контрольный файл входит в бэкапсет вместе с файлом 1.

Для того, чтобы восстановить базу с потерянным контрольным файлом из rman, надо при остановленной базе законнектиться rman target /, затем давать последовательно
startup nomount;
restore controlfile;
alter database mount;
restore database;
прописать если были после бэкапа архивные журналы (catalog),
recover database;
alter database open resetlogs;

Кроме того, при настройке rman можно указать autobackup controlfile. Единственная проблема, выяснить, где лежит эта дополнительная копия контрольного файла (это домашнее задание).

Sorry. Действительно, немного наврал. Способ вытаскивания контрольного файла из бэкапсета саппорт никому не дает. В компенсацию даю статью с металинка по 9.

Doc ID: Note:174623.1
Subject: RMAN: Full Recovery When the Recovery Catalog and Controlfile are Lost
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 31-JAN-2002
Last Revision Date: 23-OCT-2002


Performing Full Recovery When the Recovery Catalog and Controlfile are Lost
===========================================================================
Prior to Oracle9i, if you used RMAN and you lost the Recovery Catalog and
the Controlfile, it was requisite that you contact Oracle Support to assist
with the manual datafile extraction from RMAN backups. This process clearly
extended the meantime to recovery and was not guaranteed to work.
Oracle9i introduces a new feature known as Controlfile Autobackup.
This feature, once enabled, automatically backups the controlfile in a
specific format. RMAN can recognize it without access to a recovery
catalog. This format is denoted as '%F.' This particular variable includes
a critical piece of information: the database id.
This is turned on using the CONFIGURE command:
RMAN> configure controlfile autobackup on;
After turning it on, you can change the format of the controlfile autobackup.
However, you must include the variable %F else you will get
an error:
RMAN> configure controlfile autobackup format for
2> device type disk to 'c:\backups\%U';
RMAN-00571:
===========================================================
RMAN-00569:
=============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571:
===========================================================
RMAN-00579: the following error occurred at 01/31/2002 11:57:21
RMAN-03002: failure during compilation of command
RMAN-03013: command type: configure
RMAN-06492: controlfile autobackup format "c:\backups\%U" must specify a "%F"
format specifier
The %F denotion is the key that allows RMAN to recognize the backup piece
without looking it up in a recovery catalog. After you turn this feature on,
RMAN takes a separate backup of the controlfile each and every time you run
a backup command in RMAN. Prior to this, the controlfile was only backed up
automatically if the system tablespace was backed up.
The output of a database backup, for instance, would return the following
log output:
RMAN> backup database;
Starting backup at 31-JAN-02
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\ORADATA\PROD\SYSTEM01.DBF
input datafile fno=00002 name=C:\ORACLE\ORADATA\PROD\UNDOTBS01.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\PROD\EXAMPLE01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\PROD\INDX01.DBF
input datafile fno=00008 name=C:\ORACLE\ORADATA\PROD\USERS01.DBF
input datafile fno=00003 name=C:\ORACLE\ORADATA\PROD\CWMLITE01.DBF input datafile fno=00004 name=C:\ORACLE\ORADATA\PROD\DRSYS01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\PROD\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 31-JAN-02
channel ORA_DISK_1: finished piece 1 at 31-JAN-02
piece handle=C:\BACKUPS\01DFKAIH_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:56
Finished backup at 31-JAN-02
Starting Control File Autobackup at 31-JAN-02
piece handle=C:\BACKUPS\C-4159396170-20020131-00 comment=NONE
Finished Control File Autobackup at 31-JAN-02

Note: The controlfile backup takes place at the end of a backup, making it
useful to extract the backuppieces taken during the same backup command.
Also, you see that the second string of numbers in the name of the backup
piece is the dbid; in this case, 4159396170. Then, if the current database
controlfile is lost along with the database, and you do not have a Recovery
Catalog or it is unavailable, this controlfile autobackup can be used to restore a
copy of the controlfile. The controlfile can then be mounted and used to restore
the datafiles. To perform a full recovery using controlfile autobackups:

1. Create a new init.ora file for your target instance (if you do not have
a backup of it).
2. Startup nomount your new instance.
3. Start RMAN, but do not issue any connect statements
4. At the rman prompt, you will need to set the dbid. If you do not know the
dbid, you can get it from the name of the controlfile autobackup.
RMAN> set dbid=4159396170;
5. After setting the dbid, connect to the target instance that has been
started in nomount mode:
RMAN> connect target /
6. If your backup was to disk and you specified a non-default location for
the controlfile autobackup, move the file to ORACLE_HOME/dbs on unix and
ORACLE_HOME/database on Windows. This is where RMAN knows to look for
the file. If you did not change the controlfile autobackup location, this
directory is where the backups will be placed.
If you backed up to tape, you will need to use a run block to specify the
channel and device to restore from. Because the database is not mounted,
you will not be able to configure default devices or channels.
RMAN> run { allocate channel c_1 type 'sbt_tape'
parms "ENV=(NB_ORA_SERV=rm-wgt)";
restore controlfile from autobackup;}
7. Restore the controlfile:
RMAN> restore controlfile from autobackup;
8. Mount the database from the restored controlfile:
RMAN> alter database mount;
9. Restore datafiles:
RMAN> restore database;
10. After restoring the files, you can perform a recovery. Because we have
lost the online redo logfiles, and we are using a backup controlfile,
you will need to set an 'until time' clause to specify when to end
recovery and open the database:
RMAN> set until time=<time stamp>;
RMAN> recover database;
RMAN> alter database open resetlogs;
.