RMAN-06023: no backup or copy of datafile 6 found to restore

现场人员报告说误删除了用户（drop user），按照操作文档作RMAN的不完全恢复，但是报错，错误信息显示：
RMAN-03002: failure during compilation of command
RMAN-03013: command type: restore
RMAN-03002: failure during compilation of command
RMAN-03013: command type: IRESTORE
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore

在restore database的时候报没有可用的数据文件备份？于是作list backup，检查结果，发现居然没有真的没有显示可用的0级备份。

先说明一下该客户使用的备份策略：
at 5:00 /every:Friday    cmd /c E:\oracle\oradata.bak\RMAN\b_db_inc0.bat
at 5:00 /every:Saturday cmd /c E:\oracle\oradata.bak\RMAN\b_db_inc2.bat
at 5:00 /every:Sunday    cmd /c E:\oracle\oradata.bak\RMAN\b_db_inc2.bat
at 5:00 /every:Monday    cmd /c E:\oracle\oradata.bak\RMAN\b_db_inc2.bat
at 5:00 /every:Tuesday   cmd /c E:\oracle\oradata.bak\RMAN\b_db_inc1.bat
at 5:00 /every:Wednesday cmd /c E:\oracle\oradata.bak\RMAN\b_db_inc2.bat
at 5:00 /every:Thursday cmd /c E:\oracle\oradata.bak\RMAN\b_db_inc2.bat
at 6:00 /every:Friday cmd /c E:\oracle\oradata.bak\RMAN\b_del_archive.bat

每周五临晨5点作0级备份，周六至周一作2级备份，周二作1级备份，周三、周四作2级备份。

查看备份路径中生成的文件：
2004-12-31 05:04        2,147,475,968 DB0_QFIIDB_159_1_546325203
2004-12-31 05:08        2,147,475,968 DB0_QFIIDB_159_2_546325203
2004-12-31 05:09          425,230,848 DB0_QFIIDB_159_3_546325203
2005-01-01 05:04          149,479,936 DB2_QFIIDB_160_1_546411603
2005-01-02 05:04          179,380,736 DB2_QFIIDB_161_1_546498003
2005-01-03 05:04          179,945,984 DB2_QFIIDB_162_1_546584403
2005-01-04 05:04          298,500,608 DB1_QFIIDB_163_1_546670803
2005-01-05 05:04          281,788,928 DB2_QFIIDB_164_1_546757203
2005-01-06 05:04          116,072,960 DB2_QFIIDB_165_1_546843603
2005-01-08 05:04          300,474,880 DB2_QFIIDB_167_1_547016403
2005-01-09 05:04            3,596,800 DB2_QFIIDB_168_1_547102803
2005-01-10 05:04            3,662,336 DB2_QFIIDB_169_1_547189205
2005-01-11 05:04          519,537,152 DB1_QFIIDB_170_1_547275603
2005-01-12 05:04          112,280,064 DB2_QFIIDB_171_1_547362003
2005-01-13 05:04           94,863,872 DB2_QFIIDB_172_1_547448404
2005-01-15 05:04          199,836,160 DB2_QFIIDB_174_1_547621203
2005-01-16 05:04           72,442,368 DB2_QFIIDB_175_1_547707603
2005-01-17 05:04           10,600,960 DB2_QFIIDB_176_1_547794003

可以看到2004年12月31日确实作了0级备份，但是2005年1月7日和1月14日的0级备份却都没有生成，查看RMAN备份的log文件发现这两天的0级备份都报告了“磁盘空间不足”的错误，也就是空闲的磁盘空间不足够作一次0级备份，所以这两天的备份全部没有成功。而恰巧的是这个项目中并没有使用catalog，而是只使用了数据库的控制文件来存储备份信息的。而数据库的control_file_record_keep_time是默认的7天，所以很明显控制文件中的备份信息已经超过了记录的保存期限而被后续的备份信息覆盖了。

问题于是就简化为如果控制文件中不包含可用的备份信息（甚或是控制文件完全损坏），那么如何恢复RMAN备份的数据库？
这就需要使用Oracle在线文档中并没有介绍的dbms_backup_restore包。
关于该包的安装和介绍以及一些使用方法可以参看
Fenng
写的
DBA工作备忘录之三:rman备份,未使用catalog,控制文件丢失的解决办法
一文。

本文则是一次完整地在真实环境中的恢复实例，并且使用了Fenng那篇文章中没有提到的一些存储过程。

1．关闭数据库
SQL> shutdown immediate;

