Rman conflict

Hai all,
When am runnign this script manually
run
backup database format 'D:\BKP\rman\PRO_DB_t%t_s%s_p%p';
backup current controlfile format 'D:\BKP\rman\PROD_CTRL_t%t_s%s_p%p';
crosscheck backup;
backup archivelog all format 'D:\BKP\rman\PROD_ARCH_t%t_s%s_p%p';
delete noprompt obsolete device type disk;
It works fine..
But when I schedule this using task scheduler in windows. am getting the following error :
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
The disk is empty and am the administrator and I have full access to this drive
Any idea ?
Kai

Hai all,
When am runnign this script manually
run
backup database format
'D:\BKP\rman\PRO_DB_t%t_s%s_p%p';
backup current controlfile format
'D:\BKP\rman\PROD_CTRL_t%t_s%s_p%p';
crosscheck backup;
backup archivelog all format
'D:\BKP\rman\PROD_ARCH_t%t_s%s_p%p';
delete noprompt obsolete device type disk;
It works fine..
But when I schedule this using task scheduler in
windows. am getting the following error :
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path
specified.
The disk is empty and am the administrator and I have
full access to this drive
Any idea ?
KaiIs d:\ a local drive or a mapped network drive?
Niall Litchfield
http://www.orawin.info/

Similar Messages

RMAN conflict with DBCA

We're currently transitioning to RMAN as a backup solution for our databases, but there seems to be a problem with some of the bases which has previously been backed up by the use of DBCA.
I've been following this tutorial; http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov002.htm
It goes swimmingly until I reach the point where I'm to restore the actual database. Firstly, this is the command used to take the actual backup:
run {
set controlfile autobackup format for device type disk to '${INC_DIR}/cf_%F';
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
backup
incremental level 0
tag ${SID}_level_0
filesperset 6
format '${INC_DIR}/df_t%t_s%s_p%p'
(database);
}Then the files that are generated are transferred to a new host through FTP, so there's no use of tape or NFS, but both machines run the same OS and Oracle version. As previously mentioned, the various spfile and control file restorations and modifications proceed without a hitch, it's towards the end of the tutorial the problem occurs when I attempt to restore the actual database. And mind you, this is on databases which are currently being backed up through the use of DBCA.
RUN
ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/data1/backup/rman/qcdash1/incremental/df_t%t_s%s_p%p';
ALLOCATE CHANNEL disk2 DEVICE TYPE DISK FORMAT '/data1/backup/rman/qcdash1/incremental/df_t%t_s%s_p%p';
# rename the datafiles and online redo logs
SET NEWNAME FOR DATAFILE 1 TO '/data1/oradata/qcdash1t/system01.dbf';
SET NEWNAME FOR DATAFILE 2 TO '/data1/oradata/qcdash1t/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 3 TO '/data1/oradata/qcdash1t/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 4 TO '/data1/oradata/qcdash1t/users01.dbf';
SET NEWNAME FOR DATAFILE 5 TO '/data1/oradata/qcdash1t/tdcom_data.dbf';
SET NEWNAME FOR DATAFILE 6 TO '/data1/oradata/qcdash1t/tdcom_index.dbf';
# Do a SET UNTIL to prevent recovery of the online logs
SET UNTIL SCN 28713945;
# restore the database and switch the datafile names
RESTORE DATABASE;
SWITCH DATAFILE ALL;
# recover the database
RECOVER DATABASE;
channel disk1: starting datafile backupset restore
channel disk1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /data1/oradata/qcdash1t/system01.dbf
restoring datafile 00002 to /data1/oradata/qcdash1t/undotbs01.dbf
restoring datafile 00003 to /data1/oradata/qcdash1t/sysaux01.dbf
restoring datafile 00004 to /data1/oradata/qcdash1t/users01.dbf
restoring datafile 00005 to /data1/oradata/qcdash1t/tdcom_data.dbf
restoring datafile 00006 to /data1/oradata/qcdash1t/tdcom_index.dbf
ORA-19624: operation failed, retry possible
ORA-19505: failed to identify file "/backup/oracle/qcdash1/qcdash1.dfb"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
failover to previous backupI omitted a few unimportant entires to make it more readable. It's clearly failing when trying to find the qcdash1.dfb file, but why is it even looking for it? There's no tablespace in the database by that name and there's no RMAN configuration pointing to the path in question and neither does any of the newly restored database parameter and control files. The only link I could find was that on the old host a DBCA template job runs which directs its output to that very path, but what does that have to do with RMAN?

