11g RMAN UNDO backup optimization

Hi all?
I have tested 11g RMAN UNDO backup optimization
1st I fill the undo tablespace by sql manipulations and not commiting
2nd backed undo_ts up by RMAN (size 24m)
3rd I made a commit
Then backed undo tablespace again but backup_size didn’t change     (24m)
Then I made some more manipulations and backed undo_ts again. This time backup_size reduced. (11m)
Then I restarted db and backed up undo_ts again. This time backup size became what I expected (600K)
The question is why 11g rman undo tablespace backup size didn’t reduce after commit?
according to 11g undo optimization it had to
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)
13172736
SQL> begin
for i in 1..100000 loop
insert into testundo values(i);
end loop;
end;
2 3 4 5 6
PL/SQL procedure successfully completed.
SQL> SQL> update testundo set
id=2 where id>0;
2
update testundo set
ERROR at line 1:
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
10 Full *24.54M* DISK 00:00:04 10-JUN-10
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142437
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
List of Datafiles in backup set 10
File LV Type Ckp SCN Ckp Time Name
6 Full 577669 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> commit;
Commit complete.RMAN> backup datafile 6 format 'after commit.backup';
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
11 Full *24.54M* DISK 00:00:02 10-JUN-10
BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142541
Piece Name: /home/oracle/product/11/Db_1/dbs/after commit.backup
List of Datafiles in backup set 11
File LV Type Ckp SCN Ckp Time Name
6 Full 577705 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> alter system archive log current;
System altered.
SQL> commit;
Commit complete.
SQL> select count(*) from testundo;
COUNT(*)
100000
SQL> delete from testundo;
100000 rows deleted.
SQL> commit;
Commit complete.
SQL> insert into testundo values(1);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system flush buffer_cache;
System altered.RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
13 Full *11.03M* DISK 00:00:01 10-JUN-10
BP Key: 13 Status: AVAILABLE Compressed: NO Tag: TAG20100610T143359
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
List of Datafiles in backup set 13
File LV Type Ckp SCN Ckp Time Name
6 Full 578410 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
RMAN>
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 393375744 bytes
Fixed Size 1300156 bytes
Variable Size 352323908 bytes
Database Buffers 33554432 bytes
Redo Buffers 6197248 bytes
Database mounted.
Database opened.
SQL> RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
14 Full *600.00K* DISK 00:00:02 10-JUN-10
BP Key: 14 Status: AVAILABLE Compressed: NO Tag: TAG20100610T152843
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
List of Datafiles in backup set 14
File LV Type Ckp SCN Ckp Time Name
6 Full 580347 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
Thanks in advance
Turkel

Hi Turkel,
The space used for undo is also related to the undo retention setting.
As it seems you do a test update and proceed with backups on:
- 14:24:37 (-> 25M)
- 14:25:41 (-> 25M)
- 14:33:59 (-> 11M)
- 15:28:43 (-> 600K)
The first two backups probably are still within the undo retention period for the update.
The third backup shows a partly empty undo (is your setting 900?).
The last falls outside the retention period for the update resulting in the small backup size.
Regards,
Tycho

