RMAN: TSPITR fails wirh RMAN-06024

Hi everybody,
where are trying to create a auxilary database from backupsets which are stored on tape.
Now when we want to restore the controlfile with restore clone controlfile the Backup fails with following error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 09/08/2011 15:55:18
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
The strange thing is that we have many backups of controlfiles because we have controfile autobackup on. Also i issued a list backup of controlfile and that shows me many backups of controlfiles.
One thing that would be interessting is, that we moved our rman catalog to another db instance. So at the time the backup i want to restore was taken, the database was registered in the old rman catalog.
So does anybody know how to investigate and hopefully resolve this failure?
Any help is much appreciated.
Greetings

Hi,
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restoreFrom the error the backups could not able to find with location of tapes which you referred in your backup script.
As you said that you have moved your catalog to different database, further from your previous reply that resync didn't work ?
Catalog is stored and with that query we were able to find out the needed Tapes.
Also a list backup of controlfile is successfull.
So any other ideas?Can you reconfirm or recheck from your end that the dbid which referred from your list with existing databases are correct.
- Pavan Kumar N

Similar Messages

Fully Automated RMAN TSPITR fails

condition:
oracle 11.2&&windows7(32bit)
       I performed Fully Automated RMAN TSPITR yesterday.When the oracle performed the export of the metadata of the recovery set,the following problem appeared.
Performing export of metadata...
   EXPDP> Starting "SYS"."TSPITR_EXP_dbtF":
Removing automatic instance
shutting down automatic instance
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/23/2013 01:01:05
RMAN-06136: ORACLE error from auxiliary database: ORA-01097: cannot shutdown while in a transaction - commit or rollback first
RMAN-06962: Error received during export of metadata
RMAN-06960:    EXPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-39187: The transportable set is not self-contained, violation list is
ORA-39906: Constraint FK_PK between table SH.PK in tablespace TEST01 and table SH.FK in tablespace TEST02.
         The message of the problem tells me that the transprotable set is not self-contained.But I remember that I have dropped the constraint FK_PK.And then I run the following code.And the result tells me that the constraint surely be dropped.
       So ,why does the problem occur?
        Thanks!
SQL> select count(*) from dba_constraints where constraint_name ='FK_PK';
COUNT(*)
         0
SQL>    Begin
2         dbms_tts.transport_set_check('TEST02,TEST01',true,true);
3     End;
4 /
PL/SQL procedure successfully completed.
SQL> select * from transport_set_violations;
no rows selected