try restore after doing this
Resync the RMAN Catalog
     $ rman target sys/<passwd>@target catalog rman/<passwd>@catalog
     RMAN> resync catalog;
Or
Validate the backup pieces.
     $ rman target sys/<passwd>@target catalog rman/<passwd>@catalog
     RMAN> crosscheck backup;
     RMAN> resync catalog;

Error while Registering the Database with Catalog..

I m creating recovery catalog in same database, and getting the errors.
1. I have created TOOLS tablespace
2.CREATE USER RMAN2
SQL> CREATE USER rman IDENTIFIED BY cat
2 TEMPORARY TABLESPACE temp
3 DEFAULT TABLESPACE tools
4 QUOTA UNLIMITED ON tools;
CREATE USER rman IDENTIFIED BY cat
ERROR at line 1:
ORA-01920: user name 'RMAN' conflicts with another user or role name
SQL> ed
Wrote file afiedt.buf
1 CREATE USER rman2 IDENTIFIED BY cat
2 TEMPORARY TABLESPACE temp
3 DEFAULT TABLESPACE tools
4* QUOTA UNLIMITED ON tools
SQL> /
User created.
3. GRANT RECOVERY_CATALOG_OWNER
SQL> GRANT RECOVERY_CATALOG_OWNER TO rman2;
Grant succeeded.
4. To create the recovery catalog:
1. Connect to the database that will contain the catalog as the catalog owner.
H:\>rman catalog rman2/cat@rock
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 10:45:52 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to recovery catalog database
2. Run the CREATE CATALOG command to create the catalog.
RMAN> CREATE CATALOG;
recovery catalog created
3. Optionally, start SQL*Plus and query the recovery catalog to see which tables were created:
H:\>sqlplus
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Sep 5 11:53:36 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: rman2/cat
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> select count(*) from cat;
COUNT(*)
91
SQL> ed
Wrote file afiedt.buf
1 select owner, table_name, tablespace_name
2 from dba_tables
3* where table_name='DB'
SQL> /
OWNER TABLE_NAME
TABLESPACE_NAME
RMAN2 DB
TOOLS
RMAN DB
ABAMCO_TEST
Next step is to registering the Database in the Recovery Catalog.
Registering a Database in the Recovery Catalog
H:\>rman TARGET / CATALOG rman2/cat@rock
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 11:56:09 2008
Copyright (c) 1982, 2005, Oracle. 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
I m getting above error while registering the Database with Catalog,
Can anybody help me how can I register the Database with Catalog.????
Waiting for Reply!!!!!!!

Dear Manoj I can log in at TARGET Database.
H:\>rman
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 12:41:59 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target sys/rock
connected to target database: ROCK (DBID=3255117147)
RMAN>
============================================================
USING CONNECT STRING as you said.
H:\>rman target "sys/rock@rock as sysdba" catalog rman2/cat@rock
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-00552: syntax error in command line arguments
RMAN-01009: syntax error: found "as": expecting one of: "append, at, auxiliary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, nocatalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
RMAN-01007: at line 0 column 16 file: command line arguments
H:\>rman
It didnt work either.
I have only one database rock, and created recovery catalog in it. I want to register rock database with recovery catalog.

Netbackup related parameters when restoring from tape to a different server

