This content has been marked as final. Show 15 replies
I don't have a document for exactly what you ask. However back in August somebody wanted to restore to a different server with different structure NOCATALOG.
This I have step by step :
I also have active duplicate with different structure :
Maybe these will work for you.
Hi Hermant -
[oracle@mynewdb]$ ls -ltr /u01/app/oracle/fast_recovery_area/mynewdb/backupset/2013_01_29/
-rw-r----- 1 oracle oinstall 24248320 Jan 29 15:03 o1_mf_nnnd1_mynewdb_INC_LEVEL_0_8jhkz05w_.bkp
-rw-r----- 1 oracle oinstall 24787968 Jan 29 15:03 o1_mf_annnn_mynewdb_INC_LEVEL_0_8jhlbhfb_.bkp
***--> Below I am connected to the target (source DB, not mynewdb), catalog, and auxiliary (mynewdb) <- please note that while I can connect to mynewdb as the target, it lacks a controlfile so there is little I can do with it....
RMAN> CATALOG START WITH '/u01/app/oracle/fast_recovery_area/mynewdb/backupset/2013_01_29/';
searching for all files that match the pattern /u01/app/oracle/fast_recovery_area/mynewdb/backupset/2013_01_29/
no files found to be unknown to the database
I believe CATALOG is failing to find new files as my rman target is not the new DB, but the source DB
I feel like the problem is that I am trying to do a new RMAN DUPLICATE - as such, I do not have a control file yet for the duplicate database (DUPLICATE itself will restore the control file, but only if its aware of where the backup pieces are, which requires me to CATALOG them on the new server, but I cannot CATALOG without a controlfile....)
Note that I have currently abandoned using DUPLICATE and instead I am just going to use the usual RMAN commands to restore the controlfile, after which I believe I will be able to CATALOG and restore the DB as whole, I just had my mind set on using DUPLICATE (for the first time) and figured I could do it in this situation but it looks like unless the backup locations are identical in the source and auxiliary, duplicate is not supported...
Edited by: ngilbert on Jan 30, 2013 8:52 AM
Edited by: ngilbert on Jan 30, 2013 8:57 AM
Hi Mmseberg - thanks for the info - it looks like for a normal (not active) DUPLICATE I will need the backup files in the same location as the source. As I note from your blog post, you use the same method I am using now (not DUPLICATE, just usual RMAN restore controlfile, recatalog, restore).
Very helpful post on active duplication, however, I will read more on this topic.
Sure enough, once I restored the controlfile from the backup piece and connected with the mynewdb as the target:
RMAN> CATALOG RECOVERY AREA;
Starting implicit crosscheck backup at 30-JAN-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
Crosschecked 39 objects
Finished implicit crosscheck backup at 30-JAN-13
Starting implicit crosscheck copy at 30-JAN-13
using channel ORA_DISK_1
Finished implicit crosscheck copy at 30-JAN-13
searching for all files in the recovery area
List of Cataloged Files
File Name: /u01/app/oracle/fast_recovery_area/mynewdb/backupset/2013_01_25/o1_mf_nnnd0_mynewdb_FULL_LEVE_0_8j5gybn8_.bkp
File Name: /u01/app/oracle/fast_recovery_area/mynewdb/backupset/2013_01_25/o1_mf_annnn_mynewdb_FULL_LEVE_0_8j5jmm4c_.bkp
File Name: /u01/app/oracle/fast_recovery_area/mynewdb/backupset/2013_01_25/o1_mf_annnn_BACKUP_mynewdb_CS_0_8j5m51dh_.bkp
So I guess the lesson learned for me is that a non-active DUPLICATE will not work unless backup pieces are in an identical location on the source and auxiliary... At least that's what it appears
Can you try with "SET DBID" and see what happens:
rman target sys/pw@source_db CATALOG cat/pw@recovery_catalog auxiliary / (I am on the auxiliary DB box) Recovery Manager: Release 126.96.36.199.0 - Production on Tue Jan 29 15:56:41 2013 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: source_db(DBID=543581301) connected to recovery catalog database connected to auxiliary database: mynewdb (not mounted) RMAN> set DBID=543581301; RMAN> Catalog start with /u01/app/oracle/fast_recovery_area/mynewdb/backupset/2013_01_25/
Ok, so the conventional RMAN restore failed (I'm an amateur, for some reason controlfile was restoring to the wrong location in spite of OMF and RESOTRE DATABASE was only restoring the incremental level 0 from a week ago in spite of the fact that all subsequent level 1s and archive logs are cataloged and were copied to target server) so I'm retrying DUPLICATE using the BACKUP LOCATION available in 11g.
Sorry to reopen, but I'm now getting this error:
[oracle@telmasterdb mynewdb]$ rman
Recovery Manager: Release 188.8.131.52.0 - Production on Wed Jan 30 12:55:29 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN> connect auxiliary /
connected to auxiliary database: mynewdb(not mounted)
RMAN> connect catalog rmancatalog/password@RC
connected to recovery catalog database
RMAN> DUPLICATE DATABASE TO mynewdb
3> BACKUP LOCATION '/u01/app/oracle/fast_recovery_area/mynewdb'
Starting Duplicate Db at 30-JAN-13
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of Duplicate Db command at 01/30/2013 12:56:23
RMAN-05501: aborting duplication of target database
RMAN-05543: DUPLICATE without TARGET connection requires that DATABASE is specified
Database is clearly specified in the command (DUPLICATE DATABASE TO mynewdb) so is this the right error?
I should probably read every detail of the thread before I post this, but when I do a similar thing ( duplicate for standby ) my connect is :
My notes for that are here :
rman target sys/password@PRIMARY auxiliary /
I know its not the same thing, but I'm thinking only the duplicate command would be different.