续《使用oracle duplicate技术复制需要恢复的表空间到测试环境(异机)（一）》

[@more@]

datafile 61 not processed because file is offline

datafile 62 not processed because file is offline

datafile 63 not processed because file is offline

datafile 64 not processed because file is offline

datafile 65 not processed because file is offline

starting media recovery

Oracle Error:

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

ORA-01194: file 1 needs more recovery to be consistent

ORA-01110: data file 1: '/u01/oradata/aux/rwsw_system'

released channel: t1

released channel: t2

released channel: t3

RMAN-00571: ===========================================

RMAN-00569:==== ERROR MESSAGE STACK FOLLOWS ===========

RMAN-00571:=================================== =========

RMAN-03002: failure of Duplicate Db command at 11/23/2012 17:52:08

RMAN-03015: error occurred in stored script Memory Script

RMAN-06053: unable to perform media recovery because of missing log

RMAN-06025: no backup of log thread 1 seq 198703 scn 30616330375 found to restore

RMAN-06025: no backup of log thread 1 seq 198702 scn 30615965753 found to restore

RMAN-06025: no backup of log thread 1 seq 198701 scn 30615656494 found to restore

RMAN-06025: no backup of log thread 2 seq 259955 scn 30615566730 found to restore

RMAN-06025: no backup of log thread 1 seq 198700 scn 30615566571 found to restore

RMAN-06025: no backup of log thread 1 seq 198699 scn 30615473628 found to restore

RMAN-06025: no backup of log thread 1 seq 198698 scn 30615356717 found to restore

RMAN-06025: no backup of log thread 2 seq 259954 scn 30615337644 found to restore

RMAN-06025: no backup of log thread 1 seq 198697 scn 30615270920 found to restore

RMAN-06025: no backup of log thread 2 seq 259953 scn 30615178440 found to restore

RMAN-06025: no backup of log thread 1 seq 198696 scn 30615178385 found to restore

RMAN-06025: no backup of log thread 1 seq 198695 scn 30615092870 found to restore

RMAN-06025: no backup of log thread 1 seq 198694 scn 30614989842 found to restore

RMAN-06025: no backup of log thread 2 seq 259952 scn 30614979622 found to restore

RMAN-06025: no backup of log thread 1 seq 198693 scn 30614889220 found to restore

RMAN-06025: no backup of log thread 2 seq 259951 scn 30614844070 found to restore

RMAN-06025: no backup of log thread 1 seq 198692 scn 30614801850 found to restore

RMAN-06025: no backup of log thread 1 seq 198691 scn 30614671283 found to restore

RMAN-06025: no backup of log thread 2 seq 259950 scn 30614644643 found to restore

RMAN-06025: no backup of log thread 1 seq 198690 scn 30614574955 found to restore

RMAN-06025: no backup of log thread 2 seq 259949 scn 30614458361 found to restore

RMAN-06025: no backup of log thread 1 seq 198689 scn 30614435588 found to restore

RMAN-06025: no backup of log thread 1 seq 198688 scn 30614269927 found to restore

RMAN-06025: no backup of log thread 2 seq 259948 scn 30614184614 found to restore

RMAN-06025: no backup of log thread 1 seq 198687 scn 30613855412 found to restore

RMAN-06025: no backup of log thread 2 seq 259947 scn 30613855402 found to restore

RMAN-06025: no backup of log thread 2 seq 259946 scn 30613834101 found to restore

RMAN-06025: no backup of log thread 2 seq 259945 scn 30613761473 found to restore

RMAN-06025: no backup of log thread 1 seq 198686 scn 30613566022 found to restore

RMAN-06025: no backup of log thread 1 seq 198685 scn 30611871698 found to restore

RMAN-06025: no backup of log thread 2 seq 259944 scn 30611871658 found to restore

RMAN-06025: no backup of log thread 2 seq 259943 scn 30611746005 found to restore

RMAN-06025: no backup of log thread 2 seq 259942 scn 30611598124 found to restore

RMAN-06025: no backup of log thread 1 seq 198684 scn 30611460875 found to restore

RMAN-06025: no backup of log thread 2 seq 259941 scn 30611460843 found to restore