Db version: 11.2.0.2 / Solaris 10
Media Management layer : Symantec Netbackup v7
Production server : qualmh214
Prod DB Name : NEHPROD
We take backup of our prod database using a script similair to the below
run
     ALLOCATE CHANNEL c1 TYPE 'SBT_TAPE';
     SEND 'NB_ORA_CLIENT=qualmh214,NB_ORA_POLICY=qualmh214_rman, NB_ORA_SERV=hlsngt238, NB_ORA_SCHED=Weekly';
     backup incremental level 0 database tag='NEHPROD_full' plus archivelog ;
     backup format 'NEHPROD_%d_%U_%t.rbk' ;
}We have a test server :
dreyth169Every week we need to Clone the above Prod DB from its latest Level 0 Backup stored in Tape.
We have installed Symantec netbackup on our test server.
To restore using RMAN, in run block for the restore, shouldn't NB_ORA_CLIENT be the test server name dreyth169 ? ie. If we keep NB_ORA_CLIENT=qualmh214 (Prod server), then RMAN will do the restore in the PROD !!! Right? That would be a disaster.
What about NB_ORA_POLICY for test server ? Should I create new policy NB_ORA_POLICY for my test server ?

Hello;
Yes, for example if you were doing an RMAN duplicate you would set it to : ( very similar operation )
NB_ORA_CLIENT=target_server
Should I create new policy NB_ORA_POLICY for my test server ?
That's the way I would do it. It may work without it however.
Since you are using oracle 11.2 another option is "Active Database duplication" If your database isn't too large and you have decent network speed and some off peak time once a week I would consider this.
I've used this with great success and you can script it fairly easy in Unix/Linux. If the Remote Host has the Same Directory Structure this get even easier. With a couple of INIT files and a clean up script on the remote this becomes a cookie cutter. Since the job would run from the remote you can avoid RMAN conflicts with your backups.
http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm
Best Regards
mseberg
Edited by: mseberg on Jun 25, 2012 2:50 PM

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/

Rman optimization conflicting with obsolete backups?

Hello,
Suppose I have the following configuration.
I have a partitioned table with each (month-)partition on a different tablespace. I need to keep 10yrs of data. Switch a tablespace with e.g. April2008 data to read-only.
Rman set REDUNDANCY 1 and OPTIMIZATION ON.
Now redundancy 1 should keep only 1 backup of each file wouldn't it?
I do a backup database: it backups every file.
I do a backup database again: it backups every file again.
I do a backup database third time: it says "skipping file n allready backed up 2 times".
Now I do a report obsolete: it marks one of the backups op my file with April2008 data as obsolete.
After performing a delete obsolete, it is gone.
Next day I do a backup database: it backups every file again, so I have two!! backups of file n.
I would like to have only 1 and just 1 backup of the file, and it should never be backed up anymore. The redundancy cannot be set to zero.
How to deal with this?

I think we disagree on this. I can make a single-partition rman backup if:
It is on it's own tablespace, on it's own datafile. No problem with that. It is only the redundancy-problem I have.
Even if I configure redundancy to 1, it makes two backups, and one of these is obsolete. This obsolete gets deleted in a 'delete obsolete' action, and a new obsolete will be created with the next backup.
How would you backup the database with 120 partitions as I described above? Each day a full backup??

RMAN Clone Errors

