Tuesday, July 12, 2011

RMAN-12009 & RMAN-12008

I have taken a rman backup of system related tablespaces in to the disk. when i try to restore in to the new server i am got the below issues.
I tired to do the catalog start with command, but it throw me an error


RMAN> CATALOG START WITH '/mnt1/oracle/' NOPROMPT;

using target database control file instead of recovery catalog
searching for all files that match the pattern /mnt1/oracle/
no files found to be unknown to the database

RMAN> catalog backuppiece '/mnt1/oracle/smplive_SMPLIV_gtmh8n3v_1565_20110712';

catalog backuppiece '/mnt1/oracle/smplive_SMPLIV_gumh8n3v_1566_20110712';
cataloged backuppiece
backup piece handle=/mnt1/oracle/smplive_SMPLIV_gtmh8n3v_1565_20110712 recid=730 stamp=756314610

RMAN>
cataloged backuppiece
backup piece handle=/mnt1/oracle/smplive_SMPLIV_gumh8n3v_1566_20110712 recid=731 stamp=756314610




RMAN> run
2> {
3> allocate channel ch1 type disk;
4> restore tablespace  SYSTEM;
5> }

allocated channel: ch1
channel ch1: sid=1110 instance=SMPLIVL1 devtype=DISK

Starting restore at 12-JUL-11

released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/12/2011 15:13:55
RMAN-12009: command aborted because some backup pieces could not be located
RMAN-12008: could not locate backup piece /mnt1/oracle/Bhuvan_h0mh8n40_1568_20110712

RMAN> exit

SOLUTION: PLEASE CHANGE THE CLUSTER_DATABASE= FALSE; then you can start the restore. it will work. Once the restore completed then you can change the parameter to TRUE.

1 comment:

  1. could it be that your backups are on nfs?
    maybe just add nolock to nfs mount options.

    ReplyDelete