Hi, I'm on Oracle 10g with Solaris 10

I had successfully cloned a prod database to a new server but the underlying SAN had to be reconfigured, so I am trying to clone it down again.

To backup, I am using:

backup database tag='SBX_PROD_DBNAME' format '/archive/stage/PROD_DBNAME/%U';
backup archivelog all format '/archive/stage/PROD_DBNAME/%U';
sql "alter system archive log current";
backup current controlfile format '/archive/stage/PROD_DBNAME/%U';

Then to clone:
set until time ...
duplicate taget database to "SBX"
logfile etc....


Nothing too complex, and we have successfully run it before. I look at the backup log and it ran successfully with all of the same information as the one that worked previously.

However, when I run the clone script I recieve:
ORA-19870 error reading backup piece /archive/flash_recovery_area <-- This should be /archive/stage
ORA-19505 failed to identify (same as above, wrong location)

The strange thing is, the only thing I have changed in the scripts is the set until time. Everything else is the same as what ran successfully before as far as I can tell.

If anyone could tell me what I should be looking at, I would really appreciate it. I apologize if it's something obvious but I am stumped/at a loss. A direction would really help me out because right now I have none.

Thanks!
Va.

Could be please post the restoration script which you have used for restoration ?

Please try cataloging the backup peice manually and try from there ?
The error message shows it is not able to recognize the backup peice.

Rgrds,
VNK

Hi Va,

>> ORA-19505 failed to identify

Did you run an RMAN crosscheck?

See here: http://www.dba-oracle.com/bk_ora_19505_tips.htm

***************************************
>> Then to clone:

If you want to clone a database with RMAN, see here:

http://www.dba-oracle.com/t_rman_clone+copy_database.htm

Thanks!

I'll try the crosscheck. I'm not connecting to the catalog so I wouldn't need to update there but maybe crosscheck so the control file is aware.

VNK, I typed up a shortened version of my duplicate script but here is more:

connect target username@sid
connect auxiliary /

CONFIGURE CHANNEL DEVICE TYPE disk CLEAR;
CONFIGURE DEFAULT DEVICE TYPE TO disk;
CONFIGURE DEVICE TYPE disk PARALLELISM 3;

@set decryption identified by "password";

run {
set until time "to_date('05-mar-2010 09:30:00' , 'dd-mon-yyyy hh24:mi:ss');
duplicate target database to "SBX'\:
logfile
group 1 ...
group 2 ...
group 3 ...
}

All of this worked so, I am thinking what Mr. Burleson said about the crosscheck makes sense.

Thanks a bunch, appreciate the replies!
Va. )

Ok, I did a crosscheck backup and it showed the backup I was targeting as available. Then I tried doing a crosscheck backup of each individual piece, controlfile, datafiles, spfile and all showed available in the /archive/stage/dbname

However, it still keeps looking for my backup in the flash recovery area.

Also, another person is doing the exact same backup and recovery with copies of the scripts that only have slight modifications for the different prod db and clone name and is using a subdirectory of the /archive/stage so it's definitely not permissions.

It would be nice if I could specify the backup tag but I don't see a way to do this with a duplicate?

I was at a loss before but now even more, any ideas of what I might look at next?

Thanks for the time and knowledge!
Va.

Hi Va,

>> I was at a loss before but now even more, any ideas of what I might look at next?

A production recovery is no time to be learning RMAN!

Recoveries are tricky, and it's easy to corrupt data if you do not have experience . . .

You need to open an emergency (sev1) SR on MIS:

http://metalink.oracle.com

If you want to clone a database with RMAN, see here:

http://www.dba-oracle.com/t_rman_clone+copy_database.htm

Good thing I am not learning RMAN while trying to recover a production database. I am cloning production down to a sandbox using the duplicate function. I appreciate the suggestions to this point, sorry to bother.

Thanks,
Va.