RMAN-06025: no backup of log thread 2 seq 259940 scn 30611352521 found to restore

RMAN-06025: no backup of log thread 2 seq 259939 scn 30611235895 found to restore

RMAN-06025: no backup of log thread 1 seq 198683 scn 30610816928 found to restore

RMAN-06025: no backup of log thread 2 seq 259938 scn 30610816446 found to restore

RMAN-06025: no backup of log thread 2 seq 259937 scn 30610547628 found to restore

RMAN-06025: no backup of log thread 2 seq 259936 scn 30610540819 found to restore

RMAN-06025: no backup of log thread 1 seq 198682 scn 30610533953 found to restore

RMAN-06025: no backup of log thread 2 seq 259935 scn 30610532734 found to restore

RMAN-06025: no backup of log thread 2 seq 259934 scn 30610526777 found to restore

RMAN-06025: no backup of log thread 2 seq 259933 scn 30610522878 found to restore

RMAN-06025: no backup of log thread 1 seq 198681 scn 30610519100 found to restore

RMAN-06025: no backup of log thread 2 seq 259932 scn 30610518709 found to restore

RMAN-06025: no backup of log thread 2 seq 259931 scn 30610511098 found to restore

RMAN-06025: no backup of log thread 2 seq 259930 scn 30610503408 found to restore

RMAN-06025: no backup of log thread 1 seq 198680 scn 30610498180 found to restore

RMAN-06025: no backup of log thread 2 seq 259929 scn 30610495740 found to restore

RMAN-06025: no backup of log thread 2 seq 259928 scn 30610488119 found to restore

RMAN-06025: no backup of log thread 2 seq 259927 scn 30610480503 found to restore

RMAN-06025: no backup of log thread 1 seq 198679 scn 30610476127 found to restore

RMAN-06025: no backup of log thread 2 seq 259926 scn 30610473041 found to restore

MAN-06025: no backup of log thread 2 seq 259925 scn 30610465779 found to restor

RMAN>

RMAN>

说明：dupicate复制数据库完成以后，以上的rman报错属于正常现象，因为，并没有复制归档日志到辅助库进行完全恢复，故而报错显示进行介质恢复缺失归档日志。

5. 不完全恢复辅助数据库

在进行duplicate复制数据库的时候，是使用数据库最近的全备份来还原数据库的，最近的全备份生成四个备份片：67nqh0oo_1_1、66nqgpjj_1_1、67nqh0oo_2_1、66nqgpjj_2_1。

外网全备份的时间为每周六凌晨5：30：29分（2012-11-17 5:30:29）开始全备份，数据库的SCN是不断的往前推进的，备份的那一刻SCN 30536982471。因为是进行不完全恢复数据库，因此只需要restore几个归档出来就能够恢复数据库。在进行restore归档日志的时候，报错，报错内容为TSM备份软件需要进行验证。报错内容已经发给TSM维护工程师进行处理。这里我们通过ftp的方式从目标库拷贝归档日志到辅助库。

拷贝哪些归档日志来进行恢复，首先是要确定最近全备份后的第一个归档日志。通过查看数据库视图v$archived_log来确定最近全备份开始之后产生的第一个归档日志的sequence，注意，因为我们的数据库的RAC数据库，每个节点都有一个，先看RAC1实例的归档情况，first_change# 为SCN30536292746，时间为2012-11-17 4:35:29 ，next_change#为SCN30537219173，时间为2012-11-17 8:11:37，completion_time为2012-11-17 8:20:50所对应的归档日志sequence为197807，该归档日志正是最近全备份开始之后产生的第一个归档日志，全备开始时刻的SCN 30536982471，时间为2012-11-17 5:30:29，从SCN与时间来看，sequence为197807的日志文件，在全备份开始之前就已经产生，在全备份之后2012-11-17 8:20:50完成了归档，生成归档日志文件，197807跨越了备份前与备份后的事务，从SCN来看，该SCN正好落在SCN 30536292746与SCN 30537219173之间，因此恢复数据只需要从SCN 30536982471开始，从应用第一个归档日志的部分日志到你所指定的归档日志为止。

RAC1指定(指定误删除数据的time或scn)需要应用的归档日志：

197807

197808

197809

197810

197811