I just drop the constriant FK_PK.There are no index dropped of the tablespace test02 in the dba_recyclebin.
SQL> select object_name,original_name,type,ts_name from dba_recyclebin;
OBJECT_NAME                    ORIGINAL_N TYPE       TS_NAME
BIN$c96+yjANSE6ThcTovMwoPw==$0 TAB        TABLE      USERS
BIN$MkU0+TSYSJK1qnCAKglJFg==$0 TABLE1     TABLE      USERS
BIN$YCQ2IgKaQDWw6Cxrl6QRaA==$0 TAB        TABLE      TEST01
SQL> show user;
USER is "SH"
SQL> select name from v$database;
NAME
WAREHOUS
And the following code (starting the RMAN---occur the problem):
SQL> $rman target sys/123456@warehouse catalog rman/123456@catalog;
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Aug 23 10:29:47 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: WAREHOUS (DBID=4011143137)
connected to recovery catalog database
RMAN> recover tablespace test02 until scn 1346235 auxiliary destination 'G:\Oracle\TS';
Starting recover at 23-AUG-13
starting full resync of recovery catalog
full resync complete
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=22 device type=DISK
Creating automatic instance, with SID='atmp'
initialization parameters used for automatic instance:
db_name=WAREHOUS
db_unique_name=atmp_tspitr_WAREHOUS
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=G:\Oracle\TS
log_archive_dest_1='location=G:\Oracle\TS'
#No auxiliary parameter file used
starting up automatic instance WAREHOUS
Oracle instance started
Total System Global Area     292933632 bytes
Fixed Size                     1374164 bytes
Variable Size                100665388 bytes
Database Buffers             184549376 bytes
Redo Buffers                   6344704 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until scn 1346235;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
# resync catalog
resync catalog;
executing Memory Script
executing command: SET until clause
Starting restore at 23-AUG-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=59 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0NOHKRT6_1_1
channel ORA_AUX_DISK_1: piece handle=G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0NOHKRT6_1_1 tag=LEVEL1_CUMULATIVE
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=G:\ORACLE\TS\WAREHOUSE\CONTROLFILE\O1_MF_91FLFZYS_.CTL
Finished restore at 23-AUG-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
starting full resync of recovery catalog
full resync complete
contents of Memory Script:
# set requested point in time
set until scn 1346235;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 7 to
"D:\APP\ASUS\ORADATA\WAREHOUSE\TEST02.DBF";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 3, 2, 7;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_TEMP_%U_.TMP in control file
Starting restore at 23-AUG-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSTEM_%U_.DBF
channel ORA_AUX_DISK_1: restoring datafile 00003 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_UNDOTBS1_%U_.DBF
channel ORA_AUX_DISK_1: restoring datafile 00002 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSAUX_%U_.DBF
channel ORA_AUX_DISK_1: restoring datafile 00007 to D:\APP\ASUS\ORADATA\WAREHOUSE\TEST02.DBF
channel ORA_AUX_DISK_1: reading from backup piece G:\ORACLE\BACKUP\WAREHOUSE\LEVEL0_0IOHKQV0_1_1
channel ORA_AUX_DISK_1: piece handle=G:\ORACLE\BACKUP\WAREHOUSE\LEVEL0_0IOHKQV0_1_1 tag=LEVEL0
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:55
Finished restore at 23-AUG-13
datafile 1 switched to datafile copy
input datafile copy RECID=5 STAMP=824207618 file name=G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSTEM_91FLGBWL_.DBF
datafile 3 switched to datafile copy
input datafile copy RECID=6 STAMP=824207618 file name=G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_UNDOTBS1_91FLGBYW_.DBF
datafile 2 switched to datafile copy
input datafile copy RECID=7 STAMP=824207618 file name=G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSAUX_91FLGBXY_.DBF
contents of Memory Script:
# set requested point in time
set until scn 1346235;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 3 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 7 online";
# recover and open resetlogs
recover clone database tablespace "TEST02", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 3 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 7 online
Starting recover at 23-AUG-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00007: D:\APP\ASUS\ORADATA\WAREHOUSE\TEST02.DBF
destination for restore of datafile 00001: G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSTEM_91FLGBWL_.DBF
destination for restore of datafile 00003: G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_UNDOTBS1_91FLGBYW_.DBF
destination for restore of datafile 00002: G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSAUX_91FLGBXY_.DBF
channel ORA_AUX_DISK_1: reading from backup piece G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0MOHKRRO_1_1
channel ORA_AUX_DISK_1: piece handle=G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0MOHKRRO_1_1 tag=LEVEL1_CUMULATIVE
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
starting media recovery
archived log for thread 1 with sequence 14 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_18\O1_MF_1_14_911NKBNY_.ARC
archived log for thread 1 with sequence 15 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_15_912Y0W3B_.ARC
archived log for thread 1 with sequence 16 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_16_91475BY4_.ARC
archived log for thread 1 with sequence 17 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_17_9149CJMS_.ARC
archived log for thread 1 with sequence 18 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_18_915MLYR1_.ARC
archived log for thread 1 with sequence 19 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_19_915OR34Z_.ARC
archived log for thread 1 with sequence 20 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_20_916XQMRD_.ARC
archived log for thread 1 with sequence 21 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_21_91715KYK_.ARC
archived log for thread 1 with sequence 22 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_22_91884645_.ARC
archived log for thread 1 with sequence 23 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_23_919JV790_.ARC
archived log for thread 1 with sequence 24 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_24_91D6GRC1_.ARC
archived log for thread 1 with sequence 25 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_25_91D7OOOR_.ARC
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_18\O1_MF_1_14_911NKBNY_.ARC thread=1 sequence=14
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_15_912Y0W3B_.ARC thread=1 sequence=15
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_16_91475BY4_.ARC thread=1 sequence=16
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_16_91475BY4_.ARC thread=1 sequence=16
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_17_9149CJMS_.ARC thread=1 sequence=17
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_18_915MLYR1_.ARC thread=1 sequence=18
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_19_915OR34Z_.ARC thread=1 sequence=19
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_20_916XQMRD_.ARC thread=1 sequence=20
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_21_91715KYK_.ARC thread=1 sequence=21
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_22_91884645_.ARC thread=1 sequence=22
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_23_919JV790_.ARC thread=1 sequence=23
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_24_91D6GRC1_.ARC thread=1 sequence=24
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_25_91D7OOOR_.ARC thread=1 sequence=25
media recovery complete, elapsed time: 00:00:44
Finished recover at 23-AUG-13
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST02 read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
G:\Oracle\TS''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
G:\Oracle\TS''";
executing Memory Script
sql statement: alter tablespace TEST02 read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''G:\Oracle\TS''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''G:\Oracle\TS''
Performing export of metadata...
   EXPDP> Starting "SYS"."TSPITR_EXP_atmp":
