Rerunning RMAN duplicate (ASM based database)

[poojanathani]

Hi Tim,

When we run a rerun a failed RMAN duplicate, it normally skips past through the files that are already restored.
But in case of ASM datafiles, RMAN attempts to restore the data files again because the files names are generated ones.

Wondering if there's any way to get around this situation ?

Thanks

[Tim...]

Hi.

Don't think there is. Using OMF to generate file names guarantees they are unique, which is why you get this situation. You can manually clean them up before a new run.

Cheers

Tim...

[poojanathani]

Thanks Tim.
Yes, manual cleanup is an option, but I was trying to avoid it.
Mainly because I was hoping if time could be saved by skipping past through the already restored files

But if there isn't any option, can't do much really.

Regards

[Tim...]

Hi.

Never say never, but I don't know of one.

Cheers

Tim...

[poojanathani]

Hi Tim,
Checked the metalink note :
Manual Completion of a Failed RMAN Duplicate [ID 360962.1]

3. Manual Completion of Phase 3:Recovery

$ rman target / auxiliary sys/oracle@<alias>

RMAN> run {
set new name for datafile n to 'X'; ** see Notes below re incrementals
set until scn 1412841;
recover clone database;
alter clone database open resetlogs;
}

But the contents of my failed duplicate log file say -

set newname for clone datafile 1 to new;
set newname for clone datafile 2 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 4 to new;
set newname for clone datafile 5 to new;
.
.
.
.

(I wasn't very comfortable to use "set newname" as it might impact production. Instead used "set newname for clone .." as in the log file)

But it didn't work.

Still trying to find out the alternatives.

Restore/Recovery (of 1TB database) failing at about 99% and having to do all over againt is very time consuming.

Regards,

[Tim...]

Hi.

You said a lot of stuff, but I don't think you've actually asked a question. What do you want to know?

Cheers

Tim...

[poojanathani]

Sorry for that .. Got carried away !
Question remains the same actually - Is there any way to command RMAN to skip past through the already restored files using SET NEWNAME or any other clause ?

Thanks

[Tim...]

Hi.

OK. So you were asking the initial question again. Then I guess I will post my initial answer again.

"Don't think there is. Using OMF to generate file names guarantees they are unique, which is why you get this situation. You can manually clean them up before a new run."

You can raise an SR to see if there is something clever you can do, but I don't think so.

Cheers

Tim...