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

Similar Messages

  • 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.

  • 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

  • "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

  • CONFIGURE BACKUP OPTIMIZATION ON;

    CONFIGURE BACKUP OPTIMIZATION ON;
    above cmd only working on "sbt" type device or it is working also "disk".
    plz. let me know. sir.
    thanx in advance.

    From the docs:
    Requirements for Backup Optimization
    Backup optimization is used 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.
    Only one type of channel is allocated, that is, you do not mix channels of type DISK and sbt in the same backup command.
    http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1008.htm#i1008304

  • Backup Optimization vs redundancy of 3.

    backup optimization
    A configuration enabling RMAN to automatically skip backups of files that it has already backed up. You enable and disable backup optimization with theCONFIGURE command.
    Redundancy is set to 3.
    So ,  day one i have the following backup plus archive log
    Backup 1
    All DB File
    Arc_1
    Arc_2
    Second day
    Backup 2
    All DB File
    Arc_3
    Arc_4
    Third day
    Backup 3
    All DB File
    Arc_5
    Arc_6
    Fourth day
    Backup 4
    All DB File
    Arc_7
    Arc_8
    If I only had the last backup but was asked to restore to the to a point in time of yesterday,  would my redundancy 3 not mean that everything from backup 3 be on my backup 4 ?
    I believe that only the files added since backup 3 completed is on backup 4.

    Thank you.
    What you say makes sense. As my one friend said to me ,  if you planning on being able to restore backup 3's archvied files and you dont have your backup duplexed, then you cannot restore backup 3 archived files.  So,  if optimization is turned on,  duplex to 2 tapes.
    Weighin in on the likelyhood of the situation.
    Ron

  • 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

  • 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....

  • Ability to "task schedule" via small utilities backup/optimize

    Include small utilites with Lightroom that can be used with the system "task scheduler" that will perform catalogue backup and optimize on a user defined schedule.

    (Replying to myself here no edit option) Is there a way to optimize the catalog via single command line or in a bat file with sqlite3.exe and/or Contig.exe?

  • Unable to restore and recover my Database from RMAN Backup

    Dear All,
    Iam practicing RMAN in Windows environment.
    My configurations are
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%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 NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
    Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
    then i tried to startup the DB but it is saying
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
    So i tried to restore the Database with my rman backup
    RMAN> restore database;
    But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
    So, i am unable to recover my DB
    Please tell me whether i am doing any mistake, what is the solution for my problem.
    Thanks in advance
    Mahi

    All you restored was your datafiles.
    Now issue recover database and that will apply the archive logs.
    This is in the oracle documentation.
    "You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
    In this case after issuing restore database in RMAN, then issue this.
    "Recover database"
    It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

  • Please review my backup plan and give me any instruction

    Hi every one.
    I set up a database and plant a backup strategy with RMAN that is:
    - Backup incremental level 0 on every Sunday
    - Backup incremental level 1 on other days.
    My database is Oracle Enterprise 11gR2 - Linux amd64
    The backup task scheduled with crontab on Linux CentOS 5.3. My RMAN commands are bellow. Please help me to review and show any risks may happen with my strategy.
    The Incremental Level 0 RMAN:
    RUN {
            allocate channel bkp device type disk;
            backup as compressed backupset incremental level 0 tag 'DB_BKP_FULL' database include current controlfile;
            backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
            crosscheck archivelog all;
            crosscheck backup;
            delete noprompt obsolete;
            release channel bkp;
    }The incremental level 1 RMAN:
    RUN {
    allocate channel bkp device type disk;
    backup as compressed backupset incremental level 1 tag 'DB_BKP_FULL' database include current controlfile;
    backup as compressed backupset tag 'ARCL_BKP_INCR' archivelog all delete input;
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt obsolete;
    release channel bkp;
    }And this is my RMAN repository configuration:
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name OFM are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F_myautobackup_ctrlfile';
    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 '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ofm.f'; # defaultAny suggestion is appreciated.
    Regards
    Edited by: Cuong Pham on Dec 13, 2012 11:13 AM
    Edited by: Cuong Pham on Dec 13, 2012 11:15 AM

    It might be similiar to the way Amazon does it - if you set the eBook price higher at one store than every other store, that store has the right to lower the price and collect the lower price for it (price matching).
    So you sell your book at Amazon, Barnes and Noble, and Apple.
    At Amazon it's $5.
    At Barnes and Noble it's $5.
    At Apple it's $10.
    Apple has the right to lower the price to $5 and collect the commission on $5 and only remit you your commission on the $5.
    That's my GUESS. I don't actually know, I just know what's how Amazon does it.

  • Error while Running backup

    Hi
    I have downloaded the Oracle Secure Backup Cloud Software and have installed the software for secure backup but while running Backup database command i am getting the below error. Any clue?
    RMAN> backup database;
    Starting backup at 30-APR-10
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 04/30/2010 02:58:34
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    KBHS-00715: HTTP error occurred 'internal-error'
    RMAN> show all
    2> ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/home/oracle/osbws/libosbws11.so ENV=(OSB_WS_PFILE=/home/oracle/osbws/osbws.cfg)';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE ON;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/mnt/database/dbtest/db/tech_st/10.2.0/dbs/snapcf_TEST.f'; # default
    Thanks
    Edited by: user6803831 on Apr 30, 2010 12:42 AM

    Hi,
    oraInst.loc (/etc/oraInst.loc) points to directory without permissions: /u01/app/oracle/oraInventoryPlease make sure that applmgr user has read/write/execute permission on the oraInventory directory.
    Please look in to the latest OUI log file located in the central inventory /clonehot/apps/inst/apps/PROD_apps/admin/oraInventory/logs/cloneActions_<timestamp> for more detailsAny details about the error in this log file?
    Thanks,
    Hussein

  • No backup or copy of datafile 4 found to restore Error ??

    Hi,
    I have a 2 Virtual machine with Oracle 10g on OEL.
    Let's say machine 1 is called : OEL-SOURCE MACHINE
    Let's say machine 1 is called : DR-TARGET MACHINE
    When i am trying to restore rman backup on 2 machine 'DR', it comes with the message "RMAN-06023: no backup or copy of datafile 4 found to restore"
    Here are the steps that i followed on Machine 1 i.e. OEL-SOURCE MACHINE :
    RMAN>
    Oracle instance started
    database mounted
    database opened
    Total System Global Area     285212672 bytes
    Fixed Size                     1218992 bytes
    Variable Size                 83887696 bytes
    Database Buffers             197132288 bytes
    Redo Buffers                   2973696 bytes
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    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 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 NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/va00/oracle/product/10.2.0/db_1/dbs/snapcf_mytest.f'; # default
    RMAN> backup database plus archivelog;
    Starting backup at 26-OCT-10
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=14 recid=12 stamp=733426429
    input archive log thread=1 sequence=15 recid=13 stamp=733426789
    input archive log thread=1 sequence=16 recid=14 stamp=733426795
    input archive log thread=1 sequence=17 recid=15 stamp=733426801
    input archive log thread=1 sequence=18 recid=16 stamp=733426801
    input archive log thread=1 sequence=19 recid=17 stamp=733426855
    input archive log thread=1 sequence=20 recid=18 stamp=733426856
    input archive log thread=1 sequence=21 recid=19 stamp=733426861
    input archive log thread=1 sequence=22 recid=20 stamp=733426862
    input archive log thread=1 sequence=23 recid=21 stamp=733436688
    input archive log thread=1 sequence=24 recid=22 stamp=733437082
    channel ORA_DISK_1: starting piece 1 at 26-OCT-10
    channel ORA_DISK_1: finished piece 1 at 26-OCT-10
    piece handle=/va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203122_6dh07d2o_.bkp tag=TAG20101026T203122 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 26-OCT-10
    Starting backup at 26-OCT-10
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_system_6dcg5mfo_.dbf
    input datafile fno=00005 name=/va02/oracle/oradata/mytest/company_tab_01.dbf
    input datafile fno=00006 name=/va03/oracle/oradata/mytest/company_idx_01.dbf
    input datafile fno=00003 name=/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_sysaux_6dcg5mgg_.dbf
    input datafile fno=00002 name=/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_undotbs1_6dcg5mnx_.dbf
    input datafile fno=00004 name=/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_users_6dcg5moq_.dbf
    channel ORA_DISK_1: starting piece 1 at 26-OCT-10
    channel ORA_DISK_1: finished piece 1 at 26-OCT-10
    piece handle=/va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/backupset/2010_10_26/o1_mf_nnndf_TAG20101026T203125_6dh07g07_.bkp tag=TAG20101026T203125 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:05
    Finished backup at 26-OCT-10
    Starting backup at 26-OCT-10
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=25 recid=23 stamp=733437151
    channel ORA_DISK_1: starting piece 1 at 26-OCT-10
    channel ORA_DISK_1: finished piece 1 at 26-OCT-10
    piece handle=/va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203231_6dh09jj6_.bkp tag=TAG20101026T203231 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    Finished backup at 26-OCT-10
    Starting Control File and SPFILE Autobackup at 26-OCT-10
    piece handle=/va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/autobackup/2010_10_26/o1_mf_s_733437154_6dh09lhr_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 26-OCT-10This completed the RMAN
    Now i listed the backup with RMAN
    RMAN> list backup
    2> ;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    9       1.99M      DISK        00:00:02     26-OCT-10     
            BP Key: 9   Status: AVAILABLE  Compressed: NO  Tag: TAG20101026T203122
            Piece Name: /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203122_6dh07d2o_.bkp
      List of Archived Logs in backup set 9
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    14      545557     26-OCT-10 545610     26-OCT-10
      1    15      545610     26-OCT-10 546080     26-OCT-10
      1    16      546080     26-OCT-10 546083     26-OCT-10
      1    17      546083     26-OCT-10 546086     26-OCT-10
      1    18      546086     26-OCT-10 546088     26-OCT-10
      1    19      546088     26-OCT-10 546114     26-OCT-10
      1    20      546114     26-OCT-10 546116     26-OCT-10
      1    21      546116     26-OCT-10 546119     26-OCT-10
      1    22      546119     26-OCT-10 546121     26-OCT-10
      1    23      546121     26-OCT-10 567862     26-OCT-10
      1    24      567862     26-OCT-10 568231     26-OCT-10
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    10      Full    515.82M    DISK        00:01:04     26-OCT-10     
            BP Key: 10   Status: AVAILABLE  Compressed: NO  Tag: TAG20101026T203125
            Piece Name: /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/backupset/2010_10_26/o1_mf_nnndf_TAG20101026T203125_6dh07g07_.bkp
      List of Datafiles in backup set 10
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 568235     26-OCT-10 /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_system_6dcg5mfo_.dbf
      2       Full 568235     26-OCT-10 /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_undotbs1_6dcg5mnx_.dbf
      3       Full 568235     26-OCT-10 /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_sysaux_6dcg5mgg_.dbf
      4       Full 568235     26-OCT-10 /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_users_6dcg5moq_.dbf
      5       Full 568235     26-OCT-10 /va02/oracle/oradata/mytest/company_tab_01.dbf
      6       Full 568235     26-OCT-10 /va03/oracle/oradata/mytest/company_idx_01.dbf
    BS Key  Size       Device Type Elapsed Time Completion Time
    11      17.50K     DISK        00:00:01     26-OCT-10     
            BP Key: 11   Status: AVAILABLE  Compressed: NO  Tag: TAG20101026T203231
            Piece Name: /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203231_6dh09jj6_.bkp
      List of Archived Logs in backup set 11
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    25      568231     26-OCT-10 568267     26-OCT-10
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    12      Full    6.80M      DISK        00:00:00     26-OCT-10     
            BP Key: 12   Status: AVAILABLE  Compressed: NO  Tag: TAG20101026T203234
            Piece Name: /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/autobackup/2010_10_26/o1_mf_s_733437154_6dh09lhr_.bkp
      Control File Included: Ckp SCN: 568273       Ckp time: 26-OCT-10
      SPFILE Included: Modification time: 26-OCT-10
    RMAN> Then i reported obsolete, and as we can see my datafile is not listed here which is good.
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Archive Log          12     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_14_6dgotdvb_.arc
    Archive Log          13     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_15_6dgp5nyg_.arc
    Archive Log          14     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_16_6dgp5tz4_.arc
    Archive Log          15     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_17_6dgp610j_.arc
    Archive Log          16     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_18_6dgp612w_.arc
    Archive Log          17     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_19_6dgp7q9b_.arc
    Archive Log          18     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_20_6dgp7rrq_.arc
    Archive Log          19     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_21_6dgp7x5d_.arc
    Archive Log          20     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_22_6dgp7yln_.arc
    Archive Log          21     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_23_6dgztytj_.arc
    Archive Log          22     26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/archivelog/2010_10_26/o1_mf_1_24_6dh07bff_.arc
    Backup Set           9      26-OCT-10        
    Backup Piece       9      26-OCT-10          /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203122_6dh07d2o_.bkpI transferred complete RMAN folder to 2nd machine & switched to second Machine i..e DR-TARGET MACHINE
    [oracle@localhost ~]$ export ORACLE_SID=mytest
    [oracle@localhost ~]$ rman target /
    Recovery Manager: Release 10.2.0.1.0 - Production on Tue Oct 26 20:48:49 2010
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> set dbid=2432458060;
    executing command: SET DBID
    RMAN> startup nomount;   
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/va00/oracle/product/10.2.0/db_1/dbs/initmytest.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area     159383552 bytes
    Fixed Size                     1218268 bytes
    Variable Size                 54528292 bytes
    Database Buffers             100663296 bytes
    Redo Buffers                   2973696 bytes
    RMAN> restore spfile from '/tmp/rman_backups_third_set/autobackup/2010_10_26/o1_mf_s_733437154_6dh09lhr_.bkp';
    Starting restore at 26-OCT-10
    using channel ORA_DISK_1
    channel ORA_DISK_1: autobackup found: /tmp/rman_backups_third_set/autobackup/2010_10_26/o1_mf_s_733437154_6dh09lhr_.bkp
    channel ORA_DISK_1: SPFILE restore from autobackup complete
    Finished restore at 26-OCT-10
    RMAN> shutdown immediate
    Oracle instance shut down
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area     285212672 bytes
    Fixed Size                     1218992 bytes
    Variable Size                 83887696 bytes
    Database Buffers             197132288 bytes
    Redo Buffers                   2973696 bytes
    RMAN> restore controlfile from '/tmp/rman_backups_third_set/autobackup/2010_10_26/o1_mf_s_733437154_6dh09lhr_.bkp';
    Starting restore at 26-OCT-10
    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:02
    output filename=/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/controlfile/o1_mf_6dh1d2o5_.ctl
    output filename=/va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/controlfile/o1_mf_6dh1d31n_.ctl
    Finished restore at 26-OCT-10
    RMAN> shutdown immediate
    Oracle instance shut down
    RMAN> startup force mount;
    Oracle instance started
    database mounted
    Total System Global Area     285212672 bytes
    Fixed Size                     1218992 bytes
    Variable Size                 83887696 bytes
    Database Buffers             197132288 bytes
    Redo Buffers                   2973696 bytes
    RMAN> catalog start with '/tmp/rman_backups_third_set/';
    searching for all files that match the pattern /tmp/rman_backups_third_set/
    List of Files Unknown to the Database
    =====================================
    File Name: /tmp/rman_backups_third_set/autobackup/2010_10_26/o1_mf_s_733437154_6dh09lhr_.bkp
    File Name: /tmp/rman_backups_third_set/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203231_6dh09jj6_.bkp
    File Name: /tmp/rman_backups_third_set/backupset/2010_10_26/o1_mf_nnndf_TAG20101026T203125_6dh07g07_.bkp
    File Name: /tmp/rman_backups_third_set/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203122_6dh07d2o_.bkp
    File Name: /tmp/rman_backups_third_set/onlinelog/o1_mf_1_6dcg8yw6_.log
    File Name: /tmp/rman_backups_third_set/onlinelog/o1_mf_3_6dcg92d5_.log
    File Name: /tmp/rman_backups_third_set/onlinelog/o1_mf_2_6dcg90tg_.log
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_18_6dgp612w_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_24_6dh07bff_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_21_6dgp7x5d_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_28_6dh0dpsb_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_14_6dgotdvb_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_22_6dgp7yln_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_29_6dh0dqoy_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_26_6dh0df44_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_16_6dgp5tz4_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_23_6dgztytj_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_19_6dgp7q9b_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_17_6dgp610j_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_20_6dgp7rrq_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_15_6dgp5nyg_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_27_6dh0djqt_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_25_6dh09h1c_.arc
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /tmp/rman_backups_third_set/autobackup/2010_10_26/o1_mf_s_733437154_6dh09lhr_.bkp
    File Name: /tmp/rman_backups_third_set/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203231_6dh09jj6_.bkp
    File Name: /tmp/rman_backups_third_set/backupset/2010_10_26/o1_mf_nnndf_TAG20101026T203125_6dh07g07_.bkp
    File Name: /tmp/rman_backups_third_set/backupset/2010_10_26/o1_mf_annnn_TAG20101026T203122_6dh07d2o_.bkp
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_18_6dgp612w_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_24_6dh07bff_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_21_6dgp7x5d_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_28_6dh0dpsb_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_14_6dgotdvb_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_22_6dgp7yln_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_29_6dh0dqoy_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_26_6dh0df44_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_16_6dgp5tz4_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_23_6dgztytj_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_19_6dgp7q9b_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_17_6dgp610j_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_20_6dgp7rrq_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_15_6dgp5nyg_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_27_6dh0djqt_.arc
    File Name: /tmp/rman_backups_third_set/archivelog/2010_10_26/o1_mf_1_25_6dh09h1c_.arc
    List of Files Which Where Not Cataloged
    =======================================
    File Name: /tmp/rman_backups_third_set/onlinelog/o1_mf_1_6dcg8yw6_.log
      RMAN-07529: Reason: catalog is not supported for this file type
    File Name: /tmp/rman_backups_third_set/onlinelog/o1_mf_3_6dcg92d5_.log
      RMAN-07529: Reason: catalog is not supported for this file type
    File Name: /tmp/rman_backups_third_set/onlinelog/o1_mf_2_6dcg90tg_.log
      RMAN-07529: Reason: catalog is not supported for this file type
    Here comes the issue ...when i try to restore the db
    RMAN> restore database;
    Starting restore at 26-OCT-10
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 10/26/2010 20:53:13
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restoreSO MY QUESTION OR DOUBT IS WHY AT THE END IT FAILS THAT THERE IS NO BACKUP FOR DATAFILE 1,2,3,4 ??? AS WE CAN SEE ABOVE IT IS PRESENT IN MY BACKUPSET ??
    ANY IDEA /HINTS/TIPS ?
    I searched on google and somebody mentioned to a similar case that it could be a problem with 'CONFIGURE CONTROLFILE AUTOBACKUP OFF' where as in my case i have set it to 'CONFIGURE CONTROLFILE AUTOBACKUP ON'
    Somehow looks like that the control file is not having latest backup info ... :-( I already took a fresh backup 2 times and landed up in same issue.. not sure where i am doing a mistake.
    Regards
    Learner

    No replies ... :-(
    Meanwhile i also looked in the trace file folder to see if there are any clues. here goes the content of alert_log.file
    Tue Oct 26 23:28:59 2010
    Shutting down instance: further logons disabled
    Tue Oct 26 23:28:59 2010
    Stopping background process CJQ0
    Tue Oct 26 23:28:59 2010
    Stopping background process MMNL
    Tue Oct 26 23:28:59 2010
    Stopping background process MMON
    Tue Oct 26 23:28:59 2010
    Shutting down instance (immediate)
    License high water mark = 5
    Tue Oct 26 23:29:00 2010
    Stopping Job queue slave processes
    Tue Oct 26 23:29:00 2010
    Job queue slave processes stopped
    Waiting for dispatcher 'D000' to shutdown
    All dispatchers and shared servers shutdown
    Tue Oct 26 23:29:05 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Tue Oct 26 23:29:16 2010
    alter database close
    Tue Oct 26 23:29:16 2010
    ORA-1109 signalled during: alter database close...
    Tue Oct 26 23:29:16 2010
    alter database dismount
    Completed: alter database dismount
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Tue Oct 26 23:29:36 2010
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
      processes                = 150
      __shared_pool_size       = 75497472
      __large_pool_size        = 4194304
      __java_pool_size         = 4194304
      __streams_pool_size      = 0
      sga_target               = 285212672
      control_files            = /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/controlfile/o1_mf_6dh49dgy_.ctl, /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/controlfile/o1_mf_6dh49dkr_.ctl
      db_block_size            = 8192
      __db_cache_size          = 197132288
      compatible               = 10.2.0.1.0
      db_file_multiblock_read_count= 16
      db_create_file_dest      = /va00/oracle/product/10.2.0/db_1/oradata
      db_recovery_file_dest    = /va00/oracle/product/10.2.0/db_1/flash_recovery_area
      db_recovery_file_dest_size= 1572864000
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      dispatchers              = (PROTOCOL=TCP) (SERVICE=mytestXDB)
      job_queue_processes      = 10
      background_dump_dest     = /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump
      user_dump_dest           = /va00/oracle/product/10.2.0/db_1/admin/mytest/udump
      core_dump_dest           = /va00/oracle/product/10.2.0/db_1/admin/mytest/cdump
      audit_file_dest          = /va00/oracle/product/10.2.0/db_1/admin/mytest/adump
      db_name                  = mytest
      open_cursors             = 300
      pga_aggregate_target     = 94371840
    PMON started with pid=2, OS id=4483
    PSP0 started with pid=3, OS id=4485
    MMAN started with pid=4, OS id=4487
    DBW0 started with pid=5, OS id=4489
    LGWR started with pid=6, OS id=4491
    CKPT started with pid=7, OS id=4493
    SMON started with pid=8, OS id=4495
    RECO started with pid=9, OS id=4497
    CJQ0 started with pid=10, OS id=4499
    MMON started with pid=11, OS id=4501
    Tue Oct 26 23:29:38 2010
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=12, OS id=4503
    Tue Oct 26 23:29:38 2010
    starting up 1 shared server(s) ...
    Tue Oct 26 23:29:39 2010
    alter database mount
    Tue Oct 26 23:29:43 2010
    Setting recovery target incarnation to 3
    Tue Oct 26 23:29:43 2010
    Successful mount of redo thread 1, with mount id 2432571107
    Tue Oct 26 23:29:43 2010
    Database mounted in Exclusive Mode
    Completed: alter database mount
    Tue Oct 26 23:30:00 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4489.trc:
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_system_6dcg5mfo_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:30:00 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4489.trc:
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_undotbs1_6dcg5mnx_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:30:00 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4489.trc:
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_sysaux_6dcg5mgg_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:30:00 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4489.trc:
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_users_6dcg5moq_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:30:00 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4489.trc:
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: '/va02/oracle/oradata/mytest/company_tab_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:30:00 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4489.trc:
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: '/va03/oracle/oradata/mytest/company_idx_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:32:16 2010
    Shutting down instance: further logons disabled
    Tue Oct 26 23:32:16 2010
    Stopping background process MMNL
    Tue Oct 26 23:32:16 2010
    Stopping background process CJQ0
    Tue Oct 26 23:32:17 2010
    Stopping background process MMON
    Tue Oct 26 23:32:17 2010
    Shutting down instance (immediate)
    License high water mark = 5
    Tue Oct 26 23:32:17 2010
    Stopping Job queue slave processes
    Tue Oct 26 23:32:17 2010
    Job queue slave processes stopped
    Waiting for dispatcher 'D000' to shutdown
    All dispatchers and shared servers shutdown
    Tue Oct 26 23:32:23 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Tue Oct 26 23:32:33 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Tue Oct 26 23:32:38 2010
    Process OS id : 4514 alive after kill
    Errors in file
    Tue Oct 26 23:32:39 2010
    PMON failed to acquire latch, see PMON dump
    Tue Oct 26 23:32:40 2010
    alter database close
    Tue Oct 26 23:32:40 2010
    ORA-1109 signalled during: alter database close...
    Tue Oct 26 23:32:40 2010
    alter database dismount
    Completed: alter database dismount
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Tue Oct 26 23:36:35 2010
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
      processes                = 150
      __shared_pool_size       = 75497472
      __large_pool_size        = 4194304
      __java_pool_size         = 4194304
      __streams_pool_size      = 0
      sga_target               = 285212672
      control_files            = /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/controlfile/o1_mf_6dcg8wco_.ctl, /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/controlfile/o1_mf_6dcg8wps_.ctl
      db_block_size            = 8192
      __db_cache_size          = 197132288
      compatible               = 10.2.0.1.0
      db_file_multiblock_read_count= 16
      db_create_file_dest      = /va00/oracle/product/10.2.0/db_1/oradata
      db_recovery_file_dest    = /va00/oracle/product/10.2.0/db_1/flash_recovery_area
      db_recovery_file_dest_size= 1572864000
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      dispatchers              = (PROTOCOL=TCP) (SERVICE=mytestXDB)
      job_queue_processes      = 10
      background_dump_dest     = /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump
      user_dump_dest           = /va00/oracle/product/10.2.0/db_1/admin/mytest/udump
      core_dump_dest           = /va00/oracle/product/10.2.0/db_1/admin/mytest/cdump
      audit_file_dest          = /va00/oracle/product/10.2.0/db_1/admin/mytest/adump
      db_name                  = mytest
      open_cursors             = 300
      pga_aggregate_target     = 94371840
    PMON started with pid=2, OS id=4622
    PSP0 started with pid=3, OS id=4624
    MMAN started with pid=4, OS id=4626
    DBW0 started with pid=5, OS id=4628
    LGWR started with pid=6, OS id=4630
    CKPT started with pid=7, OS id=4632
    SMON started with pid=8, OS id=4634
    RECO started with pid=9, OS id=4636
    CJQ0 started with pid=10, OS id=4638
    MMON started with pid=11, OS id=4640
    MMNL started with pid=12, OS id=4642
    Tue Oct 26 23:36:36 2010
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 shared server(s) ...
    Tue Oct 26 23:36:47 2010
    Deleted Oracle managed file /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/controlfile/o1_mf_6dcg8wco_.ctl
    Deleted Oracle managed file /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/controlfile/o1_mf_6dcg8wps_.ctl
    Tue Oct 26 23:36:58 2010
    Shutting down instance: further logons disabled
    Tue Oct 26 23:36:58 2010
    Stopping background process CJQ0
    Tue Oct 26 23:36:58 2010
    Stopping background process MMNL
    Tue Oct 26 23:36:58 2010
    Stopping background process MMON
    Tue Oct 26 23:36:58 2010
    Shutting down instance (immediate)
    License high water mark = 3
    Tue Oct 26 23:36:58 2010
    Stopping Job queue slave processes
    Tue Oct 26 23:36:58 2010
    Job queue slave processes stopped
    Waiting for dispatcher 'D000' to shutdown
    All dispatchers and shared servers shutdown
    Tue Oct 26 23:37:00 2010
    alter database close
    ORA-1507 signalled during: alter database close...
    Tue Oct 26 23:37:00 2010
    alter database dismount
    ORA-1507 signalled during: alter database dismount...
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Tue Oct 26 23:37:10 2010
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
      processes                = 150
      __shared_pool_size       = 75497472
      __large_pool_size        = 4194304
      __java_pool_size         = 4194304
      __streams_pool_size      = 0
      sga_target               = 285212672
      control_files            = /va00/oracle/product/10.2.0/db_1/oradata/MYTEST/controlfile/o1_mf_6dhc2ymb_.ctl, /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/controlfile/o1_mf_6dhc2yp5_.ctl
      db_block_size            = 8192
      __db_cache_size          = 197132288
      compatible               = 10.2.0.1.0
      db_file_multiblock_read_count= 16
      db_create_file_dest      = /va00/oracle/product/10.2.0/db_1/oradata
      db_recovery_file_dest    = /va00/oracle/product/10.2.0/db_1/flash_recovery_area
      db_recovery_file_dest_size= 1572864000
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      dispatchers              = (PROTOCOL=TCP) (SERVICE=mytestXDB)
      job_queue_processes      = 10
      background_dump_dest     = /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump
      user_dump_dest           = /va00/oracle/product/10.2.0/db_1/admin/mytest/udump
      core_dump_dest           = /va00/oracle/product/10.2.0/db_1/admin/mytest/cdump
      audit_file_dest          = /va00/oracle/product/10.2.0/db_1/admin/mytest/adump
      db_name                  = mytest
      open_cursors             = 300
      pga_aggregate_target     = 94371840
    PMON started with pid=2, OS id=4654
    PSP0 started with pid=3, OS id=4656
    MMAN started with pid=4, OS id=4658
    DBW0 started with pid=5, OS id=4660
    LGWR started with pid=6, OS id=4662
    CKPT started with pid=7, OS id=4664
    SMON started with pid=8, OS id=4666
    RECO started with pid=9, OS id=4668
    CJQ0 started with pid=10, OS id=4670
    MMON started with pid=11, OS id=4672
    Tue Oct 26 23:37:11 2010
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=12, OS id=4674
    Tue Oct 26 23:37:11 2010
    starting up 1 shared server(s) ...
    Tue Oct 26 23:37:11 2010
    alter database mount
    Tue Oct 26 23:37:15 2010
    Setting recovery target incarnation to 2
    Tue Oct 26 23:37:15 2010
    Successful mount of redo thread 1, with mount id 2432596903
    Tue Oct 26 23:37:15 2010
    Database mounted in Exclusive Mode
    Completed: alter database mount
    New incarnation branch detected in Backup, filename /va00/oracle/product/10.2.0/db_1/flash_recovery_area/MYTEST/autobackup/2010_10_26/some_o1_mf_s_733420244_6dghs7pn_.bkp
    Inspection of file changed rdi from 2 to 3
    Setting recovery target incarnation to 3
    Tue Oct 26 23:37:23 2010
    Setting recovery target incarnation to 3
    Tue Oct 26 23:37:23 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_system_6dcg5mfo_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:23 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_undotbs1_6dcg5mnx_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:23 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_sysaux_6dcg5mgg_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:23 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_users_6dcg5moq_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:23 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: '/va02/oracle/oradata/mytest/company_tab_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:23 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: '/va03/oracle/oradata/mytest/company_idx_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:31 2010
    WARNING: catalog online log file /tmp/rman_backups_third_set/onlinelog/o1_mf_1_6dcg8yw6_.log is not supported
    WARNING: catalog online log file /tmp/rman_backups_third_set/onlinelog/o1_mf_3_6dcg92d5_.log is not supported
    WARNING: catalog online log file /tmp/rman_backups_third_set/onlinelog/o1_mf_2_6dcg90tg_.log is not supported
    Expanded controlfile section 11 from 28 to 144 records
    Requested to grow by 116 records; added 5 blocks of records
    Tue Oct 26 23:37:46 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_system_6dcg5mfo_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:46 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_undotbs1_6dcg5mnx_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:46 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_sysaux_6dcg5mgg_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:46 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_users_6dcg5moq_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:46 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: '/va02/oracle/oradata/mytest/company_tab_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Oct 26 23:37:46 2010
    Errors in file /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc:
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: '/va03/oracle/oradata/mytest/company_idx_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3Not sure why does it says that it was unable to obtain file status .. is it because the dbf files could not be restored that's why ??
    Also here goes the content of DBW trace file
    [oracle@localhost bdump]$ cat mytest_dbw0_4660.trc
    /va00/oracle/product/10.2.0/db_1/admin/mytest/bdump/mytest_dbw0_4660.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /va00/oracle/product/10.2.0/db_1
    System name:    Linux
    Node name:      localhost.localdomain
    Release:        2.6.18-194.el5
    Version:        #1 SMP Mon Mar 29 20:06:41 EDT 2010
    Machine:        i686
    Instance name: mytest
    Redo thread mounted by this instance: 1
    Oracle process number: 5
    Unix process pid: 4660, image: [email protected] (DBW0)
    *** 2010-10-26 23:37:23.741
    *** SERVICE NAME:() 2010-10-26 23:37:23.740
    *** SESSION ID:(167.1) 2010-10-26 23:37:23.740
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_system_6dcg5mfo_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_undotbs1_6dcg5mnx_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_sysaux_6dcg5mgg_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_users_6dcg5moq_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: '/va02/oracle/oradata/mytest/company_tab_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: '/va03/oracle/oradata/mytest/company_idx_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_system_6dcg5mfo_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_undotbs1_6dcg5mnx_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_sysaux_6dcg5mgg_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: '/va00/oracle/product/10.2.0/db_1/oradata/MYTEST/datafile/o1_mf_users_6dcg5moq_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    *** 2010-10-26 23:37:46.274
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: '/va02/oracle/oradata/mytest/company_tab_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: '/va03/oracle/oradata/mytest/company_idx_01.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3

  • Restore spfile from rman backup ---- error.

    Hi,
    I am trying to execute recovery on new machine ...
    I have done the following steps..
    I have one database as ora10g2 as peroduction database on one machine as hosta
    I have created a catalog on another machine cora10g2 (hostb)
    I have taken a full backup from hosta as per following ...
    the following command execute from hosta machine.
    $ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
    Backup completed ...
    Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
    I have done the following setting ...on host b
    set oracle_sid=DUP
    and execute following command ...
    rman target / catalog rman/rman@cora10g2
    RMAN> set dbid 2760732370
    executing command: SET DBID
    database name is "BAAN10G2" and DBID is 2760732370
    RMAN>
    RMAN>
    RMAN> startup force nomount ;
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area 159383552 bytes
    Fixed Size 1977112 bytes
    Variable Size 67114216 bytes
    Database Buffers 83886080 bytes
    Redo Buffers 6406144 bytes
    RMAN>
    RMAN>
    RMAN>
    RMAN> show all ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    RMAN>
    RMAN>
    RMAN> list backup of spfile ;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2420 Full 7.33M DISK 00:00:01 14-JUN-07
    BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
    SPFILE Included: Modification time: 14-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2509 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2694 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2760 Full 80.00K DISK 00:00:01 15-JUN-07
    BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
    Piece Name: /rman/spfile/spfile.ora
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2769 Full 7.33M DISK 00:00:02 15-JUN-07
    BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
    SPFILE Included: Modification time: 15-JUN-07
    RMAN>
    RMAN>
    RMAN> restore spfile from autobackup ;
    Starting restore at 19-JUN-07
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=36 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=35 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=34 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=33 devtype=DISK
    channel ORA_DISK_1: looking for autobackup on day: 20070619
    channel ORA_DISK_1: looking for autobackup on day: 20070618
    channel ORA_DISK_1: looking for autobackup on day: 20070617
    channel ORA_DISK_1: looking for autobackup on day: 20070616
    channel ORA_DISK_1: looking for autobackup on day: 20070615
    channel ORA_DISK_1: looking for autobackup on day: 20070614
    channel ORA_DISK_1: looking for autobackup on day: 20070613
    channel ORA_DISK_1: no autobackup in 7 days found
    channel ORA_DISK_2: looking for autobackup on day: 20070619
    channel ORA_DISK_2: looking for autobackup on day: 20070618
    channel ORA_DISK_2: looking for autobackup on day: 20070617
    channel ORA_DISK_2: looking for autobackup on day: 20070616
    channel ORA_DISK_2: looking for autobackup on day: 20070615
    channel ORA_DISK_2: looking for autobackup on day: 20070614
    channel ORA_DISK_2: looking for autobackup on day: 20070613
    channel ORA_DISK_2: no autobackup in 7 days found
    channel ORA_DISK_3: looking for autobackup on day: 20070619
    channel ORA_DISK_3: looking for autobackup on day: 20070618
    channel ORA_DISK_3: looking for autobackup on day: 20070617
    channel ORA_DISK_3: looking for autobackup on day: 20070616
    channel ORA_DISK_3: looking for autobackup on day: 20070615
    channel ORA_DISK_3: looking for autobackup on day: 20070614
    channel ORA_DISK_3: looking for autobackup on day: 20070613
    channel ORA_DISK_3: no autobackup in 7 days found
    channel ORA_DISK_4: looking for autobackup on day: 20070619
    channel ORA_DISK_4: looking for autobackup on day: 20070618
    channel ORA_DISK_4: looking for autobackup on day: 20070617
    channel ORA_DISK_4: looking for autobackup on day: 20070616
    channel ORA_DISK_4: looking for autobackup on day: 20070615
    channel ORA_DISK_4: looking for autobackup on day: 20070614
    channel ORA_DISK_4: looking for autobackup on day: 20070613
    channel ORA_DISK_4: no autobackup in 7 days found
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/19/2007 18:00:13
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    RMAN>
    I am not able to restore spfile from rman backup ;;;

    Hi,
    I would like to know few things
    1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
    2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
    Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

Maybe you are looking for

  • Constant Kernel Panics on Mavericks 10.9.5

    Hey Everyone, I really hope someone out there can help me out because these recent kernel panics I've been getting are driving me crazy because they always happen right in the middle of some important project I'm working on. Before I share the latest

  • Interactive Report Filter Problem

    Hello, I ran into a problem with an interactive report today. When the report first loads, no issue. If a filter is added, an error is returned. The error is actually generated by an assertion routine that raises and exception if a NULL value was pas

  • Unknown Error with some exception message in BAM

    Hi all I'm trying to deploy orderbooking tutorial in (SOA 10.1.3.1)of BAM guide. whereas message says A problem occured while connecting to server "localhost" using port "8888": bpel_OrderBooking_1.0.jar failed to deploy. Exception message is: javax.

  • Photoshop CS4 doesn't display anything

    I recently bought an Nvidia GTX260 graphics card hoping it would boost performance also in Photoshop. After installing the latest driver directly from the Nvidia website, I still have this problem: when I open a project, there is no error but nothing

  • Exporting from keynote to FCE

    Exporting apresentation from Keynote with H.264 compression...very good quality...finetuning in FCP and the exproted files look like crapp...tried many eports always the same...artefacts all over the place...Help please...thx