Removing automatic instance
shutting down automatic instance
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/23/2013 10:36:08
RMAN-06136: ORACLE error from auxiliary database: ORA-01097: cannot shutdown while in a transaction - commit or rollback first
RMAN-06962: Error received during export of metadata
RMAN-06960:    EXPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-39187: The transportable set is not self-contained, violation list is
ORA-39906: Constraint FK_PK between table SH.PK in tablespace TEST01 and table SH.FK in tablespace TEST02.
RMAN>

Rman command fails with "RMAN-00554: initialization of internal RMAN"

Hi
I am at cross roads with no direction. 2 things and most like cause for the issue is same
1)rman target rman1/rman1@ppmqa
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 10:34:46 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
2) sqlnet userid/passwd@db1 "/as sysdba" works some times and fails with insufficient privileges" some times
ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:55 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:57 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
SQL>
Information on environment and let me know if you need or know any more details... thanks in advance.
CRS Version 11201 and so DB
current parameters:
SQL> show parameter remote
NAME TYPE VALUE
remote_dependencies_mode string TIMESTAMP
remote_listener string sqrac202-scan.frxntnyc.frx2.co
m:1521
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
result_cache_remote_expiration integer 0
SQL> select * from v$pwfile_users
USERNAME SYSDB SYSOP SYSAS
SYS TRUE TRUE FALSE
RMAN1 TRUE TRUE FALSE
sqlnet.ora from GRID Home
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
ADR_BASE = /oracle/base
#################################

I found solution just now, this is very simple i was not aware this but this is how it working
Hope this helps
I granted sysdba from node A but not from node B, thinking that if you grant any privilege at instance level that is applicable to db level but that is not the case with sysdba privs
so i need to grant it from both nodes A and B.
here is the output
test case
initially no entry for instance 2
1) select * from gv$pwfile_users;
INST_ID USERNAME SYSDB SYSOP SYSAS
2 SYS TRUE TRUE FALSE
1 SYS TRUE TRUE FALSE
1 RMAN1 TRUE TRUE FALSE
2) grant sysdba to rman1 -- this I did at NODE B or instance 2
3) SQL> select * from gv$pwfile_users;
INST_ID USERNAME SYSDB SYSOP SYSAS
2 SYS TRUE TRUE FALSE
2 RMAN1 TRUE FALSE FALSE
1 SYS TRUE TRUE FALSE
1 RMAN1 TRUE TRUE FALSE
4) I am able to connect remotely
C:\Documents and Settings\kthoka> sqlplus rman1/rman1@ppmqa "as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Thu Dec 16 13:59:20 2010
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management
OLAP,
Data Mining and Real Application Testing options
SQL> select instance_name from v$instance;
INSTANCE_NAME
ppmqa2
5) rman also working fine
ppmqa 03:00 PM sqrac202a:/oracle/NSQ/112_64/dbs > rman target rman1/rman1@ppmqa
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 15:00:32 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PPMQA (DBID=774170541)
RMAN> exit
Recovery Manager complete.

Rman duplication fails with RMAN-00600

