【RMAN】Oracle_rman中skip引發的血案

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

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

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

RMAN-03002: failure of switch command at 09/28/2014 07:59:23

RMAN-20230: datafile copy not found in the repository

RMAN-06015: error while looking up datafile copy name: /oracle/FIRSOUL/datafile/test2.dbf

RMAN> run

2> {

3> allocate channel C1 type disk maxpiecesize 2G format "/oracle/backup/0/%d_%Y_%M_%D_%U.BAK";

4> allocate channel C2 type disk maxpiecesize 2G format "/oracle/backup/0/%d_%Y_%M_%D_%U.BAK";

5> sql 'alter system archive log current';

6> backup incremental level=0 database plus archivelog delete input;

backup current controlfile format '/oracle/backup/0/ctl_%d_%Y_%M_%D.bak'; 

 backup  spfile format '/oracle/backup/0/spfile_%d_%Y_%M_%D.bak';

7> 8> 9>  delete noprompt obsolete REDUNDANCY=2 device type disk;

10>  crosscheck backup;

11>  release channel C1;

12>  release channel C2;

13> }

file 6 is excluded from whole database backup

file 8 is excluded from whole database backup

Starting recover at 28-SEP-14

using channel ORA_DISK_1

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

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

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

RMAN-03002: failure of recover command at 09/28/2014 13:37:57

RMAN-06094: datafile 6 must be restored

sys@FIRSOUL> select * from v$tablespace;

       TS# NAME        INC BIG FLA ENC

---------- ----------- --- --- --- ---

         0 SYSTEM      YES NO  YES

         1 SYSAUX      YES NO  YES

         2 UNDOTBS1    YES NO  YES

         3 TEMP        NO  NO  YES

         4 USERS       YES NO  YES

         5 TEST1       YES NO  YES

         6 TEST2       NO  NO  YES

         7 TEST3       YES NO  YES

         8 TEST4       NO  NO  YES

         9 TEST5       YES NO  YES

CONFIGURE EXCLUDE FOR TABLESPACE 'TEST4';

CONFIGURE EXCLUDE FOR TABLESPACE 'TEST4' clear;

RMAN> run

2> {

3> set newname for datafile 1 to '/oracle/FIRSOUL/datafile/system01.dbf';

4> set newname for datafile 2 to '/oracle/FIRSOUL/datafile/sysaux01.dbf';

5> set newname for datafile 3 to '/oracle/FIRSOUL/datafile/undotbs1.dbf';

6> set newname for datafile 4 to '/oracle/FIRSOUL/datafile/users.dbf';

7> set newname for datafile 5 to '/oracle/FIRSOUL/datafile/test1.dbf';

8> set newname for datafile 7 to '/oracle/FIRSOUL/datafile/test3.dbf';

9> set newname for datafile 9 to '/oracle/FIRSOUL/datafile/test5.dbf';

10> restore database skip tablespace test2,test4;

11> switch datafile all;

12> recover database skip tablespace test2,test4;

13> }

Use an optional SKIPTABLESPACE 'tablespace_name' argument to

avoid restoring specified tablespaces, which is useful when you want to

avoid restoring tablespaces containing temporary data.

If you specify SKIP FOREVER TABLESPACE, then RMAN specifies the DROP

option of ALTER DATABASE DATAFILE ... OFFLINE when taking the

datafiles that belong to the tablespace offline before the restore. The DROP

option indicates that RMAN does not intend to recover these files and

intends to drop their tablespaces from the database after the database is

opened again. In other words, FOREVER indicates that RMAN never

intends to do anything with the skipped tablespaces again.