E-business Suite RMAN backup retention

Hi,
i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
What other parameter need to set at DB level?
Thanks

i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
What other parameter need to set at DB level?Rman backup retention policy [ID 462978.1]
Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
RMAN : Consistent Backup, Restore and Recovery using RMAN [ID 162855.1]
Backup and Recovery
http://www.oracle.com/pls/db112/portal.portal_db?selected=4&frame=#backup_and_recovery
Thanks,
Hussein

Similar Messages

  • E-business Suite RMAN cloning without connecting source

    Hi,
    I've RMAN backup with catalog and nocatalog. I want to use my nocatalog RMAN backup to clone e-business suite R12/11i Application without connecting source.
    Please advice/sugegst any doc.
    thanks

    Hi;
    What is your EBS and OS?
    Please check below notes which cover RMAN cloninig steps:
    Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1]
    Cloning Oracle Applications Release 11i with Rapid Clone [ID 230672.1]
    FAQ: Cloning Oracle Applications Release 11i http://ID 216664.1
    Also check below thread:
    Clone -with rman
    Re: backup procedure using RMAN for 11i Instance
    Hope it answer you
    Regard
    Helios

  • Considerations for keeping RMAN Backup Retention to 1 Year

    Dear All,
    We are using 2-node 10gR2 RAC on Windows Server. We use Symentec Netbackup 7.5 for backing up Oracle databases. We want to change the retention period of RMAN backups to 1 year. Other than changing the RMAN Backup recovery window to 365, what are the other considerations (other configuration change, other point etc) we should be aware of?
    Best regards,
    Riaz

    > Other than changing the RMAN Backup recovery window to 365, what are the other considerations (other configuration change, other point etc) we should be aware of?
    Use RMAN Catalog.
    How to restore your database if a storage failure occurs and all files on filesystem be lost and all rman files be at MML.
    RMAN need a catalog to request files from MML (this catalog can be a controlfile, rman catalog or both), so if you lost your controlfile without RMAN Catalog you need manually find desired files on MML and restore it one by one if these files are not cataloged in that controlfile restored, since Oracle does not catalog files stored at MML. RMAN catalog files only stored on disk.

  • Rman backup with different retention

    Hi,
    I have to write script on RMAN backup retentions and policies.
    My requirement is as below:
    Daily backup Name and retentions : db_daily_bkp_sun,db_daily_bkp_mon...with 7 days retension
    Weekly backup Name and retentions : db_wkly_bkp_01,db_wkly_bkp_02...with 4 backup retension
    Monthly backup Name and retentions : db_mnth_bkp_jan,db_mnth_bkp_feb...with 12 backups
    Yearly backup Name and retentions : db_yearly_bkp_2010,db_yearly_bkp_2011,db_yearly_bkp_2012
    All backups will be full online. We have to store backups in local disk.
    We have created backup locations on disk as below.
    Daily : /orabackup/daily
    Weekly : /orabackup/weekly
    Monthly: /orabackup/monthly
    Yearly : /orabackup/yearly
    So is it possible to take such backups in RMAN without using any third party software ? If possible then please provide me such script.
    With Regards,
    Khokhar Murtuja S
    Database Administrator

    Hi,
    RMAN will make you have only one retention.
    You can have more kind of retention using the option "keep until" in your backup command.
    It'll certainly do what you need.
    Greets,
    Loïc

  • Best practice for E-business suite 11i or R12 Application backup

    Hi,
    I'm taking RMAN backup of database. What would be "Best practice for E-business suite 11i or R12 Application backup" procedure?
    Right now I'm taking file level backup. Please suggest if any.
    Thanks

    Please review the following thread, it should be helpful.
    Reommended backup and recovery startegy for EBS
    Reommended backup and recovery startegy for EBS

  • Backup strategy for Oracle E-Business Suite

    Hi guys,
    I am administrating an EBS (E-Business Suite 11i) System with two Application servers and two database servers running in RAC mode. At the moment, the system has just been backed up at database tier by using rman. Now, I also want to backup application tier. So, here is my questions:
    - What is the most important thing which I must care when I backup the application. Because I am new at EBS so, more details and specific is, better is.
    - Is a good approach if I back up entire the current system data (include binary file, class file, misc files, forms, reports,...)
    Finally, anyone can share some experiences when do backup these systems?
    Thanks and best regards,

    Hi,
    - What is the most important thing which I must care when I backup the application. Because I am new at EBS so, more details and specific is, better is.
    - Is a good approach if I back up entire the current system data (include binary file, class file, misc files, forms, reports,...)
    Finally, anyone can share some experiences when do backup these systems?Your questions were asked and answered many times in the forum before, so please see previous threads for similar discussion.
    Regards,
    Hussein

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

  • Restoring RMAN backup from tape beyond retention policy ??

    Hello Friends,
    I just stuck in some basic finding. Need your help to resolve the questions.
    How we can use RMAN backup to restore oracle database when the RMAN backup pushed to tape already and being a OLD backup ( before retention policy date).
    Just to elaborate a more..  Say my retention policy is 3 days. I want to restore from a old backup  like 30 days old.
    So surely the requesting backup is behind retention date and has been pushed to tape.
    Please suggest.
    Thanks in advance.
    Regards
    Sinha.

    dba.arnab wrote:
    Hello Friends,
    I just stuck in some basic finding. Need your help to resolve the questions.
    How we can use RMAN backup to restore oracle database when the RMAN backup pushed to tape already and being a OLD backup ( before retention policy date).
    Just to elaborate a more..  Say my retention policy is 3 days. I want to restore from a old backup  like 30 days old.
    So surely the requesting backup is behind retention date and has been pushed to tape.
    Please suggest.
    Thanks in advance.
    Regards
    Sinha.
    Assuming the actual backup files still exist (the only thing actually deleted is the record of them in the catalog), you can make those files available and use the rman 'catalog' command to re-catalog them.

  • Backup solution for E- Business Suite

    Hi all,
    We have Oracle application and database deployed to a single server, whilst running a server on Oracle Entreprise Linx on 64 bit and running oracle R12.
    Therefore basically I see 03 root folders in my server in my Oracle folder namely,
    [oracle@test lab01]$ ll
    total 12
    drwxr-xr-x 4 oracle dba 4096 Jun 24 15:07 apps
    drwxr-xr-x 4 oracle dba 4096 Jun 24 15:07 db
    drwxr-xr-x 3 oracle dba 4096 Jun 24 15:06 instSo far as my backup solution I am planning to have:
    - RMAN backup solution for the database which is represented by the DB folder
    - OS tar command"  to copy the Oracle application which is represented by the apps* folder --> correct me if I am wrong, I am not sure...
    - I am not sure what is the function of the INST folder and what is the best way of backing it up.
    Thanks and Regards,

    Hi,
    - RMAN backup solution for the database which is represented by the DB folder Correct.
    - OS tar command"  to copy the Oracle application which is represented by the apps* folder --> correct me if I am wrong, I am not sure...Correct.
    - I am not sure what is the function of the INST folder and what is the best way of backing it up.Please refer to the "Oracle Applications Concepts" manual for details about the INST folder.
    You need to use the OS command to backup this top, just the same way you back up the application tier node files.
    Oracle Applications Concepts
    http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121oacg.pdf
    Thanks,
    Hussein

  • E Business suite 11i with Database in ASM  - Cloning

    Hi All,
    We are planning to migrate the E Business suite database to ASM and wanted to know the best cloning method to perform the cloning from Production to non production.
    Applciation - 11.5.10.2
    Database - 10.2.0.4 in ASM
    Since i dont see any specific notes in metalink on this, raised an SR with oracle and they told that oracle does not support this but we can use RMAN as few of the customers use RMAN to perform the clonine.
    Can you please advice on the best methode to perform this
    Our constraints :
    We have a constrain in performing the cloning through RMAN, for performing the duplicate database we need to have the sqlplus connection between prod and non prod. We will not be getting this setup due to security policy.
    I had referred the "Best Practices for Cloning ASM-managed Databases" white paper
    Thanks & Regards,
    Rakesh

    Hi Rakesh;
    please check:
    Clone with-Rman
    http://newappsdba.blogspot.com/2009/06/r12-cloning-from-rman-backup-using.html
    Clone R12 use RMAN backup???
    Re: rapid clone from RMAN backup
    How To Make A Copy Of An Open Database For Duplication To A Different Machine [ID 224274.1]
    Also check
    rac-EBS wiht asm
    Re: RAC for EBS R12
    Hope it helps
    Regard
    Helios

  • Oracle EBS R12 - 11.2.0.2 - Logical Standby Database & RMAN backups

    Hi all,
    I have Oracle EBusiness Suite R12 running on 11.2.0.2. Our organization used to have most of the business in North America, South America and Europe; but now we are also in Australia, China and Indonesia. Previously running large reporting batch jobs and RMAN backups at night time in USA was feasible but now that is beginning to show up as performance issue for some countries.
    I was thinking would it make sense to have a Active Data Guard logical standby database on a separate server in the same US based data center where we have our main servers and use that logical standy database for reporting and RMAN backups. I am especially concerned about RMAN backups. Would I be able to make RMAN backups from the logical standy database and somehow use those to recover our primary database if some issue happens?
    Any thoughts/suggestions?
    Thanks all,

    Active Data Guard only deals with physical standbys. If you are using a logical standby you can always open the database without using Active Data Guard option.
    http://docs.oracle.com/cd/E11882_01/server.112/e25608/rman.htm#sthref846 says that:
    >
    Backups of logical standby databases are not usable at the primary database.

  • How to Restore E-Business Suite after Server Crash?

    Hi Hussein Sawwan,
    I have a question that will be useful to other members of the community. How do I restore Oracle E-Business Suite R12 after physically loosing the server that hosts the ERP instance?
    I have 2 scenarios here:
    1-Existing cold backups of the DbTier and AppsTier are available
    I have been doing a full backup of the Apps and Inst folders once a week on an external drive.
    I have been copying the DB folder (Data + DBMS_ORACLE_HOME) after shutting down the database cleanly once a week on an external drive. Noting that, here the database is in NOARCHIVELOG mode.
    2-Existing Hot backups of the Database are available and I have a backup of the Apps and Inst folders (AppsTier)
    The database is in archivelog here. I have been doing a full hot backup of the database once a week, an Incremental backup everyday, and a full backup of the archivelogs once a week. All of this to an external drive. The Apps and Inst folders are backed up once a week to an external drive.
    Let say something bad happens and we completely loose the physical server. How can I do to restore and recover my Oracle E-Business Suite R12 to a new server?
    I know I will have to Install the same OS on the new server, but what happens after that?
    Thanks in advance,
    Clamarion.

    I believe the easiest approach would be:
    - Install the same OS on the new servers
    - Install OS pre-req software and packages for your EBS instance
    - Restore from cold backup (if the crash happened directly after this backup and you haven't lost any data)
    OR,
    - Restore from hot backup (if the crash happened after your cold backup and you have data that wasn't part of the cold backup)
    I assume that no changes to the hostname, domainname, IP Address, port numbers, directory structure, ..etc is taking place in this restore.
    Thanks,
    Hussein

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

  • E-Business Suite Database Tier cloning failure

    Hi All,
    We are cloning a new Oracle E-Business Suite test instance from the cold backup of our production. Production is single instance/archive log enabled. However, the target instance is single instance/no archive log. the DB version is 11.1.0.7
    When i am running adcfgclone.pl on the database tier, it errors out with the following.
    APPS Password : Log file located at /db1/oratrng/db/tech_st/11.1.0/appsutil/log/TRNG_oradapp/ApplyDBTier_11081226.log
    | 50% completed RC-50004: Fatal: Error occurred in ApplyDatabase:
    Control file creation failed
    ERROR while running Apply...
    Mon Nov 8 12:35:16 2010
    ERROR: Failed to execute /db1/oratrng/db/tech_st/11.1.0/appsutil/clone/bin/adclone.pl
    The logfile shows the following errors:
    ORACLE instance started.
    Total System Global Area 1069252608 bytes
    Fixed Size 2109352 bytes
    Variable Size 427823192 bytes
    Database Buffers 624951296 bytes
    Redo Buffers 14368768 bytes
    Control file created.
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/db1/oratrng/db/apps_st/data/system01.dbf'
    alter tablespace TEMP1 add tempfile '/db1/oratrng/db/apps_st/data/temp01.dbf' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    alter tablespace TEMP1 add tempfile '/db1/oratrng/db/apps_st/data/temp02.dbf' REUSE
    I tried by creating the controlfile manually too but it gave error when i tried to open the database:
    SQL> @crctl.sql
    ORACLE instance started.
    Total System Global Area 1069252608 bytes
    Fixed Size 2109352 bytes
    Variable Size 427823192 bytes
    Database Buffers 624951296 bytes
    Redo Buffers 14368768 bytes
    Control file created.
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/db1/oratrng/db/apps_st/data/system01.dbf'
    I tried to recover the above datafile.
    SQL> recover database using backup controlfile until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [kcvhvdf_1], [], [], [], [], [], [],
    I tried another cold backup(we take cold backups every night) but facing the same issue with another backup also. That's why i think its not an issue with system.dbf file being corrupt.
    when i searched metalink for ORA-600 with kcvhvdf_1, i found that it is a bug in 11.1.0.7. bug 9314439.
    the bug says:
    The problem is that when the datafiles have zero DB ID=0=0x0, the 'create controlfile set database' command is not setting the new DB ID in the datafile headers but only in the controlfile. It then causes the ORA-600 [kcvhvdf_1] to be produced in the recovery due to DB ID mismatch between datafiles (select FHDBI from x$kcvfh) and controlfile (select DBID from v$database).
    I verified the above statement and found it true.
    SQL> select FHDBI from x$kcvfh;
    FHDBI
    0
    0
    0
    0
    0
    0
    0
    0
    0
    0
    0
    select DBID from v$database;
    DBID
    551459957
    The bug states a work around:
    If using a cold backup (after a clean shutdown - NORMAL/IMMEDIATE), one workaround is to open the database right after the create controlfile (with no previous recover):
    CREATE CONTROLFILE SET DATABASE "DEV2" RESETLOGS ARCHIVELOG ...
    alter database open resetlogs;
    However, this workaround is not working for me.
    Kindly help. Its urgent.

    >
    We are cloning a new Oracle E-Business Suite test instance from the cold backup of our production...
    >
    >
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/db1/oratrng/db/apps_st/data/system01.dbf'
    >
    This to me indicates that the backup was not a cold backup.
    HTH
    Srini

  • 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