Hi All,
I'm trying to perform a database duplication from a prod server to a non prod one with ORacle 11gR2.
I'm performing a backup-based duplication without target connection from DEV3 database to DEV1 database. I followed the steps mentionned in the "backup & Recovery Guide" http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmdupdb.htm
Here are the steps I followed:
1. I configured my spfile of the auxiliary database like the target one. I also added these lines to change the location of the restores:
SQL> alter system set log_file_name_convert='/u04/DEV3/rdo','/u04/DEV1/rdo','/u03/DEV3/rdo','/u03/DE V1/rdo','/u02/DEV3/rdo','/u02/DEV1/rdo' scope=spfile;
SQL> alter system set db_file_name_convert='/u04/DEV3/rdo','/u04/DEV1/rdo','/u03/DEV3/rdo','/u03/DEV1/rdo','/u02/DEV3/rdo','/u02/DEV1/rdo','/u02/DEV3/dbf/DEV3','/u02/DEV1/dbf/DEV1' scope=spfile;
2. I then shutdown the database, and start it in nomount mode.
3. I connect to the auxiliary database, and the recovery catalog
4. I run the following rman duplication command:
RUN{
DUPLICATE DATABASE DEV3 to DEV1;
The restore succeeds but at the end, the recovery ends with the following error:
channel ORA_AUX_DISK_6: reading from backup piece /RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_138.rman
channel ORA_AUX_DISK_4: piece handle=/RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_136.rman tag=LVL0_DB_BKP
channel ORA_AUX_DISK_4: restored backup piece 2
channel ORA_AUX_DISK_4: restore complete, elapsed time: 02:24:10
channel ORA_AUX_DISK_6: piece handle=/RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_138.rman tag=LVL0_DB_BKP
channel ORA_AUX_DISK_6: restored backup piece 2
channel ORA_AUX_DISK_6: restore complete, elapsed time: 02:25:09
Finished restore at 06/06/11 15:22:58
contents of Memory Script:
catalog clone datafilecopy "/u02/DEV1/dbf/DEV1/undotbs01.dbf";
switch clone datafile 3 to datafilecopy
"/u02/DEV1/dbf/DEV1/undotbs01.dbf";
switch clone datafile all;
executing Memory Script
cataloged datafile copy
datafile copy file name=/u02/DEV1/dbf/DEV1/undotbs01.dbf RECID=70 STAMP=753117778
datafile 3 switched to datafile copy
input datafile copy RECID=70 STAMP=753117778 file name=/u02/DEV1/dbf/DEV1/undotbs01.dbf
datafile 1 switched to datafile copy
input datafile copy RECID=71 STAMP=753117780 file name=/u02/DEV1/dbf/DEV1/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=72 STAMP=753117780 file name=/u02/DEV1/dbf/DEV1/sysaux01.dbf
contents of Memory Script:
set until scn 7241504550365;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 06/06/11 15:23:15
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
using channel ORA_AUX_DISK_3
using channel ORA_AUX_DISK_4
using channel ORA_AUX_DISK_5
using channel ORA_AUX_DISK_6
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command recover : 600
RMAN-00600: internal error, arguments [8029] [1] [] [] []
Can someone please help me resolve this issue???it's quite urgent.
Thank you,
Farah

I am facing same error, did any of you find a resolution yet?
contents of Memory Script:
set until scn 7243533883622;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 10/12/11 19:33:12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command recover : 600
RMAN-00600: internal error, arguments [8029] [1] [] [] []
Wed Oct 12 19:33:14 CEST 2011 Remove the lock file
ERROR: RMAN FAILUR
I see many kblockd processes, can this be an indication:
applprod@gvaebsdb3:~ $ ps -ef|grep kblockd
root 231 211 0 Oct05 ? 00:00:00 [kblockd/0]
root 232 211 0 Oct05 ? 00:00:00 [kblockd/1]
root 233 211 0 Oct05 ? 00:00:00 [kblockd/2]
root 234 211 0 Oct05 ? 00:00:00 [kblockd/3]
root 235 211 0 Oct05 ? 00:00:00 [kblockd/4]
root 236 211 0 Oct05 ? 00:00:00 [kblockd/5]
root 237 211 0 Oct05 ? 00:00:00 [kblockd/6]
root 238 211 0 Oct05 ? 00:00:00 [kblockd/7]
root 239 211 0 Oct05 ? 00:00:00 [kblockd/8]
root 240 211 0 Oct05 ? 00:00:00 [kblockd/9]
root 241 211 0 Oct05 ? 00:00:00 [kblockd/10]
root 242 211 0 Oct05 ? 00:00:00 [kblockd/11]
root 243 211 0 Oct05 ? 00:00:00 [kblockd/12]
root 244 211 0 Oct05 ? 00:00:00 [kblockd/13]
root 245 211 0 Oct05 ? 00:00:00 [kblockd/14]
root 246 211 0 Oct05 ? 00:00:00 [kblockd/15]
Thanks,
Horia

RMAN Restoration failed from ASM to non asm

While restoring the database, we are getting this error frequently, updated the media center they said media is intact, but there is some "NO POLICY" NO SCHEDULE" error. what does this mean.
Could some one please help us why and how to resolve this issue. We are stuck in between our restoration.
ORA-19870: error reading backup piece ROCT_rman_db_weekly_20110719_2jmhrat3_1_1
ORA-19507: failed to retrieve sequential file, handle="ROCT_rman_db_weekly_20110719_2jmhrat3_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Failed to process backup file <ROCT_rman_db_weekly_20110719_2jmhrat3_1_1>

784786 wrote:
While restoring the database, we are getting this error frequently, updated the media center they said media is intact, but there is some "NO POLICY" NO SCHEDULE" error. what does this mean.
Could some one please help us why and how to resolve this issue. We are stuck in between our restoration.
ORA-19870: error reading backup piece ROCT_rman_db_weekly_20110719_2jmhrat3_1_1
ORA-19507: failed to retrieve sequential file, handle="ROCT_rman_db_weekly_20110719_2jmhrat3_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Failed to process backup file <ROCT_rman_db_weekly_20110719_2jmhrat3_1_1>where is No policy/no schedule errors?
Error reading backup piece can occur even the handle was corrupt (or) handle was unable to read (or) did tapes loaded in MML ?
*RMAN Duplicate fails with ORA-19870, ORA-19507, ORA-27029 and ORA-19511 [ID 562780.1]*

RMAN Backup Failed.

Hi Gurus,
My RMAN backup failed with below error.Please suggest.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 01/26/2013 22:48:56
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
RMAN>
Recovery Manager complete.
Thanks,

The message indicates that your database is in NOARCHIVELOG mode. You cannot make an RMAN Backup of a database that is OPEN if it is in NOARCHIVELOG mode.
You have two options
1. Make consistent RMAN Backups with the database only in MOUNT mode (SHUTDOWN ; STARTUP MOUNT)
OR
2. Configure for ArchiveLogs (create a target filesystem or FRA), set the database to ARCHIVELOG mode, monitor the volume of ArchiveLog generation, configure both Database and ArchiveLog backups.
Hemant K Chitale

Rman archivelog backup fails with rman-03002,ora-19563

Hi,
D:\ Oracle- -\BIN\RMAN TARGET / NOCATALOG
RMAN> backup archivelog all;
RMAN-03002: Error with backup command on 06-25-2013
ORA-19563: Header-Validation is not successful.
fails with the given errors.
11.2.0.2 PROD DB on Windows Server 2008 R2 Enterpriise.
When I issue BACKUP INCREMENTAL LEVEL 0 DATABASE; it works fine. but with archivelog it is creating problems. Unfortunatly, I have not found exactly the same problem on google and on Oracle support.
The DB is using INIT.ORA and last time when I switched the mode to archive log mode I set the parameter like SCOPE=MEMORY as SPFILE was not in use and ALTER SYSTEM with SCOPE=BOTH FRA destination and size, but after the DB restarting of course that setting is gone and I am having these problems.
Please suggest.
Thanks a lot.
Best Regards,

Hi,
Thanks a lot.
I don't think that archivelogs were relocated, except I changed the location yesterday.
As I wrote at the start that because of INIT.ORA file being in use instead of SPFILE. I set DB_RECOVERY_FILE_DEST, DB_RECOVERY_DEST_SIZE after changing the DB mode to ARCHIVELOG, but DB was restarted by somebody else, and as the parameter changing was NOT PERMANENT, it rollback.
LOG_ARCHIVE_DEST was set to d:\oradata\db with archivelog mode but db_recovery_file_dest and size was set to 0. Now here, I have no idea that whether archivelogs were not being backed up or deleted physically, but I guess that as log_archive_dest parameter is deprecated and mode is set to archivelog with no real ARCHIVELOG DESTINATION. Please correct me if I am wrong or totally wrong :-)
I performed DELETED EXPIRED ARCHIVELOG ALL, and it deleted 49 EXPIRED objects.
Now CROSSCHECK ARCHIVELOG ALL and LIST ARCHIVELOG ALL shows nothing.
LIST BACKUP OF ARCHIVELOG ALL has of course those 49 archivelog gap.
Could you please tell the impacts of those 49 missing archivelogs. Retention policy is set to 14 days. I mean the risk is for 14 days right? As anyhow, the older backups are being DELETED according to retention policy of RMAN.

