Duplicate by RMAN in 10g

Hi,
to duplicate a databse to an auxiliary DB, auxiliary should be in nomount.
please See 374069.1 note on metalink or Oracle® Data Guard
Concepts and Administration 10g Release 2 (10.2) B14239-04 page F-7.
But,
RMAN can not connect to an auxiliary oracle database when it is in nomount state. I created another
data base named orcl3. Impossible to conect to by RMAN as auxiliary for orcl2
and orcl3 :
orcl2 is in noumount :
C:\Documents and Settings\a.user>rman target sys/pwd@orcl auxiliary sys/pwd@orcl2
connectÚ Ó la base de donnÚes cible : ORCL (DBID=1155329895)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
RMAN-04006: Error not connected to auxiliaire :ORA-12528: TNS:listener: all appropriate instances are blocking new connections
I did :
SQL>alter database mount
and now :
C:\Documents and Settings\ >rman target sys/pwd@orcl auxiliary sys/pwd@orcl2
Regards.
Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 08:02:21 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target : ORCL (DBID=1155329895)
connected to auxiliaire : ORCL2 (DBID=608821149, non ouverte)
RMAN> exit
orcl3 is nomounted :
C:\Documents and Settings\a.user>rman target sys/pwd@orcl auxiliary
sys/pwd@orcl3
Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 08:31:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connectÚ Ó la base de donnÚes cible : ORCL (DBID=1155329895)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
RMAN-04006: Error not connected to auxiliaire :ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Many thanks.

Hi Damorgan,
you are true, RMAN connected :
C:\Documents and Settings\user>rman target sys/pwd@orcl auxiliary /
Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 15:37:46 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target : ORCL (DBID=1155329895)
connected to auxiliary : ORCL2 (non mounted)
But :
When :
RMAN> run{
2> duplicate target database for standby
3> nofilenamecheck
4> dorecover;
5> }
canal ORA_AUX_DISK_1 : restauration de fichier de contr¶le
canal ORA_AUX_DISK_1 : copie du fichier de contr¶le copiÚe
fichier en entrÚe=C:\ORACLE\ORADATA\BACKUP\ORCL\CONTROL01.DBF
fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL01.CTL
fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL02.CTL
fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL03.CTLFin de restore dans 04/08/07
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Failed in Duplicate DB 08/04/2007 15:43:10
RMAN-03015: une erreur s'est produite dans le script stockÚ Memory Script
RMAN-03009: Úchec de la commande sql sur le canal clone_default Ó 08/04/2007 15:43:10
RMAN-11003: erreur lors de l'analyse ou de l'exÚcution d'une instruction SQL : alter database mount standby database
ORA-01103: database name 'orcl' in control file is not 'orcle2'
Any idea ??

