RMAN-05001: auxiliary filename +ARS_DAT9/ars/datafile/arsystem1.259.6326886

Hi Forum
I'm trying to create a standby database, but rman was returning this error:
Recovery Manager: Release 10.2.0.3.0 - Production on Sun Sep 9 14:57:57 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ARS (DBID=3312174455)
connected to auxiliary database: ARS (not mounted)
RMAN> duplicate target database for standby;
Starting Duplicate Db at 09-SEP-07
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=156 devtype=DISK
contents of Memory Script:
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
Starting restore at 09-SEP-07
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/bkp2/qoirgqbb_1_1
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/oracle/bkp2/qoirgqbb_1_1 tag=TAG20070909T133643
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:08
output filename=+ARS_DAT1/ars_stb/controlfile/current.259.632847497
Finished restore at 09-SEP-07
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/09/2007 14:58:23
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename +ARS_DAT9/ars/datafile/arsystem1.259.632688645 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT8/ars/datafile/arsystem1.259.632688517 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT11/ars/datafile/arsystem1.258.632688041 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT10/ars/datafile/arsystem1.258.632687911 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT9/ars/datafile/arsystem1.258.632687595 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT8/ars/datafile/arsystem1.258.632687189 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT11/ars/datafile/arsystem1.257.632687073 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT10/ars/datafile/arsystem1.257.632686841 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT9/ars/datafile/arsystem1.257.632686671 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT8/ars/datafile/arsystem1.257.632686585 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT11/ars/datafile/arsystem1.256.632686301 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT10/ars/datafile/arsystem1.256.632686193 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT9/ars/datafile/arsystem1.256.632685671 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT8/ars/datafile/arsystem1.256.632685547 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT3/ars/datafile/arindex.258.624755731 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT3/ars/datafile/arindex.257.624755679 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT3/ars/datafile/arindex.256.624755627 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT2/ars/datafile/arhistory.258.624755445 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT2/ars/datafile/arsystem2.259.624755449 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT2/ars/datafile/arsystem2.257.624755395 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT2/ars/datafile/integracao.256.624755339 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT1/ars/datafile/undotbs2.264.624752453 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT1/ars/datafile/users.259.624752397 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT1/ars/datafile/sysaux.257.624752397 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT1/ars/datafile/undotbs1.258.624752397 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +ARS_DAT1/ars/datafile/system.256.624752397 conflicts with a file used by the target database
Bellow is my init file of standby instance:
*.audit_file_dest='/oracle/admin/ars_stb/adump'
*.background_dump_dest='/oracle/admin/ars_stb/bdump'
*.core_dump_dest=/oracle/admin/ARS_STB/cdump
*.user_dump_dest='/oracle/admin/ars_stb/udump'
*.cluster_database_instances=2
*.cluster_database=false
*.db_unique_name=ars_stb
*.instance_name=ars_stb
*.compatible='10.2.0.3.0'
*.control_files='+ARS_DAT1/ars/controlfile/current.260.624761147','+ARS_DAT6/ars/controlfile/current.269.624761147'#Restore Controlfile
*.db_block_size=8192
*.db_create_file_dest='+ARS_DAT1'
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='ars'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=ars_stbXDB)'
*.job_queue_processes=10
*.local_listener='LISTENERS_ARS'
*.log_archive_dest_1='LOCATION=+ARS_ARCH MANDATORY'
*.log_archive_format='ars%t_%s_%r.arc'
*.open_cursors=300
*.pga_aggregate_target=3145728000
*.processes=150
*.remote_listener='LISTENERS_ARS'
*.remote_login_passwordfile='exclusive'
*.sga_target=8388608000
*.thread=1
*.undo_management='AUTO'
*.undo_retention=3600
*.undo_tablespace=UNDOTBS1
*.log_archive_config='dg_config=(ARS_STB,ARS)'
*.log_archive_dest_2='service=ARS1 valid_for=(online_logfiles,primary_role) db_unique_name=ARS'
*.db_file_name_convert= '+DAT_ARS1/ars/','+DAT_ARS1/ars_stb/',
'+DAT_ARS2/ars/','+DAT_ARS2/ars_stb/',
'+DAT_ARS3/ars/','+DAT_ARS3/ars_stb/',
'+DAT_ARS4/ars/','+DAT_ARS4/ars_stb/',
'+DAT_ARS5/ars/','+DAT_ARS5/ars_stb/',
'+DAT_ARS6/ars/','+DAT_ARS6/ars_stb/',
'+DAT_ARS7/ars/','+DAT_ARS7/ars_stb/',
'+DAT_ARS8/ars/','+DAT_ARS8/ars_stb/',
'+DAT_ARS9/ars/','+DAT_ARS9/ars_stb/',
'+DAT_ARS10/ars/','+DAT_ARS10/ars_stb/',
'+DAT_ARS11/ars/','+DAT_ARS11/ars_stb/',
'+DAT_ARS12/ars/','+DAT_ARS12/ars_stb/',
'+DAT_ARS13/ars/','+DAT_ARS13/ars_stb/'
*.log_file_name_convert='+DAT_ARCH/ars/','+DAT_ARCH/ars_stb/'
*.standby_file_management=auto
*.fal_server='ARS1','ARS2'
*.fal_client='ARS_STB'
*.service_names='ARS_STB'
Thanks in advance

A big mistake, sorry
The correct convert parameters must be:
*.db_file_name_convert= '+ARS_DAT1/ARS/','+ARS_DAT1/ARS_STB/',
'+ARS_DAT2/ARS/','+ARS_DAT2/ARS_STB/',
'+ARS_DAT3/ARS/','+ARS_DAT3/ARS_STB/',
'+ARS_DAT4/ARS/','+ARS_DAT4/ARS_STB/',
'+ARS_DAT5/ARS/','+ARS_DAT5/ARS_STB/',
'+ARS_DAT6/ARS/','+ARS_DAT6/ARS_STB/',
'+ARS_DAT7/ARS/','+ARS_DAT7/ARS_STB/',
'+ARS_DAT8/ARS/','+ARS_DAT8/ARS_STB/',
'+ARS_DAT9/ARS/','+ARS_DAT9/ARS_STB/',
'+ARS_DAT10/ARS/','+ARS_DAT10/ARS_STB/',
'+ARS_DAT11/ARS/','+ARS_DAT11/ARS_STB/',
'+ARS_DAT12/ARS/','+ARS_DAT12/ARS_STB/',
'+ARS_DAT13/ARS/','+ARS_DAT13/ARS_STB/'
*.log_file_name_convert='+DAT_ARCH/ARS/','+DAT_ARCH/ARS_STB/'

Similar Messages

RMAN-05001: auxiliary filename

