We tried to duplicate a database from a RAC ( raw datafiles + non clustered archivelogs ) to a single node system using the following command :
run {
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev1,NB_ORA_SERV=HPLIB)';
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev2,NB_ORA_SERV=HPLIB)';
ALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev1,NB_ORA_SERV=HPLIB)';
ALLOCATE AUXILIARY CHANNEL aux4 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev2,NB_ORA_SERV=HPLIB)';
DUPLICATE TARGET DATABASE TO SDB;
}
The restore of datafiles was successful ; however the archivelog backup pointing to the second node was not restored correctly ( since our restore script failed to include the second node from where to get the other set of archivelogs ); & so we decided to recover it using the following :
SQL> select status from v$instance;
STATUS
------------
MOUNTED
oracle@appdev4:/home/oracle>rman target sys/a@dev auxiliary / nocatalog
Recovery Manager: Release 10.2.0.4.0 - Production on Wed Apr 2 08:23:38 2014
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: DEV (DBID=1605254398)
using target database control file instead of recovery catalog
connected to auxiliary database: SDB (DBID=1605254398, not open)
RMAN> run {
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev1,NB_ORA_SERV=HPLIB)';
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev1,NB_ORA_SERV=HPLIB)';
ALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev2,NB_ORA_SERV=HPLIB)';
ALLOCATE AUXILIARY CHANNEL aux4 DEVICE TYPE SBT_TAPE PARMS='ENV=(NB_ORA_CLIENT=dddev2,NB_ORA_SERV=HPLIB)';
recover database ; }
which failed with :
Starting recover at 02-APR-14
starting media recovery
media recovery failed
released channel: aux1
released channel: aux2
released channel: aux3
released channel: aux4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/02/2014 08:23:59
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start
ORA-00283: recovery session canceled due to errors
ORA-01124: cannot recover data file 1 - file is in use or recovery
ORA-01110: data file 1: '/dev/vg_dev4/rsystem01.dbf'
For some reason this process started to recover the source system ; with a lot of errors in the Source Alert logs :
Wed Apr 2 16:30:17 2014
Completed: alter database recover datafile list clear
Wed Apr 2 16:30:17 2014
alter database recover datafile list
1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12 , 13 , 14 , 15 , 16 , 17 , 18 , 19 , 20
Completed: alter database recover datafile list
1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12 , 13 , 14 , 15 , 16 , 17 , 18 , 19 , 20
Wed Apr 2 16:30:17 2014
alter database recover datafile list
21 , 22 , 23 , 24 , 25 , 26 , 27 , 28 , 29 , 30 , 31 , 32 , 33 , 34 , 35 , 36 , 115 , 394 , 396 , 398
Completed: alter database recover datafile list
21 , 22 , 23 , 24 , 25 , 26 , 27 , 28 , 29 , 30 , 31 , 32 , 33 , 34 , 35 , 36 , 115 , 394 , 396 , 398
Wed Apr 2 16:30:17 2014
Media Recovery Start
Wed Apr 2 16:30:17 2014
Media Recovery failed with error 1124
ORA-283 signalled during: alter database recover if needed
start
1. Is this the correct way to recover the DB using the backed up archivelogs ?
How do we effectively recover the DB at this point ?
2. What was wrong with our approach and how did it end up writing to the source file system ?
Please advice.
Thanks,