Similar Messages

  • Restore 11g rman cold backup on same server.

    Hi All,
    I have a requirement , where we have to clone one development database's to other database's sitting on the same host.
    I have taken the cold rman backup and copy it different database's local folder.
    I changed the db_name in target pfile and did the nomount , but when I tries to restore the controlfile , it throws me below errors.
    Just to add to to it, I was ale to restore the controlfile to the location specified in pfile.
    now , when I tries to mount the database , it throws me following errors
    Snippet from target database's
    SQL> startup mount pfile=/db/epmtrain/oracle/11.1.0/dbs/initepmtrain.bkp
    ORACLE instance started.
    Total System Global Area 1.3696E+10 bytes
    Fixed Size                  2132152 bytes
    Variable Size            6173202248 bytes
    Database Buffers         7516192768 bytes
    Redo Buffers                4362240 bytes
    ORA-00205: error in identifying control file, check alert log for more info
    RMAN> run {
    2> restore controlfile from '/db/epmtrain/export/rman/EPMDEV_06ogm377.bkp';
    3> }
    Starting restore at 07-AUG-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: restoring control file
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/07/2013 07:12:21
    ORA-19870: error while restoring backup piece /db/epmtrain/export/rman/EPMDEV_06ogm377.bkp
    ORA-19504: failed to create file "/db/epmtrain/oracle/11.1.0/dbs/db/epmtrain/data1/epmtrain/control01.ctl'"
    ORA-27040: file create error, unable to create file
    HPUX-ia64 Error: 2: No such file or directory
    Regards

    940856 wrote:
    I restored the controlfile to the path mentioned in pfile. after that , when I tries to mount the database , it throws me the following errors.
    ---------- Snippet from alert.log ------
    ORA-00210: cannot open the specified control file
    ORA-00202: control file: '/db/epmtrain/data1/epmtrain/control01.ctl''
    ORA-27037: unable to obtain file status
    HPUX-ia64 Error: 2: No such file or directory
    Additional information: 3
    ORA-205 signalled during: ALTER DATABASE   MOUNT...
    ------------ controlfile location in pfile ---------
    *.control_files=/db/epmtrain/data1/epmtrain/control01.ctl','/db/epmtrain/data1/epmtrain/control02.ctl'
    --------------- show parameter control output -------------
    SQL>  show parameter control
    NAME                                 TYPE                             VALUE
    control_file_record_keep_time        integer                          7
    control_files                        string                           /db/epmtrain/data1/epmtrain/co
                                                                          ntrol01.ctl', /db/epmtrain/dat
                                                                          a1/epmtrain/control02.ctl
    control_management_pack_access       string                           DIAGNOSTIC+TUNING
    Regards
    So present proof that "/db/epmtrain/data1/epmtrain/control01.ctl" actually exists .....

  • Backup Optimization

    backup optimization is on ; i execute the following commands twice, and backup happens second time also with a seperate piece, why ? i did not even make any changes, oracle says for a datafile to be identical The data file must have the same DBID, checkpoint SCN, creation SCN, and RESETLOGS SCN and time as a data file in a backup. The data file must be
    offline-normal, read-only, or closed normally. My file is already offline with alter tablespace users offline option. I also know that RMAN uses backup optimization when the following conditions are true:
    # The CONFIGURE BACKUP OPTIMIZATION ON command has been run to enable backup optimization.
    # You run BACKUP DATABASE, BACKUP ARCHIVELOG with ALL or LIKE options, or BACKUP BACKUPSET ALL, BACKUP RECOVERY AREA, BACKUP RECOVERY FILES, or BACKUP DATAFILECOPY.
    even if i say backup database, oracle still backs it up 2 times, datafile 4... why ?????
    backup format '/u01/back/%U' datafile 4;
    backup format '/u01/back/%U' datafile 4;
    Edited by: 842638 on 29-Jul-2012 08:28

    in addition, if you command RMAN to backup datafile or tablespace exactly, RMAN definitely will back it up. if you run "BACUP DATABASE" command, then you will see that "skipping datafile X" line during backup. (my previos message is still valid, REDUNDANCY condition must be provided)
    a specific TABLESPACE or DATAFILE backup command (Backup datafile X or Backup Tablespace Y) wil take backup every time.
    Edited by: Mustafa Kalaycı on Jul 29, 2012 8:41 AM

  • NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

    제품 : RMAN
    작성날짜 : 2004-05-20
    NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
    =======================================================
    오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
    지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
    전략을 세울 수 있다.
    1. 백업 화일 최적화 방법 (Backup File Optimization)
    백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
    백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
    화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
    이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
    된다.
    이때 같은 화일이라고 판단하는 기준은 다음과 같다.
    * Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
    반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
    되어야 함.
    * Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
    SCN 과 time.
    * Backup Set: 같은 Backup Set recid 와 stamp.
    RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
    이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
    정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
    만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
    되어도 화일을 지우게 된다.
    RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
    않는다.
    그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
    된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
    Note:
    자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
    이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
    백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
    명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
    예:
    CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
    2. Backup Optimization에 Retention Policies 적용 하기
    Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
    사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
    이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
    REDUNDANCY = 1 이 적용 된다.
         a. Recovery Window 를 이용한 Backup Optimization
    만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
    적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
    Window 보다 오래된 데이터 화일을 백업한다.
    예를 들면 다음과 같은 조건에서
    o Today is February 21.
    o The recovery window is 7 days.
    o The most recent backup of tablespace tbs2 to tape is January 3.
    o Tablespace tbs2 is read-only.
    2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
    RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
    된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
    조건을 지키게 된다.
    이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
    그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
    2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
    media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
         b. Redundancy 를 이용한 Backup Optimization
    Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
    에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
    이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
    Redundancy의 갯수를 정한다.
    아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
    동안 한다고 하자.
    Day Action Result Redundant Backup
    Monday Take tablespace archive offline clean.
    Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
    Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
    Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
    Friday Run BACKUP DATABASE. n/a Tuesday backup.
    Saturday Run BACKUP DATABASE. n/a Tuesday backup.
    Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
    Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
    화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
    3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
    금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
    복사하지 않게 된다.
    RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
    만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
    때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
    사이클이 진행 된다.
    3. RETENTION POLICY NONE vs. DEFAULT
    주의 사항:
    'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
    POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
    자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
    OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
    (REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
    'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
    제거 하라는 명령이다.
    보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
    Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
    --------------THE END----------------------------------------------

    Hi,
    Backup optimisation = +- do not copy empty space.
    So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
    In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
    Regards,
    Yoann.

  • RMAN : BACKUP OPTIMIZATION ON

    Hi All,
    I have a doubt about BACKUP OPTIMIZATION ON parameter..
    If Any one worked, can u tell me the exact use of this parameter....
    Regards,
    Prabhu.

    Used to enable or disable backup optimization. Backup file optimization can assist in reducing the space used to backup the database. When performing an RMAN backup, a check is done on the file before backup to see if the file already exists in a backupset with the same information: (dbid, checkpoint, and resetlogs data).
    For archive logs, the same file means the same dbid, thread, sequence, and resetlogs data. If the DELETE INPUT option is used, RMAN deletes all the files that would have been backed up, even when the file is not included due to file optimization.
    The two possible values for backup optimization is ON and OFF as shown in the following example syntax:
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE BACKUP OPTIMIZATION ON;
    Use caution when enabling backup optimization if you use a media manager that has an expiration policy. The media manager can expire tapes containing backups (using its media control software), and RMAN will not make new backups because of optimization. One way to protect from this is to run CROSSCHECK periodically to synchronize the repository with the media manager.
    Also note that you should consider how backup optimization works with regards to the RETENTION POLICY. RMAN will only work with files within the retention period. For example, consider performing a backup with optimization enabled and a retention period of 3 days. RMAN will only compare the datafile with backup sets within the 3 day period - even if the datafile it is about to backup hasn't changed within that 3 days.
    ofcourse the best reference is here

  • Rman backup optimization question

    Hi,
    I have come across a RAM related question and would like to understand the answer:
    The RMAN configuration has backup optimization set to ON. Which of the following commands will this setting affect?
    a) Backup Archivelog with ALL or LIKE options, b) Backup Backupset ALL, c) Backup Tablespace, d) Backup Database
    I believe all of the above are affected by backup optimization, however, only a, b and d seems correct, not c. I wonder why tablespace is not affected - it does not say read only, etc.?
    Any ideas? Thanks.

    Thanks for the quick response!
    Meanwhile I did a few tests below, and yes, tablespace does obviously not use backup optimization. But why? Doesn't the same like backup database apply? Isn't using the same retention policy?
    RMAN> backup database;
    skipping datafile 5; already backed up 2 time(s)
    RMAN> backup archivelog ALL;
    skipping archived log file /u02/fra/ORCL/ar...; already backed up 1 time(s)
    RMAN> backup tablespace example;
    input datafile file number=00005
    piece handle=/u02/fra/ORCL/backupset....
    RMAN> backup tablespace example;
    input datafile file number=00005
    piece handle=/u02/fra/ORCL/backupset....

  • RMAN backup Optimization

    Hi gurus
    I would like to know that if I enable backup Optimization on then incremental full backup skip any files which was earlier backup? Because we may know that backup Optimization on ensure skip those files which are already taken backup.
    Database : oracle 10g 10.2.0.3
    Rabi

    None.
    Under OPTIMIZATION, an Incremental Full (i.e. L0) backup would skip a file only if it has not changed since the last L0 backup --- which wouldn't be the case with most database files.
    Even when you run Incremental Differential or Incremental Cumulative (i.e. L1 or higher) backups, the file would not be skipped.
    Hemant K Chitale

  • "Backup optimization on" is not working for "backup database"

    Hi,
    I am using a windows environment and my database info is like this:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE    11.2.0.1.0      Production
    TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Productionnow, I change my configuration for backup optimization on and then make example tablespace offline and also make example datafile offline. After that I run 2 times "Backup Database" command but 2 backup has same size and have example tablespace too... Backup archivelog all is working bur backup database is not!
    according to this link it must not backup example datafile for second: http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV113
    is there something that I missed ?
    rman configuration:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\APP\ABC\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFORCL.ORA'; # default

    If you enable backup optimization, then the BACKUP command skips backing up files when the identical file has already been backed up to the specified device type.
    1. In case of datafile RMAN compares the DBID, checkpoint SCN, creation SCN, and RESETLOGS SCN and time as a datafile already in a backup. If they are identical then skip to take backup again.
    2. In case of archived redo log RMAN compares thread, sequence number, and RESETLOGS SCN and time.
    3. In case of backupset RMAN compares recid and stamp.
    Backup optimization applies to only commands,
    -BACKUP DATABASE
    -BACKUP ARCHIVELOG with ALL or LIKE options
    -BACKUP BACKUPSET ALL
    refer,
    http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14191/rcmconc1008.htm
    Thanks

  • RMAN archive backup retention

    Hi,
    My backed up archive file is not getting deleted from backup location as per my retention policy.
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '${BACKUP_DIR}/${THEDBNAME}/cf_%d_%F';
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 3;
    CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE = 5G;
    RUN
    BACKUP DATABASE format '${BACKUP_DIR}/${THEDBNAME}/db_%d_%t_%s_%p' TAG = 'DB_backup' ;
    sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    backup filesperset 25 archivelog all format '${BACKUP_DIR}/${THEDBNAME}/arch_%d_%U' TAG = 'ARCH_backup';
    delete noprompt archivelog until time 'sysdate -1' ;
    CROSSCHECK BACKUP;
    DELETE NOPROMPT EXPIRED BACKUP;
    DELETE NOPROMPT FORCE OBSOLETE;
    EOF
    The retention policy is keeping 2 sets of backups but it's not removing the backed up archive files from the backup location.
    Regards,
    DBA

    Hi
    I have the same issue. It looks like a BUG:
    list backup of archivelog .. : reports the existence aof the archivelog backups
    But the "delete obsolete recovery wiondow" deletes only the data files backups !!
    I can also confirm that by checking the catalog directly:
    select bck_type, status, max(completion_time), min(completion_time), count(*) from rman.bs where db_key=5297591 group by bck_type , status
    My catalog is 11g and my target db is 9i
    Have you succeeded to get any workaround ?
    Thanks

  • ORA-01858 error in RMAN during backup backupset format '/test/rman/%U'

    Hello!
    I am trying to perform bacup using command
    RMAN> backup backupset completed after 'sysdate-1' format '/tmp/test/%U';
    as described in:
    asmcmd scripts
    All backupsets are copied to /tmp/test/.
    Everything is going fine except the last message from RMAN:
    input backupset count=5342 stamp=660348635 creation_time=17-JUL-08
    channel ORA_DISK_1: starting piece 1 at 18-JUL-08
    piece handle=/tmp/test/6ujlo7mr_1_2 comment=NONE
    channel ORA_DISK_1: finished piece 1 at 18-JUL-08
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
    input backupset count=5343 stamp=660348722 creation_time=17-JUL-08
    channel ORA_DISK_1: starting piece 1 at 18-JUL-08
    piece handle=/tmp/test/6vjlo7pi_1_2 comment=NONE
    channel ORA_DISK_1: finished piece 1 at 18-JUL-08
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
    input backupset count=5344 stamp=660348810 creation_time=17-JUL-08
    channel ORA_DISK_1: starting piece 1 at 18-JUL-08
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/18/2008 10:59:48
    ORA-01858: a non-numeric character was found where a numeric was expected
    I suspect that rman is performing, at the end of backup, some internal work (store something in control file based catalog or so) and catches ORA-01858.
    The destination catalog is local catalog (not nfs mounted remote dir).
    RMAN is spawned from the same node the Oracle Database is running on.
    I tested it on two servers.
    Error occurs on both of them:
    version 10g (ia-32) - flash recovery area on filesystem
    and version 11g (Aix) - flash on ASM
    RMAN-oracle10> show all ;
    using target database controlfile instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    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 ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/10gSE/dbs/snap_dbname.dbf'; # default
    RMAN-oracle11> show all ;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name O2DB are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO COMPRESSED BACKUPSET;
    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 COMPRESSION ALGORITHM 'BZIP2'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbname_1/dbs/snapcf_dbname.f';
    How to diagnose the problem?
    How check what RMAN is exactly doing when error occurs?
    Or maybe there is better way to achieve this:
    I want to move backupset from asm realm to remote server without storing them on local, non asm disk.
    Any suggestions kindly welcome!
    Thanx!

    Solution:
    NLS_DATE_FORMAT mus be set mannualy;
    export NLS_DATE_FORMAT='YYYY_MM_DD'
    solved the problem..
    https://metalink.oracle.com/metalink/plsql/f?p=130:15:12788270042070262572::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,6198368,1,1,1,helvetica
    Metalinking before posting is the rule of thumb : )

  • Got error when creating a standby DB from rman:  no backup or copy... Why?

    We try to create standby database from a production DB on another server (10.2.0.4). The RMAN backup is in the nfs file system which is also mounted to the target server (the DR box). So, the access path for the rman backup is the same look from primary DB server and DR DB server. I started the RMAN run:
    RMAN> RUN
    2> {
    3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    4> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
    5> DUPLICATE TARGET DATABASE for standby
    6> nofilenamecheck
    7> dorecover;
    8> }
    9>
    10> exit
    using target database control file instead of recovery catalog
    allocated channel: aux1
    channel aux1: sid=582 devtype=DISK
    allocated channel: aux2
    channel aux2: sid=584 devtype=DISK
    Starting Duplicate Db at 21-JUN-12
    contents of Memory Script:
    set until scn 12198261770353;
    restore clone standby controlfile;
    sql clone 'alter database mount standby database';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 21-JUN-12
    released channel: aux1
    released channel: aux2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/21/2012 16:33:36
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    ===========================================================================
    The backups should have controlfile. There is rman show all display:
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/inbound/online/controlfile_auto%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/inbound/online/%d_%T_%t_%s';
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/inbound/online/snapcf_inbound.f';
    Why and how to fix? Thanks for help!

    Here is the list of command:
    RMAN> list backup of controlfile ;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5518 Full 4.57M DISK 00:00:07 17-JUN-12
    BP Key: 5518 Status: AVAILABLE Compressed: NO Tag: TAG20120617T035926
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120617-00
    Control File Included: Ckp SCN: 12197994840698 Ckp time: 17-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5522 Full 4.57M DISK 00:00:00 18-JUN-12
    BP Key: 5522 Status: AVAILABLE Compressed: NO Tag: TAG20120618T010158
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120618-00
    Control File Included: Ckp SCN: 12198041382572 Ckp time: 18-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5526 Full 4.57M DISK 00:00:01 19-JUN-12
    BP Key: 5526 Status: AVAILABLE Compressed: NO Tag: TAG20120619T010352
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120619-00
    Control File Included: Ckp SCN: 12198090424606 Ckp time: 19-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5530 Full 4.57M DISK 00:00:02 20-JUN-12
    BP Key: 5530 Status: AVAILABLE Compressed: NO Tag: TAG20120620T010304
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120620-00
    Control File Included: Ckp SCN: 12198146424201 Ckp time: 20-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5534 Full 4.57M DISK 00:00:02 21-JUN-12
    BP Key: 5534 Status: AVAILABLE Compressed: NO Tag: TAG20120621T010357
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
    Control File Included: Ckp SCN: 12198210334547 Ckp time: 21-JUN-12
    ==================================================================
    I tried to catalog the controlfile:
    RMAN> catalog controlfilecopy '/backup/inbound/online/controlfile_autoc-2080040856-20120621-00';
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of catalog command on default channel at 06/21/2012 17:24:32
    ORA-19563: control file header validation failed for file /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
    ====================================================================
    We have level 1 backup everyday, except Sunday. I have level 0 backup on Sunday. I alos tried the metalink note RMAN Duplicate For Standby Fails with Rman-06024: No Backup Or Copy Of The Control File Found To Restore [ID 466321.1]. It does not work.
    Thanks for help!

  • RMAN: Increment backup very slow

    Hi All,
    We have Datawarehouse database having size around 7TB. Increment backup performance is extremely poor it is taking approx 14hrs to complete the process. We have also enabled block change tracking but failed to meet target.
    Below mentioned DB info & RMAN configuration parameters:
    DB: 11.1.0.6
    OS: Linux 2.6.18-128.el5 x86_64
    System has 16 processor when more than two process per CPU i.e. 32
    CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01copy/control_bkp/autobackup_control_file%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 13 BACKUP TYPE TO COMPRESSED BACKUPSET;
    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 COMPRESSION ALGORITHM 'BZIP2';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbs/snapcf_PRODDB.f'; # default
    Thanks in advance.

    Thnaks for reply.
    Have you configured Compressed backups?
    --> Yes. with below command.
    RMAN> backup as compressed backupset incremental level 1 tag=$v_tag database;
    Have you allocated channels ?
    --> Yes.
    allocate channel backup_disk1 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk2 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk3 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk4 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk5 type disk format '$v_bdest/%U' maxpiecesize 10G;
    What is the Large pool size configured? try to increase.
    --> large_pool_size=1073741824
    Is backup to DISK or TAPE? mentioned in script?
    --> Backup goes to DISK only.
    How is DISK performance?
    --> How can we calculate DISK performance on LINUX?
    Regards,

  • Restoring and Recovering from RMAN cold backup

    DB Version: 11gR2
    os : Solaris
    Before dropping a DB we had taken an RMAN backup of the DB using
    RMAN> backup database;We hadn't set a FORMAT (like db_%d_S_%s_P_%p_T_%t) for this DB , so the backups went to ORACLE_HOME/dbs directory. The 2 backup files are
    /u02/app/oracle/11.2/db/dbs/01mo9fms_1_1
    /u02/app/oracle/11.2/db/dbs/02mo9fnc_1_1  -- spfile and control fileNow we need to recreate this DB on a new server.
    In the new server, we've placed the backup files in /u04/backup/rmanbkp .
    Since We hadn't set a FORMAT parameter for the original DB which we have dropped what format i will give during restore?
    Will RMAN automatically recognize the FORMAT of the backup piece and restore ?
    RMAN> run
    allocate channel c1 device type disk format 'i_dont_know_the_format';
    allocate channel c2 device type disk format 'i_dont_know_the_format';
    restore controlfile;
    restore database;
    }This the SHOW ALL output from the DB we have dropped .
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name BRCFTST are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u02/app/oracle/11.2/db/snapcf_brcftst.f'; # defaultAs you can see we hadn't set the format explicitly , ie. the line
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT is missing

    Hi,
    Before dropping a DB we had taken an RMAN backup.I hope you were in mount mode.
    Will RMAN automatically recognize the FORMAT of the backup piece and restore ?No it won't.
    First you have to restore a controlfile in nomount mode with:
    restore controlfile from '/u04/backup/rmanbkp /02mo9fnc_1_1';
    and do alter database mount.
    Than you have to run "catalog start with '/u04/backup/rmanbkp'; " so the instance now knows where to find the pieces.
    Now you can run a restore database command.
    Than open the database with resetlogs.
    Regards,
    Tycho

  • Error in RMAN TAPE BACKUP

    Dear Gurus,
    I got the following error in RMAN TAPE backup.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of delete command on default channel at 09/20/2011 02:36:58
    ORA-15028: ASM file '+ASMFLASH/gcprod/archivelog/2011_09_15/thread_2_seq_55857.2176.761912673' not dropped; currently being accessed
    RMAN>
    Recovery Manager complete.my RMAN BACKUP Script is:
    rman target sys/*****@gcprod1  nocatalog  << EOF
    spool log to $v_bdest/clean_catalog_TAPE.log append;
    run {
    allocate channel c1 type 'sbt_tape' parms
    'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    #crosscheck backupset;
    #crosscheck copy;
    #crosscheck archivelog all;
    # included on 21Jan2011 at 9:18 PM
    #delete noprompt expired backup;
    delete noprompt obsolete;
    #delete noprompt expired archivelog all;
    # included on 21Jan2011 at 9:18 PM
    release channel c1;
    exit
    EOFMy RMAN RETENTION POLICY IS:
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/oracle/product/10.2.0.1/db_1/dbs/snapcf_gcprod1.f';According to retention policy archivelogs of past 3 days should be present rest and all , i have written a script to delete and it is performing well from past 6 months, but now recently we got this error
    we have enough archivelog space.
    and the archive log pointing in this error is on 15th september archivelog.....today date is 20th september....
    My archive log was stored in asm .... i went there and saw that still 15th september archivelogs are present there.
    Please help me regarding this
    Regards,
    Vamsi.....

    For RMAN topics, please use: {forum:id=74}.

  • Clonning using RMAN Cold Backup?

    Hi,
    I have a COLD RMAN backup in prod server and now i want to clone test db using this backup through RMAN. I have 2 question regarding this
    1) Where do i need to place the prod RMAN COLD backup files in test server?
    2) If i ran below command how RMAN will know where did i placed the backup in test server?
    In Test Server
    RMAN> duplicate target database to test;DB Version is : 10.2.0.4
    Thanks in advance

    thanks. Now it is unable to restore the datafiles from rman backup.Below steps i tried.
    [oracle@Test test1]$ rman target /
    Recovery Manager: Release 10.2.0.4.0 - Production on Tue Feb 21 08:58:46 2012
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initprod2.ora';
    Oracle instance started
    Total System Global Area     603979776 bytes
    Fixed Size                     1268896 bytes
    Variable Size                163578720 bytes
    Database Buffers             436207616 bytes
    Redo Buffers                   2924544 bytes
    RMAN> restore controlfile from '/u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak';
    Starting restore at 21-FEB-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
    output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control01.ctl
    output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control02.ctl
    output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control03.ctl
    Finished restore at 21-FEB-12
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> catalog start with '/u01/app/oracle/product/10.2.0/backup/test1';
    Starting implicit crosscheck backup at 21-FEB-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 3 objects
    Finished implicit crosscheck backup at 21-FEB-12
    Starting implicit crosscheck copy at 21-FEB-12
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 21-FEB-12
    searching for all files in the recovery area
    cataloging files...
    no files cataloged
    searching for all files that match the pattern /u01/app/oracle/product/10.2.0/backup/test1
    List of Files Unknown to the Database
    =====================================
    File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
    File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak
    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/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
    File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak
    RMAN>
    RMAN> restore database;
    Starting restore at 21-FEB-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /u01/app/oracle/oradata/prod2/system.dbf
    restoring datafile 00002 to /u01/app/oracle/oradata/prod2/usr04.dbf
    restoring datafile 00003 to /u01/app/oracle/oradata/prod2/undo.dbf
    restoring datafile 00004 to /u01/app/oracle/oradata/prod2/sysaux.dbf
    restoring datafile 00005 to /u01/app/oracle/oradata/prod2/p1_01.dbf
    restoring datafile 00006 to /u01/app/oracle/oradata/prod2/p2_01.dbf
    channel ORA_DISK_1: reading from backup piece /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
    ORA-19870: error reading backup piece /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
    ORA-19504: failed to create file "/u01/app/oracle/oradata/prod2/system.dbf"
    ORA-27040: file create error, unable to create file
    Linux Error: 2: No such file or directory
    failover to previous backup
    creating datafile fno=1 name=/u01/app/oracle/oradata/prod2/system.dbf
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/21/2012 09:01:09
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '/u01/app/oracle/oradata/prod2/system.dbf'

Maybe you are looking for