I am trying to duplicate a database using rman nocatalog on local host. I have set the convert file names to db_file_name_convert and log_file_name_convert in PFILE to AUXILIARY instance.
when I execute the duplicate command in Rman I do get this error..
RUN
allocate auxiliary channel c1 DEVICE TYPE disk;
DUPLICATE TARGET DATABASE to "RMAN"
PFILE=C:\oracle\ora92\database\INITrman.ORA
LOGFILE
GROUP 1 ('C:\ORACLE\ORADATA\RMAN\REDO01.RDO') SIZE 102400K REUSE,
GROUP 2 ('C:\ORACLE\ORADATA\RMAN\REDO02.RDO') SIZE 102400K REUSE,
GROUP 3 ('C:\ORACLE\ORADATA\RMAN\REDO03.RDO') SIZE 102400K REUSE;
RMAN-05001: auxiliary filename C:\ORACLE\ORADATA\LOCAL\REDO03.RDO conflicts with
I saw the document http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmdupdb.htm#441628 but i don't know what is the problem.
SO: Xp
DB: 9.2.0.1

---INITlocal.ora
*.aq_tm_processes=1
*.background_dump_dest='C:\oracle\admin\local\bdump'
*.compatible='9.2.0.0.0'
*.control_files='C:\oracle\oradata\local\CONTROL01.CTL','C:\oracle\oradata\local\CONTROL02.CTL','C:\oracle\oradata\local\CONTROL03.CTL'
*.core_dump_dest='C:\oracle\admin\local\cdump'
*.db_block_size=8192
*.db_cache_size=25165824
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='local'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=localXDB)'
*.fast_start_mttr_target=300
*.hash_join_enabled=TRUE
*.instance_name='local'
*.java_pool_size=33554432
*.job_queue_processes=10
*.large_pool_size=8388608
*.log_archive_start=TRUE
*.open_cursors=300
*.pga_aggregate_target=25165824
*.processes=150
*.query_rewrite_enabled='FALSE'
*.remote_login_passwordfile='EXCLUSIVE'
*.shared_pool_size=50331648
*.sort_area_size=524288
*.star_transformation_enabled='FALSE'
*.timed_statistics=TRUE
*.undo_management='AUTO'
*.undo_retention=10800
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\admin\local\udump'
--INITrman.ora
*.aq_tm_processes=1
*.background_dump_dest='C:\oracle\admin\rman\bdump'
*.compatible='9.2.0.0.0'
*.control_files='C:\oracle\oradata\rman\CONTROL01.CTL','C:\oracle\oradata\rman\CONTROL02.CTL','C:\oracle\oradata\rman\CONTROL03.CTL'
*.core_dump_dest='C:\oracle\admin\rman\cdump'
*.db_block_size=8192
*.db_cache_size=25165824
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='rman'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=rmanXDB)'
*.fast_start_mttr_target=300
*.hash_join_enabled=TRUE
*.instance_name='rman'
*.java_pool_size=33554432
*.job_queue_processes=10
*.large_pool_size=8388608
*.log_archive_start=TRUE
*.open_cursors=300
*.pga_aggregate_target=25165824
*.processes=150
*.query_rewrite_enabled='FALSE'
*.remote_login_passwordfile='EXCLUSIVE'
*.shared_pool_size=50331648
*.sort_area_size=524288
*.star_transformation_enabled='FALSE'
*.timed_statistics=TRUE
*.undo_management='AUTO'
*.undo_retention=10800
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\admin\rman\udump'
*.db_file_name_convert=('C:\ORACLE\ORADATA\LOCAL\','C:\ORACLE\ORADATA\RMAN\')
*.log_file_name_convert=('C:\ORACLE\ORADATA\LOCAL\','C:\ORACLE\ORADATA\RMAN\')
--Target and Aux are on same machine
--RMAN command
RUN
allocate auxiliary channel c1 DEVICE TYPE disk;
DUPLICATE TARGET DATABASE to "RMAN"
PFILE=C:\oracle\ora92\database\INITrman.ORA;
LOGFILE
GROUP 1 ('C:\ORACLE\ORADATA\RMAN\REDO01.RDO') SIZE 102400K REUSE,
GROUP 2 ('C:\ORACLE\ORADATA\RMAN\REDO02.RDO') SIZE 102400K REUSE,
GROUP 3 ('C:\ORACLE\ORADATA\RMAN\REDO03.RDO') SIZE 102400K REUSE;
I follow "Preparing the RMAN DUPLICATE Auxiliary Instance: Basic Steps".
I think the problem is in LOG_FILE_NAME_CONVERT or the logfile clause to convert the online redo log filenames
Message was edited by:
juanudo

RMAN-05001 auxiliary .... conflicts with a file used by the target database

I can´t recreate my physical standby.
It worked in the past.
Now I reinstalled the 3 standbyclients.
Copied the spfile from the primary - modified the entries and did a rman backup.
But when issuing the duplicate database command - it comes up with the error above
SPFILE standyby db:
*.db_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
*.log_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
Starting restore at 15-APR-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/stage/33lb65n2_1_1
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/oracle/stage/33lb65n2_1_1 tag=TAG20100415T102434
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:11
output filename=+REDO1/stdy/controlfile/current.262.716293055
output filename=+REDO2/stdy/controlfile/backup.262.716293055
Finished restore at 15-APR-10
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/15/2010 10:31:46
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename DATA/prim/datafile/system.262.715097535 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.263.715097499 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs3.269.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs2.270.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/example.272.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/users.268.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.273.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs1.271.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/system.264.710521021 conflicts with a file used by the target database+

Hi ,
I feel you are using ASM but still check the below details:
Cause
Production and Auxiliary have same directory structure and are running on two different machines. RMAN must be told not check that the target datafiles are sharing the same names as the duplicated files being created. Otherwise, the following errors will be returned:
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_03.dbf
conflicts with a file used by the target database
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_02.dbf
Solution
To implement the solution, please use nofilenamecheck in syntax as follows:
1. Connect to Target, auxiliary, and rman catalog and
2. use script as
run{
set until time "to_date('2005/09/17 14:00:00','yyyy/mm/dd HH24:MI:SS')";
allocate auxiliary channel aux1 type 'sbt_tape';
allocate auxiliary channel aux2 type 'sbt_tape';
duplicate target database for standby dorecover nofilenamecheck;
Make sure to use auxiliary type of channel so RMAN restore take place at auxiliary database.
Thanks,
Rafi.
http://rafioracledba.blogspot.com/

Auxiliary filename conflicts with a file used by the target database

Hi,
I am using RMAN backup to duplicate my prod database.
My database is 10g on Linux.
My RMAN script is like this
connect auxiliary /;
connect catalog rman/rman@catalog;
connect target sys/sys@prod;
sql "alter session set optimizer_mode=RULE";
run {
allocate auxiliary channel dup1 type disk;
allocate auxiliary channel dup2 type disk;
allocate auxiliary channel dup3 type disk;
set newname for datafile 1 to '/d05/u08/oracle/qadata/system01.dbf';
set newname for datafile 2 to '/d05/u08/oracle/qadata/system02.dbf';
set newname for datafile 3 to '/d05/u08/oracle/qadata/system03.dbf';
set newname for tempfile 1 to '/d05/u09/oracle/qadata/temp01.dbf';
set newname for tempfile 2 to '/d05/u09/oracle/qadata/temp02.dbf';
set newname for tempfile 3 to '/d05/u09/oracle/qadata/temp03.dbf';
set newname for tempfile 4 to '/d05/u09/oracle/qadata/temp04.dbf';
duplicate target database to qa logfile
group 1 ('/d05/u09/oracle/qadata/log1a.log',
'/d05/u09/oracle/qadata/log1b.log') size 50m,
group 2 ('/d05/u09/oracle/qadata/log2a.log',
'/d05/u09/oracle/qadata/log2b.log') size 50m,
group 3 ('/d05/u09/oracle/qadata/log3a.log',
'/d05/u09/oracle/qadata/log3b.log') size 50m;
I am getting the following error in the middle
Starting Duplicate Db at 18-SEP-10
released channel: dup1
released channel: dup2
released channel: dup3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/18/2010 11:32:07
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename /db01/u08/oracle/proddata/GRCM.dbf conflicts with a file used by the target database
Recovery Manager complete.
Previously the duplicate db was successful, but now it is giving error.
How can I solve this.
Thanks,
Kavitha

5001, 1, "auxiliary file name %s conflicts with a file used by the target database"
// *Cause: RMAN is attempting to use the specified file name as a restore
//         destination in the auxiliary database, but this name is already
//         in use by the target database.
// *Action: Use the CONFIGURE AUXNAME command to specify a name for the data
//          file that does not conflict with a file name in use by the
//          target db.

Auxiliary filename conflict - duplicate command

Hi,
We want to duplicate our production database (repos) from machine wmd-portal to auxiliary database (reposdup) of machine vmcdemo6.
Following are the command and error message:
Command:
RMAN> duplicate target database to reposdup;
Error message:
RMAN-05001: auxiliary filename C:\IASINFRA\ORADATA\REPOS\UNDOTBS01.DBF conflicts
with a file used by the target database
init.ora of auxiliary instance contains the following lines:
DB_FILE_NAME_CONVERT=(\\Wmd-portal\iasInfra\oradata\repos,\\vmcdev6\oracle\oradata\reposdup)
LOG_FILE_NAME_CONVERT=("\\Wmd-portal\iasInfra\oradata\repos","\\vmcdev6\oracle\oradata\reposdup")
Why are we getting a filename conflict?
We started the database using the following command:
sql> startup nomount pfile=c:\oracle\admin\reposdup\pfile\init.ora....
Thanks,
Karthik
ps: RMAN executable of wmd-portal was used.

Tedious work around is to use "set auxname ..." for each datafile and use "logfile clause" of duplicate command as below:
duplicate target database to reposdup
pfile='\\vmcdev6\oracle\admin\reposdup\pfile\init.ora' logfile GROUP 1('\\vmcdev\oracle\oradata\reposdup\redo01_1.f','\\vmcdev6\oracle\oradata\reposdup\redo01_2.f') size 200K,
GROUP 2
('\\vmcdev6\oracle\oradata\reposdup\redo02_1.f','\\vmcdev6\oracle\oradata\reposdup\redo02_2.f') size 200K,
GROUP 3
('\\vmcdev6\oracle\oradata\reposdup\redo03_1.f','\\vmcdev6\oracle\oradata\reposdup\redo03_2.f') size 200K reuse;
Seems to work.
I thought it was a precedence problem. However setting the auxname of each datafile to null doesn't work. Does anyone have a clue?
I use RMAN 9.0
Thanks,
karthik

RMAN-05001 - without files data

I dublicate DB prod host1 on prod host2. On host2 - no files data. RMAN return error - RMAN-05001: auxiliary filename /ora_oebs/data/u01/APPS_TS_MEDIA10.dbf conflicts with a file used by the target database.
RMAN returns 05001 pay no regard to presence of the files data ?

From Oracle error messages book:
RMAN-05001 auxiliary filename string conflicts with a file used by the target
database
Cause: RMAN is attempting to use the specified file name as a restore
destination in the auxiliary database, but this name is already in use by the
target database.
Action: Use the SET AUXNAME command to specify a name for the datafile
that does not conflict with a file name in use by the target database.
Are target & auxiliary databases on the same host (machine)?

RMAN-05001 - RMAN-03002 | Duplicating Database fails | Redo-Logs

Sorry guys,
first of all...my english is the worsteds you´ve ever seen...
I got some kind of problem using rman duplicating a DB called cs2t into cs2b.
Starting Duplicate Db at 17.05.2006 07:54:10
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/17/2006 07:54:10
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo05.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo04.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo03.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo02.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo01.log conflicts with a file used by the target database
Recovery Manager complete.
Therefore I found on metalink some informations about using UNTIL TIME.
I´ve tryed it....but now...there are some other erros on my rman.log
executing command: SET until clause
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/17/2006 08:22:14
ORA-01830: date format picture ends before converting entire input string
Recovery Manager complete.
and now: no ideas anymore...i´ve googled for it about 3hours...nothing found....may anybody help me - please?
P.S. I hope you´ll understand anything i´ve wrote into this message ;-)

hi,
you have to use db_file_name_convert and db_log-filename_convert parameter in the auxiliary database parameter file and use nofilenamecheck parameter with the duplicate command.
This is also recommended that you create new redo og files for auxiliary databse just like --
RMAN> run{
2> allocate auxiliary channel c1 device type disk;
3> duplicate target database to prod1 pfile='c:\oracle\ora92\database\initprod1.ora'
4> logfile 'c:\oracle\oradata\prod1\redo01.log' size 50m,
5> 'c:\oracle\oradata\prod1\redo02.log' size 50m,
6> 'c:\oracle\oradata\prod1\redo03.log' size 50m ;}
i hope it solve your problem..
Navneet

RMAN-06010: error while looking up datafile: 82

Iam building dataguard - Physical Standby database by using the RMAN duplicate command and we are not using the recovery catalog but control file.
Iam getting the following error while running the duplicate command.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";
RMAN-06010: error while looking up datafile: 82
Actually we dropped the datafile(tablespace) before taken the backup but it is giving error though we are using the latest control file.
I do not see this file is available in the database as we dropped it successfully.
Could some one let me know what could be the problem and how to resolve it.
Your early response is greatly appreciated.
Note:
backup script -- It went successfully.
# Script to be used to backup the production in preparation of creating a DataGuard instance
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting backup on O01FLX3"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/full_backup_run_$dt.log
connect target /
configure device type disk clear;
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run{
change archivelog all validate;
backup current controlfile for standby format '/tmp/stby_snapcf_O01FLX3.f';
backup database format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.bak';
sql 'alter system archive log current';
backup archivelog all format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.arc';
EXIT
EOF
duplicate Script:
#!/bin/ksh
# Script to create standby database for production.
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting dataguard instance on O01FLX3DR"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/cr_stdby_O01FLX3$dt.log
connect target /
connect auxiliary sys/xxxxxx@O01FLX3DR
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run {
set until time "to_date('20080217:19:00', 'YYYYMMDD:HH24:MI')";
duplicate target database for standby dorecover nofilenamecheck;
exit;
EOF
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";

Thank you for your reply. Actually Iam not renaming the datafile but building the
dataguard instance and some how control file is looking for old datafile that was deleted.
Actually both primary and dataguard instances are running on 10.2.0.3 . Oracle control file is listing the datafile 82 as old deleted file, while building the dataguard.
---- This file was deleted long time back but still oracle control file is looking for this file while building the dataguard. Iam using the latest control file.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3"
When I listed the datafile 82, it is showing the correct datafile.
RMAN> list backup of datafile 82;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
50234 Incr 2 26.93M DISK 00:04:03 18-FEB-08
BP Key: 101470 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51757_1_20080218_647031779.bak
List of Datafiles in backup set 50234
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953177017970 18-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
BS Key Type LV Size Device Type Elapsed Time Completion Time
50334 Incr 2 27.76M DISK 00:04:16 19-FEB-08
BP Key: 101587 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51857_1_20080219_647119328.bak
List of Datafiles in backup set 50334
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953257549488 19-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
So Iam thinking that there should be a problem in control file and let me know how to resolve it.
Please let me know if you have any questions.
Thanks for your help.
Suresh.D

RMAN's commands to check the datafiles for any sort of corruptions

what are RMAN's commands to check the datafiles for any sort of corruptions

RMAN is check database or backups here? i think its checking backups? and
You mean to say that its not checking the datafiles but the backup of them for corruption is it?If this is what you meant than I guess you haven't read teh link that I referred.From there,
When performing a BACKUP... VALIDATE, RMAN reads the files to be backed up in their entirety, as it would during a real backup. It does not, however, actually produce any backup sets or image copies.This command wont check the backups and neither its taking a backup.Its checking it for corruptions.
[i]
RMAN>backup validate database ;
not working when db is in no-archivelog mode
Are you trying to run it in the open stage ? If you are in Noarchive mode, you can't run backup related commands in open stage.Run it in the mount stage.
Aman....

Rman connect auxiliary displays wrong database

I am trying to use the new 11g duplicate from active database feature. I am running into the following error and can't figure out what is wrong.
RMAN> connect target sys/xxxxx@ebsprod
connected to target database: EBSPROD (DBID=3420264532)
RMAN> connect auxiliary sys/xxxxx@abc
connected to auxiliary database: EBSPROD (not mounted)
RMAN>
The auxiliary database shows the same DB name as the target. The correct auxiliary name is ABC in this case. The DB is started in nomount with the correct name. The new init.ora is correct as well. What is it looking at? Any help would be greatly appreciated.

The correct auxiliary name is ABC in this case. The DB is started in nomount with the correct name. The new init.ora is correct as well.show us the requested db_name parameter, init.ora and tnsnames.ora
RMAN displays the value of db_name
db_unique_name and instance_name doesnt matter here

RMAN Duplicate DB fails to restore datafile created during backup.

Database is 9i.
Performing duplicate database using rman on seperate host.
Reason of failure is , there were datafiles created during backup. Question is , Is there a workaround to perform duplicate database to work.
Error :
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/16/2007 14:42:44
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 791 found to restore
RMAN-06023: no backup or copy of datafile 790 found to restore
RMAN-06023: no backup or copy of datafile 789 found to restore
RMAN-06023: no backup or copy of datafile 788 found to restore
RMAN-06023: no backup or copy of datafile 787 found to restore
RMAN-06023: no backup or copy of datafile 786 found to restore
Backup Date is : 23rd Nov to 26th Nov
Datafile created between backup period are :
786 /oracle/prod/proddata17/btabd_322/btabd.data322 Nov-25-2007 02:58:38 AM
787 /oracle/prod/proddata17/btabd_323/btabd.data323 Nov-25-2007 03:06:02 AM
788 /oracle/prod/proddata17/btabd_324/btabd.data324 Nov-25-2007 03:17:48 AM
789 /oracle/prod/proddata17/btabd_325/btabd.data325 Nov-25-2007 03:26:50 AM
790 /oracle/prod/proddata17/btabd_326/btabd.data326 Nov-25-2007 03:32:31 AM
791 /oracle/prod/proddata17/btabd_327/btabd.data327 Nov-25-2007 03:39:59 AM
Restore Script :
rman TARGET dtbackup/dt0dmin@prod CATALOG rman_prd/rman_prd@rcat_db connect auxiliary /
run {
set until time = "TO_DATE('11/26/2007 10:30:00','mm/dd/yyyy hh24:mi:ss')";
allocate auxiliary channel aux1 type 'SBT_TAPE' PARMS="BLKSIZE=262144";
DUPLICATE TARGET DATABASE TO DUP ;
}

I think there is no workaround and this is expected behavior - atleast till 10.2. If you refer oracle documentation, it says that it requires target database in either MOUNT or OPEN stage to duplicate database using RMAN. So RMAN will get current physical structure information about target database from its control file and when any file is not there in the backup, it will give error. Only way to resolve this is to take backup of these datafiles through RMAN either as backupset or copy. ( I think oracle can take hint from here and make RMAN database duplication possible for which backup is not available - its a small change in code - if backup not found, then start taking backup. Already in 11g, during RMAN duplication, RMAN can use backup from other server)

RMAN - Using fileperset = 1 and want datafile name to appear in piece name

Environment: 10.2.0.4 on HP-UX
Hi guys,
One of my many problems with Netbackup is the inablity to trace backups as they get duplicated around the environment
For our FULL backups, our backup script uses filesperset = 1 which means every datafile is backed up into its own piece
We use rman format parameters %s %U etc to label our pieces. What would really help us would be if we could have the datafile name appear in the name of the backup piece
Is that possible?
this is a sample extract of out script
SEND 'NB_ORA_POLICY=Oracle_${DATABASE_NAME},NB_ORA_SCHED=${NB_ORA_SCHED}';
#------ Backup Full Database
backup incremental level 0
database
filesperset 1
format 'Full_DB_${DATABASE_NAME}_Weekly_Datafiles_%s:%t:%p.rman_backup'
include current controlfile
tag Full_DB_NetBackup;
(note: I may be missing something fundamental here and being stupid, it's been known)

Never tried but you can try with this
*%f - Specifies the absolute file number*.
I just checked, it works. It wll give you file number not file name though.
and also with
*%N - You can have tablespace name with it*. This would be little more helpful.
You can combine both to get the file number and tablespace name together. I got the output like this.
FULL_DB_2::UNDOTBS1.RMAN
This means file *2* of undo tablespace. I used this format string format 'E:\Full_DB_%f::%N.rman'
Edited by: TSharma on Mar 5, 2013 11:57 AM

RMAN can't SET NEWNAME for datafiles added after Level 1

Version: 11.2.0.3
Platform : Solaris 10
I have the most recent Level 0 , Level 1 and post-L1 Archive logs of the source DB.
I am trying restore, recover in a different machine using plain RMAN (not RMAN DUPLICATE) into a new datafile location.
After the Level 1 backup was taken, 2 datafiles (namdata01.dbf, finaldata01.dbf) were added ( this got 'recorded' on the subsequent post-L1 archivelogs )
Before I ran restore and recover, I restored the latest control file from the most recent L1
RMAN> restore controlfile from '/u01/CATALOGTST/rmanBkpPieces/SNTCDEV_L1_0cnjqk54_1_1_20120829.rmbk' ;Understandably, this control file doesn't have info about the 2 datafiles added after L1 .Wish I could restore control file from archive log :)
So, I cataloged the archive logs as well using CATALOG command.
RMAN> catalog start with '/u01/CATALOGTST/rmanBkpPieces';
using target database control file instead of recovery catalog
searching for all files that match the pattern /u01/CATALOGTST/rmanBkpPieces
List of Files Unknown to the Database
=====================================
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_full_07njqj6j_1_1_20120828.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_full_08njqj8u_1_1_20120828.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_L1_0bnjqk3d_1_1_20120829.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_L1_0cnjqk54_1_1_20120829.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/arch_1_13_790513173.arc
File Name: /u01/CATALOGTST/rmanBkpPieces/arch_1_14_790513173.arc
File Name: /u01/CATALOGTST/rmanBkpPieces/arch_1_15_790513173.arc
File Name: /u01/CATALOGTST/rmanBkpPieces/06njqj6h_1_1
File Name: /u01/CATALOGTST/rmanBkpPieces/09njqj90_1_1
File Name: /u01/CATALOGTST/rmanBkpPieces/0anjqk3b_1_1
File Name: /u01/CATALOGTST/rmanBkpPieces/0dnjqk56_1_1
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_full_07njqj6j_1_1_20120828.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_full_08njqj8u_1_1_20120828.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_L1_0bnjqk3d_1_1_20120829.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/SNTCDEV_L1_0cnjqk54_1_1_20120829.rmbk
File Name: /u01/CATALOGTST/rmanBkpPieces/arch_1_13_790513173.arc                         -------------------> arch logs that contain info on the new datafiles
File Name: /u01/CATALOGTST/rmanBkpPieces/arch_1_14_790513173.arc                         -------------------> arch logs that contain info on the new datafiles
File Name: /u01/CATALOGTST/rmanBkpPieces/arch_1_15_790513173.arc                          -------------------> arch logs that contain info on the new datafiles
File Name: /u01/CATALOGTST/rmanBkpPieces/06njqj6h_1_1
File Name: /u01/CATALOGTST/rmanBkpPieces/09njqj90_1_1
File Name: /u01/CATALOGTST/rmanBkpPieces/0anjqk3b_1_1
File Name: /u01/CATALOGTST/rmanBkpPieces/0dnjqk56_1_1
RMAN> EXITDuring Recovery , RMAN applied the archive logs and managed to create the datafiles successfully. But it can't restore the datafiles to the new location specified in the SET NEWNAME location. Luckily , I had created the original path and these 2 datafiles got restored there.
RMAN can't seem enforce SET NEWNAME for datafiles added after Level 1 backup despite cataloging.
Does SET NEWNAME .... thing work only for RESTORE ?
Log of restore and recover
$ cat restore-recover.txt
run
set newname for database to '/u01/app/CLONE1/oradata/sntcdev/%b' ;
set newname for tempfile '/u01/app/oradata/sntcdev/temp01.dbf' to '/u01/app/CLONE1/oradata/sntcdev/temp01.dbf' ;
restore database;
switch datafile all;
switch tempfile all;
recover database;
$
$ rman target / cmdfile=restore-recover.txt
Recovery Manager: Release 11.2.0.3.0 - Production on Sun Sep 16 21:27:49 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SNTCDEV (DBID=2498462290, not open)
RMAN> run
2> {
3> set newname for database to '/u01/app/CLONE1/oradata/sntcdev/%b' ;
4> set newname for tempfile '/u01/app/oradata/sntcdev/temp01.dbf' to '/u01/app/CLONE1/oradata/sntcdev/temp01.dbf' ;
5> restore database;
6> switch datafile all;
7> switch tempfile all;
8> recover database;
9> }
10>
11>
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 16-SEP-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/CLONE1/oradata/sntcdev/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/CLONE1/oradata/sntcdev/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/CLONE1/oradata/sntcdev/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/CLONE1/oradata/sntcdev/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/CLONE1/oradata/sntcdev/example01.dbf
channel ORA_DISK_1: restoring datafile 00006 to /u01/app/CLONE1/oradata/sntcdev/cisdata01.dbf
channel ORA_DISK_1: reading from backup piece /u01/RMAN_bkp/BKP_sntcdev/SNTCDEV_full_07njqj6j_1_1_20120828.rmbk
channel ORA_DISK_1: errors found reading piece handle=/u01/RMAN_bkp/BKP_sntcdev/SNTCDEV_full_07njqj6j_1_1_20120828.rmbk
channel ORA_DISK_1: failover to piece handle=/u01/CATALOGTST/rmanBkpPieces/SNTCDEV_full_07njqj6j_1_1_20120828.rmbk tag=TAG20120828T234834
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
Finished restore at 16-SEP-12
datafile 1 switched to datafile copy
input datafile copy RECID=8 STAMP=794179772 file name=/u01/app/CLONE1/oradata/sntcdev/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=9 STAMP=794179772 file name=/u01/app/CLONE1/oradata/sntcdev/sysaux01.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=10 STAMP=794179772 file name=/u01/app/CLONE1/oradata/sntcdev/undotbs01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=11 STAMP=794179772 file name=/u01/app/CLONE1/oradata/sntcdev/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=12 STAMP=794179772 file name=/u01/app/CLONE1/oradata/sntcdev/example01.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=13 STAMP=794179772 file name=/u01/app/CLONE1/oradata/sntcdev/cisdata01.dbf
renamed tempfile 1 to /u01/app/CLONE1/oradata/sntcdev/temp01.dbf in control file
Starting recover at 16-SEP-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u01/app/CLONE1/oradata/sntcdev/system01.dbf
destination for restore of datafile 00002: /u01/app/CLONE1/oradata/sntcdev/sysaux01.dbf
destination for restore of datafile 00003: /u01/app/CLONE1/oradata/sntcdev/undotbs01.dbf
destination for restore of datafile 00004: /u01/app/CLONE1/oradata/sntcdev/users01.dbf
destination for restore of datafile 00005: /u01/app/CLONE1/oradata/sntcdev/example01.dbf
destination for restore of datafile 00006: /u01/app/CLONE1/oradata/sntcdev/cisdata01.dbf
channel ORA_DISK_1: reading from backup piece /u01/RMAN_bkp/BKP_sntcdev/SNTCDEV_L1_0bnjqk3d_1_1_20120829.rmbk
channel ORA_DISK_1: errors found reading piece handle=/u01/RMAN_bkp/BKP_sntcdev/SNTCDEV_L1_0bnjqk3d_1_1_20120829.rmbk
channel ORA_DISK_1: failover to piece handle=/u01/CATALOGTST/rmanBkpPieces/SNTCDEV_L1_0bnjqk3d_1_1_20120829.rmbk tag=TAG20120829T000356
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
starting media recovery
archived log for thread 1 with sequence 13 is already on disk as file /u01/CATALOGTST/rmanBkpPieces/arch_1_13_790513173.arc
archived log for thread 1 with sequence 14 is already on disk as file /u01/CATALOGTST/rmanBkpPieces/arch_1_14_790513173.arc
archived log for thread 1 with sequence 15 is already on disk as file /u01/CATALOGTST/rmanBkpPieces/arch_1_15_790513173.arc
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=12
channel ORA_DISK_1: reading from backup piece /u01/CATALOGTST/rmanBkpPieces/0dnjqk56_1_1
channel ORA_DISK_1: piece handle=/u01/CATALOGTST/rmanBkpPieces/0dnjqk56_1_1 tag=TAG20120829T000454
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/archLogs/arch_1_12_790513173.arc thread=1 sequence=12
archived log file name=/u01/CATALOGTST/rmanBkpPieces/arch_1_13_790513173.arc thread=1 sequence=13
creating datafile file number=7 name=/u01/app/oradata/sntcdev/namdata01.dbf
archived log file name=/u01/CATALOGTST/rmanBkpPieces/arch_1_13_790513173.arc thread=1 sequence=13
archived log file name=/u01/CATALOGTST/rmanBkpPieces/arch_1_14_790513173.arc thread=1 sequence=14
archived log file name=/u01/CATALOGTST/rmanBkpPieces/arch_1_15_790513173.arc thread=1 sequence=15
creating datafile file number=8 name=/u01/app/oradata/sntcdev/finaldata01.dbf
archived log file name=/u01/CATALOGTST/rmanBkpPieces/arch_1_15_790513173.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=16
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/16/2012 21:29:51
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 16 and starting SCN of 1004015
Recovery Manager complete.
$
$
$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Sun Sep 16 21:30:04 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select name from v$datafile;
NAME
/u01/app/CLONE1/oradata/sntcdev/system01.dbf
/u01/app/CLONE1/oradata/sntcdev/sysaux01.dbf
/u01/app/CLONE1/oradata/sntcdev/undotbs01.dbf
/u01/app/CLONE1/oradata/sntcdev/users01.dbf
/u01/app/CLONE1/oradata/sntcdev/example01.dbf
/u01/app/CLONE1/oradata/sntcdev/cisdata01.dbf
/u01/app/oradata/sntcdev/namdata01.dbf           ----------------------> restored to old location ignoring SET NEWNAME ....
/u01/app/oradata/sntcdev/finaldata01.dbf         ----------------------> restored to old location ignoring SET NEWNAME ....
8 rows selected.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
$ cd /u01/app/oradata/sntcdev            # -----------------------------> the old location
$
$ ls -alrt
total 243924
drwxr-xr-x   3 oracle   oinstall     512 Aug 5 10:55 ..
drwxr-xr-x   2 oracle   oinstall     512 Sep 16 20:59 .
-rw-r-----   1 oracle   oinstall 104865792 Sep 16 21:29 namdata01.dbf
-rw-r-----   1 oracle   oinstall 19931136 Sep 16 21:29 finaldata01.dbf

RMAN> run
2> {
3> set newname for database to '/u01/app/CLONE1/oradata/sntcdev/%b' ;
4> set newname for tempfile '/u01/app/oradata/sntcdev/temp01.dbf' to '/u01/app/CLONE1/oradata/sntcdev/temp01.dbf' ;
5> restore database;
6> switch datafile all;
7> switch tempfile all;
8> recover database;
9> }RMAN executes the commands in the run block stepwise. In your case, starting from "set newname for database..." and lastly executing "recover database...".
Let me interpret it for you.
1. You restored the controlfile from the L1 backup which does not have any information about the 2 newly added datafiles. You cataloged the backuppieces and the archives to this controlfile, which means that the controlfile would now be aware that the required backups and archives are in this cataloged location.
2. You set newname for database to the desired location, thereby this command is executed restoring the database from the L0 and L1 backups. (These 2 backups do not have any information about the newly added datafiles and hence the 2 files would still not be restored).
3. You execute restore database which restores the files from L0 and L1 backup.
4. Switch datafile all, this renames all the files that were restored in the previous steps to the desired name/location that was mentioned in step 2.
5. Recover database: This is where the archivelogs come into picture. The data in the archives would be created & recovered. The newly added datafiles are now created & recovered but RMAN does not go back to STEP 2 and STEP 4 to re-execute the commands in STEP2 and STEP4 to restore it to the desired location (STEP 2) and Rename it (STEP 4). The files will have to renamed later by moving them manually to the location that you require.
So, RMAN does not execute the SET NEWNAME for datafiles which were added after the backup as the information about these files do not exist in the RMAN backuppieces.

Error in Creation of Dataguard for RAC

My pfile of RAC looks like:
RACDB2.__large_pool_size=4194304
RACDB1.__large_pool_size=4194304
RACDB2.__shared_pool_size=92274688
RACDB1.__shared_pool_size=92274688
RACDB2.__streams_pool_size=0
RACDB1.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/RACDB/adump'
*.background_dump_dest='/u01/app/oracle/admin/RACDB/bdump'
*.cluster_database_instances=2
*.cluster_database=true
*.compatible='10.2.0.1.0'
*.control_files='+DATA/racdb/controlfile/current.260.627905745','+FLASH/racdb/controlfile/current.256.627905753'
*.core_dump_dest='/u01/app/oracle/admin/RACDB/cdump'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='+DATA/RACDB','+DATADG/RACDG'
*.db_name='RACDB'
*.db_recovery_file_dest='+FLASH'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=RACDBXDB)'
*.fal_client='RACDB'
*.fal_server='RACDG'
RACDB1.instance_number=1
RACDB2.instance_number=2
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(RACDB,RACDG)'
*.log_archive_dest_1='LOCATION=+FLASH/RACDB/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=RACDB'
*.log_archive_dest_2='SERVICE=RACDG VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=RACDG'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_format='%t_%s_%r.arc'
*.log_file_name_convert='+DATA/RACDB','+DATADG/RACDG'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_listener='LISTENERS_RACDB'
*.remote_login_passwordfile='exclusive'
*.service_names='RACDB'
*.sga_target=167772160
*.standby_file_management='AUTO'
RACDB2.thread=2
RACDB1.thread=1
*.undo_management='AUTO'
RACDB2.undo_tablespace='UNDOTBS2'
RACDB1.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/RACDB/udump'
My pfile of Dataguard Instance in nomount state looks like:
RACDG.__db_cache_size=58720256
RACDG.__java_pool_size=4194304
RACDG.__large_pool_size=4194304
RACDG.__shared_pool_size=96468992
RACDG.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/RACDG/adump'
*.background_dump_dest='/u01/app/oracle/admin/RACDG/bdump'
##*.cluster_database_instances=2
##*.cluster_database=true
*.compatible='10.2.0.1.0'
##*.control_files='+DATA/RACDG/controlfile/current.260.627905745','+FLASH/RACDG/controlfile/current.256.627905753'
*.core_dump_dest='/u01/app/oracle/admin/RACDG/cdump'
*.db_block_size=8192
*.db_create_file_dest='+DATADG'
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='+DATADG/RACDG','+DATA/RACDB'
*.db_name='RACDB'
*.db_recovery_file_dest='+FLASHDG'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=RACDGXDB)'
*.FAL_CLIENT='RACDG'
*.FAL_SERVER='RACDB'
*.job_queue_processes=10
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(RACDB,RACDG)'
*.log_archive_dest_1='LOCATION=+FLASHDG/RACDG/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=RACDG'
*.log_archive_dest_2='SERVICE=RACDB VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=RACDB'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.log_archive_format='%t_%s_%r.arc'
*.log_file_name_convert='+DATADG/RACDG','+DATA/RACDB'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
##*.remote_listener='LISTENERS_RACDG'
*.remote_login_passwordfile='exclusive'
SERVICE_NAMES='RACDG'
sga_target=167772160
standby_file_management='auto'
undo_management='AUTO'
undo_tablespace='UNDOTBS1'
user_dump_dest='/u01/app/oracle/admin/RACDG/udump'
DB_UNIQUE_NAME=RACDG
and here is what I am doing on the standby location:
[oracle@dg01 ~]$ echo $ORACLE_SID
RACDG
[oracle@dg01 ~]$ rman
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Jul 17 21:19:21 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect auxiliary /
connected to auxiliary database: RACDG (not mounted)
RMAN> connect target sys/xxxxxxx@RACDB
connected to target database: RACDB (DBID=625522512)
RMAN> duplicate target database for standby;
Starting Duplicate Db at 2007-07-17 22:27:08
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=156 devtype=DISK
contents of Memory Script:
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
Starting restore at 2007-07-17 22:27:10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /software/backup/ctl4.ctl
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/software/backup/ctl4.ctl tag=TAG20070717T201921
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:23
output filename=+DATADG/racdg/controlfile/current.275.628208075
output filename=+FLASHDG/racdg/controlfile/backup.268.628208079
Finished restore at 2007-07-17 22:27:34
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/17/2007 22:27:43
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/undotbs2.265.627906771 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/example.264.627905917 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/users.259.627905395 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/sysaux.257.627905385 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/undotbs1.258.627905395 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/system.256.627905375 conflicts with a file used by the target database
RMAN>
Any help to clear this error will be apprecited.......
Message was edited by:
Bal
null

Hi
Thanks everybody for helping me on this issue...........
As suggested, I had taken the parameter log_file_name_convert and db_file_name_convert out of my RAC primary database but still I am getting the same error.
Any help will be appriciated..............
SQL> show parameter convert
NAME TYPE VALUE
db_file_name_convert string
log_file_name_convert string
SQL>
oracle@dg01<3>:/u01/app/oracle> rman
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Jul 18 17:07:49 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect auxiliary /
connected to auxiliary database: RACDB (not mounted)
RMAN> connect target sys/xxx@RACDB
connected to target database: RACDB (DBID=625522512)
RMAN> duplicate target database for standby;
Starting Duplicate Db at 2007-07-18 17:10:53
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=156 devtype=DISK
contents of Memory Script:
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
Starting restore at 2007-07-18 17:10:54
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /software/backup/ctl5.ctr
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/software/backup/ctl5.ctr tag=TAG20070718T170529
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:33
output filename=+DATADG/racdg/controlfile/current.275.628208075
output filename=+FLASHDG/racdg/controlfile/backup.268.628208079
Finished restore at 2007-07-18 17:11:31
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/18/2007 17:11:43
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/undotbs2.265.627906771 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/example.264.627905917 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/users.259.627905395 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/sysaux.257.627905385 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/undotbs1.258.627905395 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/racdb/datafile/system.256.627905375 conflicts with a file used by the target database

Duplicate database from ASM to Non-ASM problem

Friends,
I am unable to duplicate the database from ASM TO Non-ASM,
OS: Linux AS4
Oracle version: 10.2.0.1
initAUXDB.ora parameters:
background_dump_dest=/u01/oracle/product/10.2.0/admin/auxdb/adump
core_dump_dest=/u01/oracle/product/10.2.0/admin/auxdb/cdump
background_dump_dest=/u01/oracle/product/10.2.0/admin/auxdb/bdump
user_dump_dest=/u01/oracle/product/10.2.0/admin/auxdb/udump
db_name=auxdb
undo_tablespace=undotbs1
undo_management=auto
undo_retention=900
db_block_size=8192
compatible=10.2.0.1
control_files='/u01/oracle/product/10.2.0/oradata/auxdb/control01.ctl'
db_file_name_convert=('+DATA','/u01/oracle/product/10.2.0/oradata/auxdb')
log_file_name_convert=('+DATA','/u01/oracle/product/10.2.0/oradata/auxdb')
db_create_file_dest='/u01/oracle/product/10.2.0/oradata/auxdb'
db_create_online_log_dest_1='/u01/oracle/product/10.2.0/oradata/auxdb'
My target database diskgroup info:
GROUP_NUMBER NAME SECTOR_SIZE BLOCK_SIZE STATE
1 DATA 512 4096 MOUNTED N
2 FLASH 512 4096 MOUNTED E
Please could you have look the following error:
type1:
Note: when I configure The log_file_name_convert=('+DATA') in initAUXDB.ora parameter file, the following error are occurring:
RMAN> run {
2> allocate auxiliary channel C1 device type disk;
3> duplicate target database to auxdb;
4> }
Starting Duplicate Db at 03-MAR-13
released channel: C1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/03/2013 14:43:05
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename +FLASH/prod/onlinelog/group_3.259.809008171 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +FLASH/prod/onlinelog/group_2.258.809008167 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +FLASH/prod/onlinelog/group_1.257.809008165 conflicts with a file used by the target database
type2:
when I configure The log_file_name_convert=('+FLASH') in initAUXDB.ora, again I am getting the following error:
RMAN> run {
2> allocate auxiliary channel C1 device type disk;
3> duplicate target database to auxdb;
4> }
allocated channel: C1
channel C1: sid=36 devtype=DISK
Starting Duplicate Db at 04-MAR-13
released channel: C1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/04/2013 08:37:10
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename +DATA/prod/onlinelog/group_3.263.809008169 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/prod/onlinelog/group_2.262.809008165 conflicts with a file used by the target database
RMAN-05001: auxiliary filename +DATA/prod/onlinelog/group_1.261.809008163 conflicts with a file used by the target database
Please suggest me to overcome the above errors.

Hi Mr.Rao,
Thank you for your reply..
I follwed as per as your query, but I am getting different error:
channel C1: starting datafile backupset restore
channel C1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/system.256.809008077 <---------here the directory structure is "/u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/" but I mention in initauxdb.ora parameter only "/u01/oracle/product/10.2.0/odata/auxdb/".
restoring datafile 00002 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/undotbs1.258.809008077
restoring datafile 00003 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/sysaux.257.809008077
restoring datafile 00004 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/users.259.809008077
channel C1: reading from backup piece +FLASH/prod/backupset/2013_03_04/nnndf0_tag20130304t072249_0.265.809162569
ORA-19870: error reading backup piece +FLASH/prod/backupset/2013_03_04/nnndf0_tag20130304t072249_0.265.809162569
ORA-19505: failed to identify file "+FLASH/prod/backupset/2013_03_04/nnndf0_tag20130304t072249_0.265.809162569"
ORA-17503: ksfdopn:2 Failed to open file +FLASH/prod/backupset/2013_03_04/nnndf0_tag20130304t072249_0.265.809162569
ORA-15001: diskgroup "FLASH" does not exist or is not mounte
failover to previous backup
channel C1: starting datafile backupset restore
channel C1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/system.256.809008077
restoring datafile 00002 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/undotbs1.258.809008077
restoring datafile 00003 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/sysaux.257.809008077
restoring datafile 00004 to /u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/users.259.809008077
channel C1: reading from backup piece /u01/backup/prod/df_t809162421_s24_p1
channel C1: restored backup piece 1
piece handle=/u01/backup/prod/df_t809162421_s24_p1 tag=TAG20130304T072021
channel C1: restore complete, elapsed time: 00:01:17
Finished restore at 04-MAR-13
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "AUXDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '/u01/oracle/product/10.2.0/oradata/auxdb/prod/onlinelog/group_1.261.809008163',
'/u01/oracle/product/10.2.0/oradata/auxdb/prod/onlinelog/group_1.257.809008165' ) SIZE 50 M REUSE,
GROUP 2 ( '/u01/oracle/product/10.2.0/oradata/auxdb/prod/onlinelog/group_2.262.809008165',
'/u01/oracle/product/10.2.0/oradata/auxdb/prod/onlinelog/group_2.258.809008167' ) SIZE 50 M REUSE,
GROUP 3 ( '/u01/oracle/product/10.2.0/oradata/auxdb/prod/onlinelog/group_3.263.809008169',
'/u01/oracle/product/10.2.0/oradata/auxdb/prod/onlinelog/group_3.259.809008171' ) SIZE 50 M REUSE
DATAFILE
'/u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/system.256.809008077'
CHARACTER SET WE8ISO8859P1
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=809171578 filename=/u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/undotbs1.258.809008077
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=809171578 filename=/u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/sysaux.257.809008077
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=809171578 filename=/u01/oracle/product/10.2.0/oradata/auxdb/prod/datafile/users.259.809008077
channel C1: starting archive log restore to default destination
channel C1: restoring archive log
archive log thread=1 sequence=12
channel C1: restoring archive log
archive log thread=1 sequence=13
channel C1: reading from backup piece /u01/backup/prod/al_t809162496_s26_p1
channel C1: restored backup piece 1
piece handle=/u01/backup/prod/al_t809162496_s26_p1 tag=TAG20130304T072136
channel C1: restore complete, elapsed time: 00:00:04
archive log filename=/u01/oracle/product/10.2.0/db_1/dbs/arch1_12_809008161.dbf thread=1 sequence=12
channel clone_default: deleting archive log(s)
archive log filename=/u01/oracle/product/10.2.0/db_1/dbs/arch1_12_809008161.dbf recid=2 stamp=809171585
archive log filename=/u01/oracle/product/10.2.0/db_1/dbs/arch1_13_809008161.dbf thread=1 sequence=13
channel clone_default: deleting archive log(s)
archive log filename=/u01/oracle/product/10.2.0/db_1/dbs/arch1_13_809008161.dbf recid=1 stamp=809171583
channel C1: starting archive log restore to default destination
channel C1: restoring archive log
archive log thread=1 sequence=14
channel C1: reading from backup piece +FLASH/prod/backupset/2013_03_04/annnf0_tag20130304t072246_0.264.809162567
ORA-19870: error reading backup piece +FLASH/prod/backupset/2013_03_04/annnf0_tag20130304t072246_0.264.809162567
ORA-19505: failed to identify file "+FLASH/prod/backupset/2013_03_04/annnf0_tag20130304t072246_0.264.809162567"
ORA-17503: ksfdopn:2 Failed to open file +FLASH/prod/backupset/2013_03_04/annnf0_tag20130304t072246_0.264.809162567
ORA-15001: diskgroup "FLASH" does not exist or is not mounte
released channel: C1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/04/2013 09:53:11
RMAN-03015: error occurred in stored script Memory Script
RMAN-20506: no backup of archivelog found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 14 lowscn 542329 found to restore

RMAN-05001: auxiliary filename +ARS_DAT9/ars/datafile/arsystem1.259.6326886

Similar Messages

Maybe you are looking for