2．启动数据库到nomount状态
SQL> startup nomount;
3． restore 0级备份文件
DECLARE
devtype varchar2(256);
done boolean;
BEGIN
devtype:=sys.dbms_backup_restore.deviceAllocate (type=>'',ident=>'t1');
sys.dbms_backup_restore.restoreSetDatafile;
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>01,toname=>'E:\ORACLE\ORADATA\QFIIDB\SYSTEM01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>02,toname=>'E:\ORACLE\ORADATA\QFIIDB\RBS01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>03,toname=>'E:\ORACLE\ORADATA\QFIIDB\USERS01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>04,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>05,toname=>'E:\ORACLE\ORADATA\QFIIDB\TOOLS01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>06,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>07,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>08,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS01.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>09,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS02.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>10,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS02.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>11,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS02.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>12,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS02.DBF');
sys.dbms_backup_restore.restoreDatafileTo(dfnumber=>13,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS03.DBF');
sys.dbms_backup_restore.restoreBackupPiece(done=>done,handle=>'E:\ORACLE\ORADATA.BAK\DB0_QFIIDB_159_1_546325203', params=>null);
sys.dbms_backup_restore.restoreBackupPiece(done=>done,handle=>'E:\ORACLE\ORADATA.BAK\DB0_QFIIDB_159_2_546325203', params=>null);
sys.dbms_backup_restore.restoreBackupPiece(done=>done,handle=>'E:\ORACLE\ORADATA.BAK\DB0_QFIIDB_159_3_546325203', params=>null);
sys.dbms_backup_restore.deviceDeallocate;
END;
/

4． restore 1级备份文件
DECLARE
devtype varchar2(256);
done boolean;
BEGIN
devtype:=sys.dbms_backup_restore.deviceAllocate (type=>'',ident=>'t1');
sys.dbms_backup_restore.applySetDatafile;
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>01,toname=>'E:\ORACLE\ORADATA\QFIIDB\SYSTEM01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>02,toname=>'E:\ORACLE\ORADATA\QFIIDB\RBS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>03,toname=>'E:\ORACLE\ORADATA\QFIIDB\USERS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>04,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>05,toname=>'E:\ORACLE\ORADATA\QFIIDB\TOOLS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>06,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>07,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>08,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>09,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>10,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>11,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>12,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>13,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS03.DBF');
sys.dbms_backup_restore.applyBackupPiece(done=>done,handle=>'E:\ORACLE\ORADATA.BAK\DB1_QFIIDB_170_1_547275603', params=>null);
sys.dbms_backup_restore.deviceDeallocate;
END;
/

5． restore 第一份2级备份文件
DECLARE
devtype varchar2(256);
done boolean;
BEGIN
devtype:=sys.dbms_backup_restore.deviceAllocate (type=>'',ident=>'t1');
sys.dbms_backup_restore.applySetDatafile;
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>01,toname=>'E:\ORACLE\ORADATA\QFIIDB\SYSTEM01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>02,toname=>'E:\ORACLE\ORADATA\QFIIDB\RBS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>03,toname=>'E:\ORACLE\ORADATA\QFIIDB\USERS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>04,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>05,toname=>'E:\ORACLE\ORADATA\QFIIDB\TOOLS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>06,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>07,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>08,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>09,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>10,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>11,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>12,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>13,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS03.DBF');
sys.dbms_backup_restore.applyBackupPiece(done=>done,handle=>'E:\ORACLE\ORADATA.BAK\DB2_QFIIDB_171_1_547362003', params=>null);
sys.dbms_backup_restore.deviceDeallocate;
END;
/

6． restore 第二份2级备份文件
DECLARE
devtype varchar2(256);
done boolean;
BEGIN
devtype:=sys.dbms_backup_restore.deviceAllocate (type=>'',ident=>'t1');
sys.dbms_backup_restore.applySetDatafile;
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>01,toname=>'E:\ORACLE\ORADATA\QFIIDB\SYSTEM01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>02,toname=>'E:\ORACLE\ORADATA\QFIIDB\RBS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>03,toname=>'E:\ORACLE\ORADATA\QFIIDB\USERS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>04,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>05,toname=>'E:\ORACLE\ORADATA\QFIIDB\TOOLS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>06,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>07,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>08,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS01.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>09,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>10,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_INX_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>11,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>12,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_HIS_IND_TS02.DBF');
sys.dbms_backup_restore.applyDatafileTo(dfnumber=>13,toname=>'E:\ORACLE\ORADATA\QFIIDB\STK_TS03.DBF');
sys.dbms_backup_restore.applyBackupPiece(done=>done,handle=>'E:\ORACLE\ORADATA.BAK\DB2_QFIIDB_172_1_547448404', params=>null);
sys.dbms_backup_restore.deviceDeallocate;
END;
/

7． mount数据库
SQL> alter database mount;

8．恢复数据库到drop user前的某一时间点
SQL> >recover database until time '2005-1-14 16:00:00';

9．启动数据库
SQL> alter database open resetlogs;

10．             立刻作一次full备份

情况描述
客户报告数据库故障，新来的系统管理员误操作。删掉了一些文件。具体情况是：删掉了所有重要数据文件、所有控制文件。数据库原来是归档模式，用rman备份数据，而rman 使用控制文件。幸运的是，最后一次 rman full 备份是包括了控制文件在内。系统没有设定自动备份控制文件。现在状况是数据库无法启动。
不用说，客户的备份方案不够完善，但是这时候再去说这些话责备用户有事后诸葛亮之嫌，"用户是上帝，不要去得罪他"。还有，客户有Full备份（虽然不是自动备份控制文件，这样无法用常规的恢复步骤来进行恢复）。这对我们来说是个绝对的好消息。
下面我们通过一次模拟操作来演示这个问题的解决办法。
背景知识
在Oracle 816 以后的版本中,Oracle提供了一个包:DBMS_BACKUP_RESTORE.DBMS_BACKUP_RESTORE 包是由dbmsbkrs.sql 和 prvtbkrs.plb 这两个脚本创建的.catproc.sql 脚本运行后会调用这两个包.所以是每个数据库都有的这个包是Oracle服务器和操作系统之间IO操作的接口.由恢复管理器直接调用。而且据说这两个脚本的功能是内建到Oracle的一些库文件中的.
由此可见，我们可以在数据库 nomount 情况下调用这些package ,来达到我们的恢复目的。在dbmsbkrs.sql 和prvtbkrs.plb 这两个脚本中有详细的说明文档，出于篇幅问题，就不一一加以翻译了，但在下面会直接引用一些原文说明。
关键的内容有：
FUNCTION 　deviceAllocate(
　　　　　　 type IN varchar2 default NULL
　　　　　　,name IN varchar2 default NULL
　　　　　　,ident IN varchar2 default NULL
　　　　　　,noio IN boolean default FALSE
　　　　　　,params IN varchar2 default NULL )
RETURN varchar2;
-- Describe the device to be used for sequential I/O. For device types where
-- only one process at a time can use a device, this call allocates a device
-- for exclusive use by this session. The device remains allocated until
-- deviceDeallocate is called or session termination. The device can be used
-- both for creating and restoring backups.
--
-- Specifying a device allocates a context that exists until the session
-- terminates or deviceDeallocate is called. Only one device can be specified
-- at a time for a particular session. Thus deviceDeallocate must be called
-- before a different device can be specified. This is not a limitation since
-- a session can only read or write one backup at a time.
--
-- The other major effect of allocating a device is to specify the name space
-- for the backup handles (file names). The handle for a sequential file does
-- not necessarily define the type of device used to write the file. Thus it
-- is necessary to specify the device type in order to interpret the file
-- handle. The NULL device type is defined for all systems. It is the file
-- system supplied by the operating system. The sequential file handles are
-- thus normal file names.
--
-- A device can be specified either by name or by type.
-- If the type is specified but not the name, the system picks an
-- available device of that type.
-- If the name is specified but not the type, the type is determined
-- from the device.
-- If neither the type or the name is given, the backups are files in
-- the operating system file system.
-- Note that some types of devices, optical disks for example, can be shared
-- by many processes, and thus do not really require allocation of the device
-- itself. However we do need to allocate the context for accessing the
-- device, and we do need to know the device type for proper interpretation
-- of the file handle. Thus it is always necessary to make the device
-- allocation call before making most other calls in this package.
--
-- Input parameters:
-- type
-- If specified, this gives the type of device to use for sequential
-- I/O. The allowed types are port specific. For example a port may
-- support the type "TAPE" which is implemented via the Oracle tape
-- API. If no type is specified, it may be implied by specifying a
-- particular device name to allocate. The type should be allowed to
-- default to NULL if operating system files are to be used.
--
-- name
-- If specified, this names a particular piece of hardware to use for
-- accessing sequential files. If not specified, any available
-- device of the correct type will be allocated. If the device cannot
-- be shared, it is allocated to this session for exclusive use.
-- The name should be allowed to default to NULL if operating system
-- files are to be used.
--
-- ident
-- This is the users identifier that he uses to name this device. It
-- is only used to report the status of this session via
-- dbms_application_info. This value will be placed in the CLIENT_INFO
-- column of the V$SESSION table, in the row corresponding to the
-- session in which the device was allocated. This value can also
-- be queried with the dbms_application_info.read_client_info procedure.
--
-- noio
-- If TRUE, the device will not be used for doing any I/O. This allows
-- the specification of a device type for deleting sequential files
-- without actually allocating a piece of hardware. An allocation for
-- noio can also be used for issuing device commands. Note that some
-- commands may actually require a physical device and thus will get
-- an error if the allocate was done with noio set to TRUE.
--
-- params
-- This string is simply passed to the device allocate OSD. It is
-- completely port and device specific.
--
-- Returns:
-- It returns a valid device type. This is the type that should be
-- allocated to access the same sequential files at a later date. Note
-- that this might not be exactly the same value as the input string.
-- The allocate OSD may do some translation of the type passed in. The
-- return value is NULL when using operating system files.
PROCEDURE restoreControlfileTo(cfname IN varchar2);
-- This copies the controlfile from the backup set to an operating system
-- file. If the database is mounted, the name must NOT match any of the
-- current controlfiles.
--
-- Input parameters:
-- cfname
-- Name of file to create or overwrite with the controlfile from the
-- backup set.
PROCEDURE restoreDataFileTo( dfnumber IN binary_integer
,toname IN varchar2 default NULL);
--
-- restoreDataFileTo creates the output file from a complete backup in the
-- backup set.
如果您有兴趣可以去阅读一下这两个文件的注释说明．
解决过程
首先，用控制文件作数据库系统的全备份：
C:WUTemp>rman target /
Recovery Manager: Release 9.2.0.1.0 - Production.
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: DEMO (DBID=3272375326)
RMAN> run {
2> allocate channel C1 type disk;
3> backup full tag 'FullBackup' format 'd:\KDE\%d_%u_%s_%p.dbf' database include current controlfile;
4> sql ' alter system archive log current';
5> release channel C1;
6> }
using target database controlfile instead of recovery catalog
allocated channel: C1
channel C1: sid=15 devtype=DISK
Starting backup at 18-JUL-04
channel C1: starting full datafile backupset
channel C1: specifying datafile(s) in backupset
including current SPFILE in backupset
including current controlfile in backupset
input datafile fno=00001 name=D:\ORACLE\ORADATA\DEMO\SYSTEM01.DBF
input datafile fno=00002 name=D:\ORACLE\ORADATA\DEMO\UNDOTBS01.DBF
input datafile fno=00004 name=D:\ORACLE\ORADATA\DEMO\EXAMPLE01.DBF
input datafile fno=00009 name=D:\ORACLE\ORADATA\DEMO\XDB01.DBF
input datafile fno=00005 name=D:\ORACLE\ORADATA\DEMO\INDX01.DBF
input datafile fno=00008 name=D:\ORACLE\ORADATA\DEMO\USERS01.DBF
input datafile fno=00003 name=D:\ORACLE\ORADATA\DEMO\DRSYS01.DBF
input datafile fno=00006 name=D:\ORACLE\ORADATA\DEMO\ODM01.DBF
input datafile fno=00007 name=D:\ORACLE\ORADATA\DEMO\TOOLS01.DBF
channel C1: starting piece 1 at 18-JUL-04
channel C1: finished piece 1 at 18-JUL-04
piece handle=D:\KDE\DEMO_01FR79OT_1_1.DBF comment=NONE
channel C1: backup set complete, elapsed time: 00:01:17
Finished backup at 18-JUL-04
sql statement: alter system archive log current
released channel: C1
如上所示，我们做了一次数据库的Full备份．备份片中包括控制文件．注意上面输出内容的黑体部分．我们在后面的恢复操作中会用到．
模拟错误，关掉实例，删掉所有的控制文件和所有的.DBF文件。然后starup会看到如下的出错信息:
SQL> startup
ORACLE instance started.
Total System Global Area 152115804 bytes
Fixed Size 453212 bytes
Variable Size 100663296 bytes
Database Buffers 50331648 bytes
Redo Buffers 667648 bytes
ORA-00205: error in identifying controlfile, check alert log for more info
查看alert Log,应该是系统找不到控制文件．现在情形和客户问题一致．不过在继续讲述之前，我们还需要介绍一点背景知识．
我们首先尝试恢复控制文件：
SQL>startup force nomount;
SQL> DECLARE
2 devtype varchar2(256);
3 done boolean;
4 BEGIN
5 devtype:=sys.dbms_backup_restore.deviceAllocate(type=>'',ident=>'T1');
6 sys.dbms_backup_restore.restoreSetDatafile;
7 sys.dbms_backup_restore.restoreControlfileTo(cfname=>'d:\oracle\Control01.ctl');
8 sys.dbms_backup_restore.restoreBackupPiece(done=>done,handle=>'D:\KDE\DEMO_01FR79OT_1_1.DBF', params=>null);
9 sys.dbms_backup_restore.deviceDeallocate;
10 END;
11 /
PL/SQL procedure successfully completed.
OK,控制文件恢复完成．对以上内容的解释:

RMAN-06023: no backup or copy of datafile 6 found to restore

RMAN-06023: no backup or copy of datafile 6 found to restore

你可能感兴趣的:(Oracle,Troubleshooting)