Hello,
We use Commvault for our backup software. I can successfully clone one application's PROD instance on server1 to TEST on server2.
However, for another application, attempting the same process of cloning the app's PROD instance on server1 to TEST on server2, I'm getting RMAN errors.
The prod database is ISLP and test database is ISLT. I've set the parameters:
o alter system set db_file_name_convert = '/u02/oradata/ISLP', '/u02/oradata/ISLT'
o alter system set log_file_name_convert= '/u01/oradata/ISLP', '/data/oracle/ISLT'
Again the destination is on a second server.
The error message I receive is:
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/09/2013 12:48:55
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_2b.log conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_1b.log conflicts with a file used by the target database
RMAN>
Recovery Manager complete.
I don't understand why RMAN keeps trying to create new redo log files in a directory that is not specified by the log_file_name_convert parameter. I also don't understand why this exact same process works for cloning one applications database but not this application. I would appreciate any help. Thank you. Here is the RMAN script being executed by Commvault.
Rman Script:
[run {
set newname for datafile '/u02/oradata/ISLP/infosilem_ISLP_01.dbf' to '/u02/oradata/ISLT/infosilem_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/sysaux_ISLP_01.dbf' to '/u02/oradata/ISLT/sysaux_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/system_ISLP_01.dbf' to '/u02/oradata/ISLT/system_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/tools_ISLP_01.dbf' to '/u02/oradata/ISLT/tools_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/undo_ISLP_01.dbf' to '/u02/oradata/ISLT/undo_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/users_ISLP_01.dbf' to '/u02/oradata/ISLT/users_ISLP_01.dbf';
allocate auxiliary channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=/opt/galaxy/Base64/libobk.so,BLKSIZE=262144,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 137 -ins 150 -at 22 -j 700481 -jt 700481:3:1 -bal 0 -rcp 0 -ms 1 -p 2 -cn s-dbint -vm Instance001)"
TRACE 0;
set until time = "TO_DATE('05/08/2013 09:00:00','MM/DD/YYYY HH24:MI:SS')" ;
duplicate target database to 'ISLT'
exit;
]

You haven't defined a log_file_name_convert for /u02/oradata/ISLP/
Possibly, the database has multiplexed redo log files, one member each in /u01/oradata/ISLP and one member each in /u02/oradata/ISLP.
Hemant K Chitale

RMAN script for hot backup (looking for code critic) code attached.

