My Oracle Support Banner

RMAN Duplicate Process Skipped a Tablespace (Doc ID 2337856.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.



RMAN duplicate skipped one tablespace.

Cust was using "set until time" to perform a backup-based duplication of a database to a point in time. 

A tablespace that was created during the RMAN backup being used was not copied over as part of the duplicate process.

The is an issue for certain versions as per the following document, however, in this case the expected RMAN-06023 error was not seen. 

   Rman-06023 encountered during duplicate to point in time after datafile was added (Doc ID 782317.1)

In this case the RMAN output log showed the following "skip forever tablespace" message...

set newname for clone datafile 223 to new;
  clone database
  skip forever tablespace "ERASEME" ;  <-------------
executing Memory Script

20:30 RMAN Duplicate Command:
  set until time "to_date('01-12-2017 20:30:00','dd-mm-yyyy hh24:mi:ss')";

21:05 Cust using this backup in which the datafile was added to that tablespace during the backup run
  674640 DB INCR COMPLETED 12/01/17 21:05 12/02/17 01:33 4.46

22:00 Fri Dec 01 22:00:27 2017
  alter tablespace ERASEME add datafile '+DATA_ERS' size 10g autoextend on maxsize 32767m
  Completed: alter tablespace ERASEME add datafile '+DATA_ERS' size 10g autoextend on maxsize 32767m

22:12 Datafile creation time:
  01-12-2017 22:12:32 +DATA_ERS/prd/datafile/eraseme.314.961624827


ASM diskgroup is currently mounted.

Datafiles and Tablespace are currently found to be READ/WRITE and ONLINE. 


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.