RMAN duplicate failed

Hi all,
have below doubts.
IF RMAN duplicate failed in the middle of the process due to disk full or any other reason.
Do I start from the beginning again or is there anyway to sort of "resume" from where it stopped?
Please consider what need to do in 9i or in 10G.
Please also reply what need to do for FS or for ASM.
Please also share if you have any doc or link.

Hi,
IF RMAN duplicate failed in the middle of the process due to disk full or any other reason.See always perform fresh duplicate.
it will overwrite the existing files... so you need to check in alert log file like how many files restored & recovered during duplicate..
sybrand_b wrote:
Duplicate database is a quite robust command.
It will automatically skip what has already been done, so you can safely re-execute it without problems.
Been there, done that.
Sybrand Bakker
Senior Oracle DBA@sybrand
What it automatically skips?
1)did RMAN duplicate knows about earlier restores...
2)if i restored system,sysaux,users,undo datafiles of another database and again I'm performing another database in same location.. so it will skip?
are you sure...
Thanks
*Manual Completion of a Failed RMAN Duplicate [ID 360962.1]*
Edited by: CKPT on Dec 11, 2010 12:40 PM

RMAN TSPITR 600 fatal error

Hi, I run RMAN TSPITR and got a RMAN-00600: internal error. could anyone see the follwing ouput and give some advice?
thanks.
------------------output from RMAN ---------------------
run{
allocate clone channel c1 type disk;
allocate clone channel c2 type disk;
recover tablespace "RMAN" until time '2002-Dec-16 13:19:10';
allocated channel: c1
channel c1: sid=10 devtype=DISK
allocated channel: c2
channel c2: sid=11 devtype=DISK
Starting recover at Dec 16 2002 17:00:09
printing stored script: Memory Script
# set the until clause
set until time "2002-Dec-16 13:19:10";
# restore the controlfile
restore clone controlfile to clone_cf;
# replicate the controlfile
replicate clone controlfile from clone_cf;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log for tspitr to a resent until time
sql 'alter system archive log current';
# resync catalog after controlfile restore
resync catalog;
executing script: Memory Script
executing command: SET until clause
Starting restore at Dec 16 2002 17:00:09
channel c1: starting datafile backupset restore
channel c1: restoring controlfile
output filename=/orabackup/aux/control01.ctl
channel c1: restored backup piece 1
piece handle=/orabackup/df_ECAZ3_56_1 tag=null params=NULL
channel c1: restore complete
Finished restore at Dec 16 2002 17:00:11
replicating controlfile
input filename=/orabackup/aux/control01.ctl
sql statement: alter database mount clone database
sql statement: alter system archive log current
starting full resync of recovery catalog
full resync complete
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 12/16/2002 17:00:21
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code: 600
RMAN-03013: command type: recover
RMAN-00600: internal error, arguments [5502] [] [] [] []

Is the receovery catalog in the same database you want to recover?

Rman restore failed

HI All,
I would be thankful to you if you help me.
I am restoring full database backup with RMN but due to space crunch issue my restore got failed.
Please let me know is there any way i can start my restore operation from the point it failed with RMAN
Regards,

910742 wrote:
HI AlL,
Please share you experience.Patience, Grasshopper
You posted this follow-up a mere SIX minutes after your previous post.
This forum is not a chat line, and it is not paid support.
Everyone here has a job for which they are paid, and this forum is not it.
No one is responsible for monitoring it and giving a quick response.
Furthermore, it is a global forum. The person with the information you seek may very well live 20 time zones away from you and was going to bed just as you posted. He will not even see your post for several more hours.
Your original post went up in the middle of the night for half the world.
No one with the information you seek is deliberately withholding it until you sound sufficiently desperate.

RMAN TSPITR

I try to understand why we cannot perform a second attemp at RMAN TSPITR without a recovery catalog.... Any idea??
========================================================
It is extremely important that you choose the right target time or SCN for TSPITR. After you bring a tablespace online after TSPITR, you cannot use any backup from a time earlier than the moment you brought the tablespace online. In practice, this means that you cannot make a second attempt at TSPITR if you choose the wrong target time the first time, unless you are using a recovery catalog. If you have a recovery catalog, however, you can perform repeated TSPITR operations to different target times.
\==============================================================

As indicated in the docs:
Assume that you run TSPITR on a tablespace, and then bring the tablespace online at time t. When not using a recovery catalog, the current control file has no record of the older incarnation of the recovered tablespace. Thus, recovery with a current control file that involves this tablespace can no longer use a backup taken prior to time t. You can, however, perform incomplete recovery of the whole database to any time less than or equal to t, if you can restore a backup control file from before time t.
HTH

Rman backup fails on windows when using batch file

Hello Gurus ..
I am trying to setup incremental backup on my windows OS based server using RMAN command in batch file. When I use batch file in OS scheduler it is working fine, when I am calling same batch file from my LOCAL desktop PC it throws errors as below.
D:\> \\3.193.211.19\sgdba\rman\bkp_acressit.bat
D:\>rman catalog rman/******@acressit target / cmd
file=E:\sgdba\rman\bkp_arch.rcv log E:\sgdba\rman\sit_arch_rman_backup.log
RMAN-00557: could not open MSGLOG "E:\sgdba\rman\sit_arch_rman_backup.log"
Argument Value Description
target quoted-string connect-string for target database
catalog quoted-string connect-string for recovery catalog
nocatalog none if specified, then no recovery catalog
cmdfile quoted-string name of input command file
log quoted-string name of output message log file
trace quoted-string name of output debugging message log file
append none if specified, log is opened in append mode
debug optional-args activate debugging
msgno none show RMAN-nnnn prefix for all messages
send quoted-string send a command to the media manager
pipe string building block for pipe names
timeout integer number of seconds to wait for pipe input
checksyntax none check the command file for syntax errors
Both single and double quotes (' or ") are accepted for a quoted-string.
Quotes are not required unless the string contains embedded white-space.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00556: could not open CMDFILE "E:\sgdba\rman\bkp_arch.rcv"
Contents of the batch file and RCV file as below:
Batch File:
rman catalog rman/*******@acressit target / cmdfile=E:\sgdba\rman\bkp_arch.rcv log E:\sgdba\rman\sit_arch_rman_backup.log
RCV File:
RUN {
ALLOCATE CHANNEL ch1 TYPE
DISK FORMAT 'E:\ORA_RMAN_BACKUP\ARCH_%d_%u_%s_%p';
BACKUP ARCHIVELOG delete input;
RELEASE CHANNEL ch1;
EXIT;
--------------------------xxxxxxxxxxxxxx------------------------
* on my DB server I am login using my administrator account, on my PC I dont have admin account.
* I have checked remote execution using local user as well as admin user.
* I have checked the permission and my local ID & EVERYONE has all permission in that folder.
Any help will be appriciated.
Thanks & Regards
Ashish

Ashish wrote:
hi Atil,
u have guessed it correctly, I came to know that issue later I copy file on local PC and it works fine.
Now I am working on netbackup server. I want to use the same script to initiate backup from netbackup server. Do you have any idea or any guidelines from you will appriciate.
Thanks
AshishAshish,
Is it "symantec's netbackup"? I do not know that product and if it has an option to enter your own RMAN scripts. On the other hand, it should be able to create irman scripts according to your backup job definition.
Regards
Gokhan

How to I find out if rman backup that was done is Rman Cold backup or Rman

Hi,please help me I have backup set ,that is backupset that have rman data backup and autobackup that have control file,I want to restore this backup but I don't know how the backup was done .please advice me how to check if this was Rman cold backup or rman hot backup.I have pfile that is extracted from database before backup was taken.

Hi Thanks for the update,I checked the v$backup_set on the other database ,but it does not tell me whether ithe backup was Rman cold backup in which database was mounted or Rman hot backup ,now I have to do the restore but I don't know what type of backup do I have please assist.
Edited by: user1022397 on 2010/11/11 4:40 AM

Tablespace Point in Time Recovery fails with RMAN-06026:

I have cataloged with RMAN the datafiles from Snapshot backup. Still it fails with the following error.
RMAN> RECOVER TABLESPACE TSPC UNTIL TIME "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')" AUXILIARY DESTINATION '/tmp/auxpran';
Starting recover at 03-APR-13
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='Ebgt'
initialization parameters used for automatic instance:
db_name=ORCL
db_unique_name=Ebgt_tspitr_ORCL
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/tmp/auxpran
log_archive_dest_1='location=/tmp/auxpran'
#No auxiliary parameter file used
starting up automatic instance ORCL
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 03-APR-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=19 device type=DISK
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: copied control file copy
input file name=/tmp/auxpran/controlbc.ctl
output file name=/tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl
Finished restore at 03-APR-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 5 to
"+DG_DATA/orcl/datafile/tspc.268.811733685";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 3, 2, 5;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /tmp/auxpran/ORCL/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 03-APR-13
using channel ORA_AUX_DISK_1
One or more auxiliary set datafiles could not be removed
Removing automatic instance
shutting down automatic instance
database dismounted
Oracle instance shut down
Automatic instance removed
auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/03/2013 02:32:55
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Could anyone please reply ASAP?
Regards,
Pranam

I had created a snapshot of the database(datafiles and archivelogs) and cataloged them.
CATALOG START WITH "+TBL_DG_DATA/ORCL/DATAFILE/" NOPROMPT;
catalog start with "+DG_ARCH/ORCL/ARCHIVELOG/" NOPROMPT;
The time i gave was after the snapshot was created.
When it failed the first time I created another controlfile using
sql "alter database backup controlfile to ''/tmp/auxpran/controlbc.ctl''";
And ran the recover command after the time after i generated this controlfile. Changed nothing else. TSPITR completed successfully. But it had failed first time. Cannot figure how it ran the second time but failed the first time.
Removing automatic instance
Automatic instance removed
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_temp_8opndd87_.tmp deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_3_8opnd1o6_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_2_8opncy32_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_1_8opncv7d_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_sysaux_8opn516p_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_undotbs1_8opn4j14_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_system_8opmyvly_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opmy14q_.ctl deleted
Finished recover at 03-APR-13

RMAN script failed while creating Data Guard 11g

Hi Friends,
I am creating Physical Standby (11g) using RMAN (ACTIVE) on windows using the doc : Step by Step Guide on Creating Physical Standby Using RMAN DUPLICATE...FROM ACTIVE DATABASE [ID 1075908.1]
The folder structure on Primary DB and on Physical Standby is totally different.
while executing RMAN script i got errors for lot of locations and i specified the proper location in RMAN script itself (ex set diagnostic_dest = 'c:\app\' , set db_recovery_file_dest='C:\app\flash_recovery_area')
Location of control files on Primary DB:
D:\oradata\MESSTG\CONTROL01.CTL
D:\oradata\flash_recovery\messtg\MESSTG\CONTROL02.CTL
Location of control files (planned) on Physical Standby DB:
C:\app\oradata\MESSTDBY\CONTROL01.CTL
C:\app\flash_recovery_area\MESSTDBY\CONTROL02.CTL
How to specify control file location of Physical standby in set control_files?
Also i have 2 control files on Primary DB so do i need to specify both the control files , if so how?
I tried different combination in RMAN script but all are failed:
set control_files='D:\oradata\MESSTG\CONTROL01.CTL','C:\app\oradata\MESSTDBY\CONTROL01.CTL'
RMAN Error is :
while using set control_files=: C:\app\oradata\MESSTDBY\CONTROL01.CTL
contents of Memory Script:
backup as copy current controlfile for standby auxiliary format 'D:\ORADATA\MESSTG\CONTROL01.CTL';
restore clone controlfile to 'C:\APP\ORADATA\MESSTDBY\CONTROL01.CTL' from
'D:\ORADATA\MESSTG\CONTROL01.CTL';
executing Memory Script
Starting backup at 16-APR-13
channel prmy1: starting datafile copy
copying standby control file
released channel: prmy1
released channel: prmy2
released channel: prmy3
released channel: prmy4
released channel: stby
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/16/2013 14:18:41
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on prmy1 channel at 04/16/2013 14:18:41
ORA-17628: Oracle error 19505 returned by remote Oracle server
RMAN>
Error 2)
while using set control_files='D:\oradata\MESSTG\CONTROL01.CTL','C:\app\oradata\MESSTDBY\CONTROL01.CTL'
contents of Memory Script:
backup as copy current controlfile for standby auxiliary format 'D:\ORADATA\MESSTG\CONTROL01.CTL';
executing Memory Script
Starting backup at 16-APR-13
channel prmy1: starting datafile copy
copying standby control file
released channel: prmy1
released channel: prmy2
released channel: prmy3
released channel: prmy4
released channel: stby
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/16/2013 13:22:33
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on prmy1 channel at 04/16/2013 13:22:33
ORA-17628: Oracle error 19505 returned by remote Oracle server
RMAN>
Regards,
DB

Hi,
Can you paste here you rman script ?
I think following script can help you.
duplicate target database for standby
from active database
spfile
set "control_files"="d:\oradata\<standbydbuniquename>\CONTROL01.CTL"
set "db_name"="<DBNAME>"
set "db_unique_name"="<STANBYD DBA UNIQUENAME>"
set "db_file_name_convert"="C:\app\oracle\oradata\<dbname>","d:\oradata\<standbydbuniquename>"
set "log_file_name_convert"="C:\app\oracle\oradata\<dbname>","d:\oradata\<standbydbuniquename>"
set "db_recovery_file_dest"="D:\fast_recovery_area"
nofilenamecheck;C:\app\oracle\oradata\<dbname> - it is primary database dafiles location
D:\oradata\<standbydbuniquename> - it is standby database datafile location.
Don't forget creation of diagnostinc dests.
Regards
Mahir M. Quluzade

RMAN: TSPITR fails wirh RMAN-06024

Similar Messages

Maybe you are looking for