Hello Guru's,
I have been having soem trouble running a successful hot full rman backup nightly.
We max our CPU load whenever our RMAN takes too long and conflicts with a Legato tape backup. I have a development server that I attempted to get a consistent backup time duration that is rock solid as to not conflict with the Legato backup time.
I just found out about duration with RMAN scripts here is my code:
#!/bin/bash
#rman backup script for daily hot whole database backup
at -f /hd1/rman_scripts/rman_backup 0600 tomorrow
rman target/
run {
allocate channel d1 device type disk format '/path/%U';
backup duration 1:00 partial minimize load database filesperset 1;
backup as BACKUPSET tag '%TAG' database;
backup as BACKUPSET tag '%TAG' archivelog all delete all input;
delete noprompt obsolete;
release channel d1;
exit
It completes the backup, but does not use the 1 hour allocated- it only uses 15 minutes on average and creates many files instead of normally three backup files.
Here is the results from querying the v$rman_status table for operation,status,start_time:
RMAN,FAILED, 17-OCT-06 0600
BACKUP,FAILED,17-OCT-06 0600
RMAN,FAILED,17-OCT-06 0606
BACKUP,COMPLETED,17-OCT-06 0606
BACKUP,COMPLETED,17-OCT-06 0606
BACKUP,FAILED,17-OCT-06 0615
RMAN,COMPLETED,17-OCT-06 1513
REPORT,COMPLETED,17-OCT-06 1513
DELETE,COMPLETED,17-OCT-06 1513
However, the timestamps of the backupset files it creates is:
06:15 and not 1513?????????????
RMAN appears to have only taken 15 minutes to create the files, why do I have a completed timestamp from v$rman_status of 1513???
Please advise and comment, I am just learning RMAN.

Try to remove the DURATION option in your script.
Here more details about that part.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1010261
Bye, Aron

Configuring RMAN for dataguard.

Hi all,
Here we have a dataguard environment with db1(db_unique_name) as primary and db2(db_unique_name) as physical standby database. For both primary and secondary the ORACLE_SID is 'oracledb'.We configured dataguard in 10g environments and we are not using grid control. And now we want to configure rman for incremental backups. We are using a third catalog database to which we registered from primary db successfully. During primary rman configuration it is showing conflicts. Even the changes made in primary RMAN configuration are applied on to the standby too which i think shouldn't happen in this scenario. How to resolve this issue? Is this happening because of the same ORACLE_SID for both primary and secondary? I'm attaching the link of the doc that we followed also the errors and configuration in rman. Can anyone help?
http://docs.oracle.com/cd/B28359_01/server.111/b28294/rman.htm#BAJFBBBB
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN-08591: WARNING: invalid archivelog deletion policy
RMAN> CONFIGURE DB_UNIQUE_NAME db1 CONNECT IDENTIFIER 'db1';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "db_unique_name": expecting one of: "archivelog, auxiliary, auxname, backup, channel, controlfile, clonename, compatible, datafile, device, default, exclude, encryption, maxsetsize, retention, snapshot"
RMAN-01007: at line 1 column 11 file: standard input
RMAN> show all;
starting full resync of recovery catalog
full resync complete
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_NIOS.f'; # default
Thanks.

RMAN> show db_unique_name;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "db_unique_name": expecting one of: "all, archivelog, auxiliary, auxname, backup, channel, controlfile, datafile, device, default, exclude, encryption, maxsetsize, retention, snapshot"
RMAN-01007: at line 1 column 7 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 21 file: standard input
But on this i'm getting response
SQL> select db_unique_name from v$database;
DB_UNIQUE_NAME
db1
same and db2 as db_unique_name for standby....
Edited by: 954758 on Sep 3, 2012 3:41 AM

Recover database to another database -- RMAN duplicate?

I have a situation where I want to restore our production DB on server 1 (prod1) to test DB on server 2 (test1) to a paticular point in time. I have rman catalog and backup of production database. DB versions our both 10.2..0.3.
I have been attemtping the following
rman target sys@prod1 catalog rman@catalog
connect auxiliary sys@test1
run{
set until time "to_date('07-05-2007 07:00', 'DD-MM-YYYY HH24:MI')";
duplicate target database to test1;
This fails with RMAN aboritng and then a bunch of RMAN-05001 errors saying that auxiliary filename XXXX conflicts with a file used by the target database...
I am confused why does it care what the target DB files are or that there is a conflict when it should be restoring to the auxiliary database (test1)? I want to restore my target DB (prod1) to my auxiliary DB (test1)... What am I doing wrong?
Is there a better way to attempt to use a backup from yesterday to restore into another (non-production) DB? Is the approach I am using correct or workable, and I am just missing something?
Thanks

There are a couple of work around for this, the Oracle document has this fully covered.
13 Creating and Updating Duplicate Databases with RMAN

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.

Dataguard configured using RMAN not in sync with Primary

Hi All.
I have configured physical standby using RMAN it has errored out as below message since the Physical standby is came in Mount state and it is not in sync with Primary.
$ rman target sys/oracle1@PROD_st_STBY auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Jul 29 13:27:02 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PROD_ST (DBID=609107922)
connected to auxiliary database: PROD_ST (not mounted)
RMAN> duplicate target database for standby dorecover;
Starting Duplicate Db at 29-JUL-12
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=156 device type=DISK
contents of Memory Script:
set until scn 239665;
restore clone standby controlfile;
executing Memory Script
executing command: SET until clause
Starting restore at 29-JUL-12
using channel ORA_AUX_DISK_1
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 /oracle1/oraerp/PROD_st/rman/07ngg1p6_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/07ngg1p6_1_1 tag=TAG20120719T140110
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/oracle1/oraerp/PROD_st/cont_.ctl
Finished restore at 29-JUL-12
contents of Memory Script:
sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/29/2012 13:27:29
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/undotbs1.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/sysaux.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/system01.dbf conflicts with a file used by the target database
RMAN>
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
PROD_ST MOUNTED
SQL> select name,db_unique_name,database_role from v$database;
NAME DB_UNIQUE_NAME DATABASE_ROLE
PROD_ST PROD_st_STBY PHYSICAL STANDBY
SQL>
SQL> alter database recover managed standby database disconnect;
Database altered.
SQL>
SQL> alter system set log_archive_dest_state_2=enable;
System altered.
SQL> sho parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string LOCATION=/oracle1/oraerp/PROD_
st/arch/ VALID_FOR=(ALL_LOGFIL
ES,ALL_ROLES)
On Primary
==========
SQL> SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
FROM V$ARCHIVED_LOG
WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
ORDER BY 1; 2 3 4
Thread Last Sequence Generated
1 281
ON STANDBY
SQL> SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
2 FROM
3 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
4 (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
5 WHERE
6 ARCH.THREAD# = APPL.THREAD#
ORDER BY 1; 7
no rows selected
SQL>
SQL> SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;
no rows selected
SQL>
Please suggest solution.
Best Regards,
Edited by: user13707876 on 19-Jul-2012 02:04

Hi,
It has worked now since error with warnings encountered as below:
$ rman target sys/oracle1@PROD_st_STBY auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Jul 29 15:57:39 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PROD_ST (DBID=609107922)
connected to auxiliary database: PROD_ST (not mounted)
RMAN> duplicate target database for standby nofilenamecheck;
Starting Duplicate Db at 29-JUL-12
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=156 device type=DISK
contents of Memory Script:
restore clone standby controlfile;
executing Memory Script
Starting restore at 29-JUL-12
using channel ORA_AUX_DISK_1
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 /oracle1/oraerp/PROD_st/rman/0enggc17_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/0enggc17_1_1 tag=TAG20120719T165607
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/oracle1/oraerp/PROD_st/cont_.ctl
Finished restore at 29-JUL-12
contents of Memory Script:
sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
contents of Memory Script:
set newname for tempfile 1 to
"/oracle1/oraerp/PROD_st/temp01.dbf";
switch clone tempfile all;
set newname for datafile 1 to
"/oracle1/oraerp/PROD_st/system01.dbf";
set newname for datafile 2 to
"/oracle1/oraerp/PROD_st/sysaux.dbf";
set newname for datafile 3 to
"/oracle1/oraerp/PROD_st/undotbs1.dbf";
set newname for datafile 4 to
"/oracle1/oraerp/PROD_st/users01.dbf";
restore
clone database
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /oracle1/oraerp/PROD_st/temp01.dbf in control file
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 29-JUL-12
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 /oracle1/oraerp/PROD_st/system01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00004 to /oracle1/oraerp/PROD_st/users01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/09nggc0j_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/09nggc0j_1_1 tag=TAG20120719T165547
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
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 00002 to /oracle1/oraerp/PROD_st/sysaux.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /oracle1/oraerp/PROD_st/undotbs1.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/08nggc0j_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/08nggc0j_1_1 tag=TAG20120719T165547
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 29-JUL-12
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy RECID=1 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=2 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/sysaux.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=3 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/undotbs1.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=4 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/users01.dbf
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/oracle1/oraerp/PROD_st/redo.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/oracle1/oraerp/PROD_st/redo_2.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 5 thread 0: '/oracle1/oraerp/PROD_st/log5.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 6 thread 0: '/oracle1/oraerp/PROD_st/log6.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
Finished Duplicate Db at 29-JUL-12
RMAN>
So please suggest can i rename them all redolog file.
Best Regards,

Rman batch file for windows

Hi,
I created two files for Rman.
One is showall.txt
Another one is rman.bat
rman.bat contains
rman target=sys/system @c:\showall.txt
showall.txt contains
show all;
list backup;
when i click the rman.bat,it is simply running indefinitely and no output display.
please tell any example script for RMAN on windows by scheduled.

Santosh Kumar wrote:
hi,
thanks for reply.I find that changed the file name rman1.bat insetad of rman.bat .bcz the name conflict with
RMAN.EXE si when the click that it's running indefinitly...........................Not a convincing reason...........My backup script name is also rman.bat, it runs fine.
Regards,
S.K.
Edited by: Santosh Kumar on Aug 15, 2009 7:02 PMI'd guess a pathing issue. Your directory with rman.bat probably comes first in your path. The OP probably had ORACLE_HOME/bin first, so rman.exe fired. It wouldn't have been 'running forever' so much as it was wating for input that the OP never provided.
Just my guess.

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

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 conflict

Similar Messages

Maybe you are looking for