RAC2实例也是同样如此，不再赘述。

RAC2指定(指定误删除数的time或scn)需要应用的归档日志：

2_259344

2_259345

2_259346

2_259347

下面不完全恢复辅助数据库：

SQL> recover database until cancel using backup controlfile;

ORA-00279: change 30536982471 generated at 11/17/2012 05:30:29 needed for

thread 1

ORA-00289: suggestion : /u01/oradata/archivelog/1_197807.dbf

ORA-00280: change 30536982471 for thread 1 is in sequence #197807

Specify log: {=suggested | filename | AUTO | CANCEL}

/u01/oradata/archivelog/1_197807.dbf #####手工输入

ORA-00279: change 30536982471 generated at needed for thread 2

Specify log: {=suggested | filename | AUTO | CANCEL}

/u01/oradata/archivelog/2_259344.dbf ######手工输入

ORA-00279: change 30537219173 generated at 11/17/2012 08:11:37 needed for

thread 1

ORA-00289: suggestion : /u01/oradata/archivelog/1_197808.dbf

ORA-00280: change 30537219173 for thread 1 is in sequence #197808

ORA-00278: log file '/u01/oradata/archivelog/1_197807.dbf' no longer needed for

this recovery

Specify log: {=suggested | filename | AUTO | CANCEL}

AUTO

ORA-00279: change 30537240862 generated at 11/17/2012 08:15:01 needed for

thread 2

ORA-00289: suggestion : /u01/oradata/archivelog/2_259345.dbf

ORA-00280: change 30537240862 for thread 2 is in sequence #259345

ORA-00278: log file '/u01/oradata/archivelog/2_259344.dbf' no longer needed for

this recovery

ORA-00279: change 30537250810 generated at 11/17/2012 08:29:41 needed for

thread 2

ORA-00289: suggestion : /u01/oradata/archivelog/2_259346.dbf

ORA-00280: change 30537250810 for thread 2 is in sequence #259346

ORA-00278: log file '/u01/oradata/archivelog/2_259345.dbf' no longer needed for

this recovery

ORA-00279: change 30537361331 generated at 11/17/2012 09:23:14 needed for

thread 1

ORA-00289: suggestion : /u01/oradata/archivelog/1_197809.dbf

ORA-00280: change 30537361331 for thread 1 is in sequence #197809

ORA-00278: log file '/u01/oradata/archivelog/1_197808.dbf' no longer needed for

this recovery

ORA-00279: change 30537447732 generated at 11/17/2012 09:42:17 needed for

thread 2

ORA-00289: suggestion : /u01/oradata/archivelog/2_259347.dbf

ORA-00280: change 30537447732 for thread 2 is in sequence #259347

ORA-00278: log file '/u01/oradata/archivelog/2_259346.dbf' no longer needed for

this recovery

ORA-00279: change 30537457290 generated at 11/17/2012 09:44:27 needed for

thread 1

ORA-00289: suggestion : /u01/oradata/archivelog/1_197810.dbf

ORA-00280: change 30537457290 for thread 1 is in sequence #197810

ORA-00278: log file '/u01/oradata/archivelog/1_197809.dbf' no longer needed for

this recovery

ORA-00279: change 30537549021 generated at 11/17/2012 10:02:57 needed for

thread 1

ORA-00289: suggestion : /u01/oradata/archivelog/1_197811.dbf

ORA-00280: change 30537549021 for thread 1 is in sequence #197811

ORA-00278: log file '/u01/oradata/archivelog/1_197810.dbf' no longer needed for

this recovery

ORA-00279: change 30537667229 generated at 11/17/2012 10:16:16 needed for

thread 2

ORA-00289: suggestion : /u01/oradata/archivelog/2_259348.dbf

ORA-00280: change 30537667229 for thread 2 is in sequence #259348

ORA-00278: log file '/u01/oradata/archivelog/2_259347.dbf' no longer needed for

this recovery

ORA-00308: cannot open archived log '/u01/oradata/archivelog/2_259348.dbf'

ORA-27037: unable to obtain file status

IBM AIX RISC System/6000 Error: 2: No such file or directory

Additional information: 3

2. 以resetlogs 打开数据库

SQL> alter database open resetlogs;

Database altered.