Similar Messages

  • Duplicate from 9i to 10g

    Hii All,
    Can I duplicate the database from 9i to 10g using 10g RMAN command?
    thankss in advance

    hi,
    No, you can not do that. RMAN 10g executable is not compatible to take RMAN backup of 9i. Moreover, RMAN DUPLICATE works only with 10g. As per Oracle Documentation, the compatibility matrix doesn't support this.
    Hope it helps !
    Cheers !

  • Duplicate by RMAN

    Hi,
    on 10 gR2 can we duplicate from RMAN Backup using SET UNTIL TIME ?
    I mean for example can I duplicate from the backups of 22 of January (my backups from 22 of Jan and 23 , 24 until first of february are available ).
    If the backups are on tape should we do something extra ?
    Thanks.

    on 10 gR2 can we duplicate from RMAN Backup using SET UNTIL TIME ?
    Ans: Yes, If you have full Backup + all algenerated archive logs after full backup till set until time.
    If the backups are on tape should we do something extra ?
    Ans: No, use that channel that you need to take the RMAN backup.
    Regards
    Asif Kabir

  • Licence is required for RMAN in 10g??

    Hi, all.
    Licence is required for RMAN in 10g??
    Thanks in advance.
    Best Regards.

    Yes. You need to license the Diagnostic Pack to get AWR.
    http://download.oracle.com/docs/cd/B19306_01/license.102/b14199/options.htm#CIHGFIAF specifically states that
    The Oracle Diagnostic Pack provides automatic performance diagnostic and advanced system monitoring functionality. The Diagnostic Pack includes the following features:
    * Automatic Workload Repository
    * Automatic ...
    "

  • RMAN for 10g RAC in windows2003

    Hello experts,
    could any one help to configure RMAN for 10g RAC in windows2003?
    thanks,

    Hi;
    Please check:
    RMAN: RAC Backup and Recovery using RMAN [ID 243760.1]
    RMAN configuration in ORACLE RAC database
    RMAN configuration in ORACLE RAC database
    RMAN and RAC
    RMAN and RAC
    Also check this search:
    http://forums.oracle.com/forums/search.jspa?threadID=&q=RMAN+RAC&objID=f384&dateRange=all&userID=&numResults=15
    I belive those are will answer your question
    Regard
    Helios

  • Migrating with RMAN from 10g to 11g

    Hi gurus,
    I am following the following procedure to migrate database from 10g to 11g using rman
    Source side:
    RMAN>connect target
    RMAN>backup database;
    RMAN>backup archivelog all;
    RMAN>backup current controlfile;
    SQL> create pfile from spfile;
    Copied datafile, archivelog backup files and pfile and password files to target side. i.e. on 11g server side
    Target side:
    Set proper parameters for 11g
    SQL>startup nomount;
    RMAN>connect target
    RMAN>set dbid=<source database id>
    RMAN>catalog start with '<rman backup file location';
    RMAN>restore controlfile;
    RMAN>run
    set newname for datafile 1 to '<target datafiles location with file name';
    restore database;
    switch datafile all;
    finished
    upto now it's success full when i am trying to recover
    RMAN>recover database;
    it is saying
    rman 00571
    rman 00569
    rman 00571
    rman 03002
    ora - 19698
    can you please suggest the solution for this.
    thanks a lot.

    I'm not sure what you're doing is supported.
    You are taking a 10g database and restore and recover it using 11g software.
    I think you are allowed to do that with 10g software only.

  • RMAN in 10g database deletes archivelog files before standby receives them

    Hi all,
    We currently have problem with our Oracle 10gR1 database on Windows 2000 server in that the RMAN backups on the primary database delete archivelogs before the standby database can receive current and new archivelogs from primary database. What happens is that RMAN backs up the archivelogs and deletes them from disk before the archivelogs are sent to the standby. The standby then looks for these archivelogs on the primary but is unable to locate them. Whenever this happens, the production database (primary) hangs and we have to restart the instance on the primary. We have our Data Guard setup in maximum performance mode so this should not happen.
    As a short term fix, we have changed the backups to have RMAN backup and delete the archive logs 15 minutes older than current time so that the standby can receive the logs and not have problems. Besides this fix is there a long term solution to the problem or is it a bug in Oracle 10g? The issue came up after we upgraded from 9i to 10g and never saw it before in 9i with RMAN and Data Guard physical standby databases.
    Thanks
    Ben Prusinski, Oracle DBA

    thanks for answer...
    did you managed to make it 'work'?
    according to doc. if set on standby it should:
    <>
    Then, these files are eligible for deletion:
    Archived redo log files in the flash recovery area that
    were applied on the standby database.
    <>
    and this is to my understanding irespective to retention policy...unfortunately report obsolete does not report applied archived logs as eligable for deletion.
    How this works in your case?
    regards.
    goran

  • RMAN using 10g grid control

    I have oracle 8i and 9i databases including 9i RAC instances.
    Planning to setup a 10g instance for centralized RMAN backups for all the above databases.
    Do i need 10Grid control for this functionality ?
    If yes what are the agent softwares needed on the 101g server as well as on 8i and 9i databases, so that i can discover the nodes.
    Do i need to run an agent for every database, in case a machine host's more than on database ?
    Do i need an agent running on every node of my RAC instance ?
    Thanks for your help!

    Hi,
    if you want to perform rman backup of all these database by Gui mode of management server then agent should be running on these database.
    but if u go for manually(Prefer way) then u have first create a catalog on seprate server and register all these databases with this catalog and then run script for taking backup of database.
    second method is best for ur case and in that u don't need of running agent.
    Thanks
    Kuljeet

  • Duplicate Problems (RMAN is looking at the wrong backup)

    We are running into a problem when we try to duplicate our database. Here is the process we use to duplicate:
    delete old backup files (we only use RMAN for cloning so we don't need them)
    set prod db environment variables<run rman
    connect target sys/####;
    backup database;
    exit;
    set test db environment variables<shutdown test database, rename test db folder (in case we missed getting something important out) create a new folder for test db.
    start test db (nomount)
    rman
    connect target sys/####@PROD
    connect auxiliary sys/####@TEST
    run
    allocate auxiliary channel disk1 type disk;
    duplicate target database to TEST;
    we get this error:
    channel disk1: reading from backup piece E:\RMAN\PROD\BKUP_PROD_610891176_1
    ORA-19870: error reading backup piece E:\RMAN\PROD\BKUP_PROD_610891176_1
    ORA-19505: failed to identify file "E:\RMAN\PROD\BKUP_PROD_610891176_1"
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    failover to previous backup
    The backup file RMAN is trying to read is the backup from our previous clone. How can I tell RMAN to look at the backup we just made?
    I've run "list backup;" and the most recent backup is shown there. We've run into this problem a couple of times now, but not everytime. I can't find any rhyme or reason for why it works or fails but the process is the same sometimes we can just wait a half-hour or an hour and it works. Anyone have any ideas that could help?
    BTW - We aren't using a recovery catalog.

    http://dbataj.blogspot.com/2006/12/duplicating-database-with-recovery.html

  • ORA:01013 with Duplicate Database - RMAN

    Hi,
    I havea demo database on server1 and am creating a clone database on server2 with RMAN duplicate command. I have the catalog on server1 itself. I created the backups of the database and executed RMAN command from server2 with
    server1 in open status and server2 in nomount state.
    the command i ran was:
    duplicate target database to clonedb
    until logseq 338 thread 1
    pfile=/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora
    logfile
    '/u01/app/oracle/oradata/clonedb/redo01.log' size 1m,
    '/u01/app/oracle/oradata/clonedb/redo02.log' size 1m;
    Please let me know how to overcome this error..
    Thanks,
    Raj
    This is the error i got along with the log it created...
    Starting Duplicate Db at 28-OCT-04
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=14 devtype=DISK
    printing stored script: Memory Script
    set until scn 130734;
    set newname for datafile 1 to
    "/u02/oradata/clonedb/system01.dbf";
    set newname for datafile 2 to
    "/u03/oradata/clonedb/undotbs01.dbf";
    set newname for datafile 3 to
    "/u02/oradata/clonedb/testtbs_01.dbf";
    set newname for datafile 4 to
    "/u02/oradata/clonedb/system02.dbf";
    set newname for datafile 5 to
    "/u02/oradata/clonedb/rmantbs_01.dbf";
    restore
    check readonly
    clone database
    executing script: Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 28-OCT-04
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backupset restore channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u02/oradata/clonedb/system01.dbf restoring datafile 00002 to /u03/oradata/clonedb/undotbs01.dbf
    restoring datafile 00003 to /u02/oradata/clonedb/testtbs_01.dbf
    restoring datafile 00004 to /u02/oradata/clonedb/system02.dbf restoring datafile 00005 to /u02/oradata/clonedb/rmantbs_01.dbf
    channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/full/DEMODB_20041027_05g3jeeq_1_1 tag=FULL params=NULL channel ORA_AUX_DISK_1: restore complete Finished restore at 28-OCT-04 sql statement: CREATE CONTROLFILE REUSE SET DATABASE "clonedb" RESETLOGS ARCHIVELOG
    MAXLOGFILES 5
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 1
    MAXLOGHISTORY 680
    LOGFILE
    GROUP 1 '/u01/app/oracle/oradata/clonedb/redo01.log' SIZE 1048576 ,
    GROUP 2 '/u01/app/oracle/oradata/clonedb/redo02.log' SIZE 1048576
    DATAFILE
    '/u02/oradata/clonedb/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    printing stored script: Memory Script
    switch clone datafile all;
    executing script: Memory Script
    datafile 2 switched to datafile copy
    input datafilecopy recid=1 stamp=540710832 filename=/u03/oradata/clonedb/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafilecopy recid=2 stamp=540710832 filename=/u02/oradata/clonedb/testtbs_01.dbf
    datafile 4 switched to datafile copy
    input datafilecopy recid=3 stamp=540710832 filename=/u02/oradata/clonedb/system02.dbf
    datafile 5 switched to datafile copy
    input datafilecopy recid=4 stamp=540710832 filename=/u02/oradata/clonedb/rmantbs_01.dbf
    printing stored script: Memory Script
    set until scn 130734;
    recover
    clone database
    delete archivelog
    executing script: Memory Script
    executing command: SET until clause
    Starting recover at 28-OCT-04
    using channel ORA_AUX_DISK_1
    starting media recovery
    channel ORA_AUX_DISK_1: starting archive log restore to default destination channel ORA_AUX_DISK_1: restoring archive log archive log thread=1 sequence=337 channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/arch/arc_DEMODB_20041027_06g3jef2_1_1 tag=TAG20041027T134050 params=NULL channel ORA_AUX_DISK_1: restore complete archive log filename=/u02/oradata/clonedb/arch/1_337.arc thread=1 sequence=337 channel clone_default: deleting archive log(s) archive log filename=/u02/oradata/clonedb/arch/1_337.arc recid=1 stamp=540710834 media recovery complete Finished recover at 28-OCT-04
    printing stored script: Memory Script
    shutdown clone;
    startup clone nomount pfile= '/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora';
    executing script: Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/28/2004 06:28:26
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
    Recovery Manager complete.

    HI,
    # STBY:
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area  242208768 bytes
    Fixed Size            2227176 bytes
    Variable Size          184550424 bytes
    Database Buffers       50331648 bytes
    Redo Buffers            5099520 bytes
    # PRIMARY:
    RMAN> CONNECT TARGET sys/oracle@JOHN;
    connected to target database: JOHN (DBID=1575580406)
    RMAN> CONNECT AUXILIARY sys/oracle@JOHN_DB2;
    Until this you did correct. now just in a run block, like
    eg
    run
    allocate channel ....
    allocate channel...
    duplicate target database for standby from active database;

  • How to duplicate by rman database?

    dear sir, i read one article and follow step and 2nd auxiliary database i delete all dbf, ctl, log(redo) files ...then tryying to create dubplicate giving me error
    can some one send steps of it
    rgds
    shahzad

    Database Duplication with RMAN
    Use the RMAN DUPLICATE command to create a copy of the target database that you can use for testing. The command restores backups and copies of the primary database's files and creates a new database.
    As part of the duplicating operation, RMAN manages the following:
    Restores the target datafiles into the duplicate database and performs incomplete recovery using all available archived log and incremental backups.
    Opens the duplicate database with the RESETLOGS option after incomplete recovery to create the online redo logs.
    Generates a new, unique database identifier for the duplicate database.
    Note also the following features of RMAN duplication. You can:
    Skip read-only tablespaces with the SKIP READONLY clause (read-only tablespaces are included by default). You can also exclude any tablespace with the SKIP TABLESPACE clause so long as it is not the SYSTEM tablespace and does not contain rollback or undo data. If you omit tablespaces, then you can add them later.
    Create your duplicate database in a new host. If the same directory structure is available, then you can use the NOFILENAMECHECK option and reuse the target datafile filenames for the duplicate datafiles.
    Create your duplicate database by using the SET UNTIL command or UNTIL clause of the DUPLICATE command to recover it to a noncurrent time. By default, the DUPLICATE command creates the database using the most recent backups of the target database and then performs recovery to the most recent consistent point contained in the incremental and archived redo log backups.
    Use the duplicate database without a recovery catalog.
    Register the duplicate database in the same recovery catalog as the target database. This option is possible because the duplicate database receives a new database identifier during duplication. If you copy the target database using operating system utilities, then the database identifier of the copied database remains the same so you cannot register it in the same recovery catalog.
    Figure 6-3 illustrates a case of database duplication. In this example, RMAN creates two duplicate database by using one set of datafile backups: one database on the local host and one database a remote host.
    Figure 6-3 Creating a Duplicate Database from Backups
    Text description of the illustration sbr81078.gif
    The method you use to duplicate your database depends on whether you are creating your duplicate database on the same or a different host and whether the duplicate directory structure is the same as your target database directory structure. For example, in some cases you can keep the same directory structure and filenames in your duplicate database, while other times you must rename the files.
    See Also:
    Chapter 12, "Duplicating a Database with Recovery Manager" to learn how to make a duplicate database, and Oracle9i Recovery Manager Reference for DUPLICATE command syntax.
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc2.htm#462471
    Joel Pérez
    http://www.oracle.com/technology/experts

  • RMAN with 10g grid contorl

    Hi All,
    Did anyone check how RMAN work in 10g grid control? I have RMAN in 9i EM so just curious.

    I am getting this error in output log.any idea ?
    error writing input to commandBad name after db1' at - line 5.

  • User managed backup and rman  oralce 10g

    hi guys
    what are the enhancement of user managed backup and rman in oralce 10g
    would u pls tell me in understandable manner
    thanks in advance

    Hi,
    what are the enhancement of user managed backup and rman in oralce 10g
    would u pls tell me in understandable manneRefer below link
    http://dbataj.blogspot.com/2008/05/rman-versus-user-managed-backup-part-i.html
    Hope helps.
    Regards,
    X A H E E R

  • Does RMAN in 10g Enterprise Have Backup with *Compression* ?

    hi RMNA experts,
    I use the Enterprise edition of 10g. Using RMAN for database backups.
    Can you request compression in an RMAN backup - to get a smaller backup file?
    Thanks, John

    Yes you can. Here is the script.
    run {
    allocate channel ch1 device type disk;
    backup as compressed backupset incremental level 0 format '/u03/rman_backup/RMAN_DBF_TST<%s:%t:%p>.bkp' database;
    sql 'alter system archive log current';
    backup as compressed backupset format '/u03/rman_backup/RMAN_ARCH_TST<%s:%t:%p>.bkp' archivelog all delete input;
    backup as compressed backupset format '/u03/rman_backup/RMAN_CTL_TST<%s:%t:%p>.bkp' current controlfile;
    Regards
    Asif Kabir

  • Error while taking backup  through RMAN in 10g XE

    While taking backup through RMAN in XE instance , an error comes out.
    The contents of oxe_backup_current file is as below :
    XE Backup Log
    Recovery Manager: Release 10.2.0.1.0 - Production on Wed Jul 6 15:49:51 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database: XE (DBID=2635631092)
    RMAN>
    echo set on
    RMAN> shutdown immediate;
    using target database control file instead of recovery catalog
    database closed
    database dismounted
    Oracle instance shut down
    RMAN> startup mount;
    connected to target database (not started)
    Oracle instance started
    database mounted
    Total System Global Area     805306368 bytes
    Fixed Size                     1261444 bytes
    Variable Size                209715324 bytes
    Database Buffers             591396864 bytes
    Redo Buffers                   2932736 bytes
    RMAN> configure retention policy to redundancy 2;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    new RMAN configuration parameters are successfully stored
    RMAN> configure controlfile autobackup format for device type disk clear;
    RMAN configuration parameters are successfully reset to default value
    RMAN> configure controlfile autobackup on;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    RMAN> sql "create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile";
    *sql statement: create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile*
    *RMAN-00571: ===========================================================*
    *RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
    *RMAN-00571: ===========================================================*
    *RMAN-03009: failure of sql command on default channel at 07/06/2011 15:50:57*
    *RMAN-11003: failure during parse/execution of SQL statement: create pfile='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora' from spfile*
    *ORA-27086: unable to lock file - already in use*
    *Linux Error: 11: Resource temporarily unavailable*
    Additional information: 8
    Additional information: 16476
    RMAN> backup as backupset device type disk database;
    Starting backup at 06-JUL-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=102 devtype=DISK
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00003 name=/usr/lib/oracle/xe/oradata/XE/sysaux.dbf
    input datafile fno=00005 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_log01.dbf
    input datafile fno=00006 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_lrg01.dbf
    input datafile fno=00001 name=/usr/lib/oracle/xe/oradata/XE/system.dbf
    input datafile fno=00009 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_log01.dbf
    input datafile fno=00010 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_lrg01.dbf
    input datafile fno=00002 name=/usr/lib/oracle/xe/oradata/XE/undo.dbf
    input datafile fno=00004 name=/usr/lib/oracle/xe/oradata/XE/users.dbf
    input datafile fno=00008 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_sml01.dbf
    input datafile fno=00012 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_sml01.dbf
    input datafile fno=00011 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_mdm01.dbf
    input datafile fno=00007 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_mdm01.dbf
    channel ORA_DISK_1: starting piece 1 at 06-JUL-11
    channel ORA_DISK_1: finished piece 1 at 06-JUL-11
    piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T155057_718dw649_.bkp tag=TAG20110706T155057 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
    Finished backup at 06-JUL-11
    Starting Control File and SPFILE Autobackup at 06-JUL-11
    piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755797849_718dwofy_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 06-JUL-11
    RMAN> configure controlfile autobackup off;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    new RMAN configuration parameters are successfully stored
    RMAN> alter database open;
    database opened
    RMAN> delete noprompt obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           3      06-JUL-11        
      Backup Piece       3      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp
    Backup Set           4      06-JUL-11        
      Backup Piece       4      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp
    deleted backup piece
    backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp recid=3 stamp=755789684
    deleted backup piece
    backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp recid=4 stamp=755789699
    Deleted 2 objects
    RMAN>
    Recovery Manager complete.
    RMAN error: See log for details.

    I think it is trying to overwrite exiting file. Either give a different name or cleanup the files in preferred location.

Maybe you are looking for