1

Topic: Problem at cloning of a DB with the help rman duplicate

Good afternoon!
Recently I faced a problem unusual to me at DB cloning. I launched DB cloning approximately following command:

duplicate target database to newdb
spfile
parameter_value_convert ' olddb ', ' newdb'
set db_recovery_file_dest_size = ' 1g'
set db_recovery_file_dest ='somedg1'
set control_files ='somedg1 ', ' somedg1'
set db_create_online_log_dest_1 ='somedg1'
set db_create_file_dest ='somedg1'
set pga_aggregate_target = ' 1g'
;

In the course of cloning I noted unusual messages from rman:

datafile 11 not processed because file is offline
datafile 12 not processed because file belongs to tablespace with one or more offline immediate datafile (tablespace1)

Further in a script generated rman':

skip forever tablespace "tablespace1";

And in the end, indifferently, rman opened  without one tabular space.
In process  it has been installed that this day in this tabular space the new file has been added and between the moment of adding of a file and recovery time  has not been made any backup copies except archive logs.
There were two questions:
1) whether Normal this behavior rman'? Or there can be it a bug.  on a metalink found nothing.
2) whether It is possible what to redefine that in the image this behavior? For example me arranged more if rman simply quitted with an error that cannot create a file. I do not say already that rman could create quite this file using available information.
For help:
1) Rman at performance duplicate it is connected to target, auxiliary and catalog.
2) the Version of a DB 11.2.0.4 PSU 170718
3) As storage both on a source and on the receiver it is used ASM
4) I realize that it was possible to make a differential backup copy after adding of files, but this variant not absolutely approaches me for some reasons.
5) In a DB-source there is no file or tabular space in the status "OFFLINE"
I will be very grateful if you offer the variants of the possible reasons and the decision of this problem.
If the given information has not enough, I will try to add it operatively.

2

Re: Problem at cloning of a DB with the help rman duplicate

Most simple if the size allows to fulfill DUPLICATE FROM ACTIVE DATABASE

3

Re: Problem at cloning of a DB with the help rman duplicate

Thanks for answers!

wrote:

Hitych;
it is included after all?
It is possible to try to make backup datafile 11;
Or to make
duplicate... until ' sysdate-7 ';
Generally on a bug similar.
Bug 12799744: DUPLICATE TO POINT IN TIME AFTER DATAFILE WAS ADDED FAIL.

it is included.
The variant with  one file does not approach as duplicate is launched by a script and not the manager. I.e. the person who launches does not know anything about the added files. If only to trace appearance of new files in a script, but it will be artful enough script.
Bug to 12799744 mine it is not so similar, there rman just falls at file adding, and at me it persistently recovers the big basis and opens its actually damaged, without a piece of the data.

Ljubomudrov wrote:

Most simple if the size allows to fulfill DUPLICATE FROM ACTIVE DATABASE

This variant too not so approaches, since the basis big enough (> 2) and is strongly loaded at night.