New at rman backup

Dear experts!
We always did our db backups with scripts (offline and online). Now we want to use RMAN. I have read a few tutorials over the web.
RUN
configure default device type to disk;
configure channel device type disk format = "M:\rmanbackup\%d_%s_%T";
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to 'M:\rmanbackup\%F.ctl';
configure maxsetsize to 1900M;
backup database plus archivelog;
backup archivelog all delete input;
DELETE BACKUP COMPLETED BEFORE 'SYSDATE-14' DEVICE TYPE DISK;
After two weeks the backup is obsolet. What do you think about my rman script? Are there any weak points or is it ok for first. I'll call the script once a week and do a full database export every day.
Thanks
Markus

I would recommend running the configure commands once and then removing them from you weekly script.
Might also help to configure a retention period instead of doing a delete based on a set time.
configure retention policy to recovery window of 14 days;Then add:
delete noprompt force obsolete;Depending on how many archive log locations you have, you may also want to change the archive log backup command to:
backup database plus archivelog delete all input;and remove the "backup archivelog all delete input" command.
May also help to get a text file backup of your spfile and control file (not mandatory, but you never know when it will come in handy).
Therefore, you could run all the configure commands below once:
configure default device type to disk;
configure channel device type disk format = "M:\rmanbackup\%d_%s_%T";
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to 'M:\rmanbackup\%F.ctl';
configure maxsetsize to 1900M;
configure retention policy to recovery window of 14 days;Then change your RUN command to:
RUN
backup database plus archivelog delete all input;
sql "alter database backup controlfile to trace as ''M:\rmanbackup\controlORCL9.txt''";
sql "create pfile=''M:\rmanbackup\initORCL9.ora'' from spfile";
delete noprompt force obsolete;
}You could run this and see if this works for you.

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.

  • Create a new Database in an other server using a copie of RMAN backup

    Hi all,
    I want to create an other instance for our production database. We have disk and tape in rman backup. My question is can i create a new database using our disk backup in an other server?
    If some procedure or steps is there, email it to my adresse [email protected]
    Hamid.
    Thanks

    By means of the use of Recovery Manager it is possible to duplicate a database out from a previously taken rman backup. The method will be outlined in the next few lines.
    Let's assume a source database named SRCDB and the target database, named GEMINI. A unix like environment is assumed, but it can be implemented on windows as well, just beware of the particular Oracle implementation on a windows platform (orapwd file name, service creation, path format)
    1. Create a password file for the Cloned (GEMINI) instance:
    orapwd file=/u01/app/oracle/product/9.2.0.1.0/dbs/orapwGEMINI password=password entries=10
    2. Configure tnsnames.ora and listner.ora
    Properly identify the database at the tnsnames.ora and have the instance manually registered against the listener.ora files, both files located at the $ORACLE_HOME/network/admin directory.
    2.a Manually register the database against the listener (listener.ora)
    (SID_DESC =
    (ORACLE_HOME = /u01/app/oracle/product/9.2.0.1.0)
    (SID_NAME = GEMINI)
    2.b Added the target GEMINI to the tnsnames.ora
    GEMINI =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1521))
    (CONNECT_DATA =
    (ORACLE_SID = GEMINI)
    2.c Reload the listener
    lsnrctl reload
    3. Create a new init.ora for the cloned database.
    Next create an init.ora file for the cloned database. In case the same paths cannot be used on the target host, either because it is the same source host or because those paths are not reproducible on the target, then DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT may be required to be defined
    DB_NAME=GEMINI
    CONTROL_FILES=(/u02/oradata/GEMINI/control01.ctl,
    /u02/oradata/GEMINI/control02.ctl,
    /u02/oradata/GEMINI/control03.ctl)
    # Convert file names to allow for different directory structure.
    DB_FILE_NAME_CONVERT=(/u02/oradata/SRCDB/,/u02/oradata/GEMINI/)
    LOG_FILE_NAME_CONVERT=(/u01/oradata/SRCDB/,/u01/oradata/GEMINI/)
    # block_size and compatible parameters must match those of the source database
    DB_BLOCK_SIZE=8192
    COMPATIBLE=9.2.0.0.0
    4. Connect to the cloned instance
    ORACLE_SID=GEMINI; export ORACLE_SID
    sqlplus /nolog
    conn / as sysdba
    5. Create an SPFILE based on the init.ora
    CREATE SPFILE FROM PFILE='/u01/app/oracle/admin/GEMINI/pfile/init.ora';
    6. Start the database in NOMOUNT mode:
    STARTUP FORCE NOMOUNT;
    7. Connect to the TARGET, CATALOG and AUXILIARY databases.
    By means of the rman three connections are open, one for the Source Database (SOURCEDB), another for the Catalog database (RCAT), and one more for the cloned database (GEMINI)
    ORACLE_SID=GEMINI; export ORACLE_SID
    rman TARGET sys/password@SRCDB CATALOG rman/rman@RCAT AUXILIARY /
    8. Complete or Incomplete clone (recover)
    From the rman the database using one of the following commands:
    8.a Clone the database by means of a complete recover.
    DUPLICATE TARGET DATABASE TO GEMINI;
    8.b Clone the database up to a defined point in time in the past by means of an incomplete recover
    DUPLICATE TARGET DATABASE TO GEMINI UNTIL TIME 'SYSDATE-2';
    9. Process finished.
    Once the process is finished, the newly created GEMINI database is ready to be used as an independent new cloned database.
    Ref. RMAN Clone a Database
    ~ Madrid

  • Creating a new controlfile with datafiles in RMAN backup

    Hi,
    i am using oracle 10g (10.2.0.1) in RHEL5 server. i am trying to restore a RMAN backup from one server to another new server with new db name. i have taken out the spfile from RMAN autobackup and created pfile from it and edited the pfile with new dbname and directory structure and started the db in nomount with the new pfile. Now i have restored the controfile from the RMAN autobackup tried to put the database in mount state. But it failed due to the below error
    RMAN-03002: failure of alter db command at 11/05/2012 21:44:56
    ORA-01103: database name 'ORADB' in control file is not 'DEVDB'
    Hence i shutdown the database and started the db in nomount with new pfile and tried to create the controlfile with the new db name,but it failed as it is looking for the datafiles.
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01565: error in identifying file
    '/u01/app/oracle/oradata/DEVDB/datafile/o1_mf_system_80jq0kfw_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    All my datafiles reside in my RMAN backup. How to get the datafiles from RMAN backup in the above scenario??
    Regards,
    007

    Hello;
    The location and filename and DBIS will be different, but you need something like this :
    $ORACLE_HOME/bin/rman  << EOF
    CONNECT TARGET /
    STARTUP NOMOUNT;
    SET DBID 3754763357;  #DBID of PROD database
    RUN
       ALLOCATE CHANNEL c1 DEVICE TYPE disk format '/u01/oradata/backups';
       RESTORE CONTROLFILE FROM '/u01/oradata/backups/sb_t790762003_s85_p1';
       ALTER DATABASE MOUNT;
       SET NEWNAME FOR DATAFILE 1 TO '/u01/app/oracle/oradata/CLONE/system01.dbf';
        SET NEWNAME FOR TEMPFILE 1 TO '/u01/app/oracle/oradata/CLONE/temp01.dbf';
       RESTORE DATABASE;
       SWITCH DATAFILE ALL;
       RECOVER DATABASE;
       release channel c1;
    ALTER DATABASE OPEN RESETLOGS; So you need "SET NEWNAME" for all your files
    Full Example
    http://www.visi.com/~mseberg/rman/restore_database_without_catalog.html
    Best Regards
    mseberg

  • Setting up new dbname/sid while creating oracle db from rman backups in 11g

    Hi all,
    I have rman backups and need to create another database from rman backups with different name... but it is unsuccessful..
    created instance with new db...
    running create new db connecting rman auxiliary sys/password@newdb
    run {
    SET NEWNAME FOR DATAFILE 1 TO 'F:\app\HOME\oradata\clonedb1\SYSTEM01.DBF';
    SET NEWNAME FOR DATAFILE 2 TO 'F:\app\HOME\oradata\clonedb1\SYSAUX01.DBF';
    SET NEWNAME FOR DATAFILE 3 TO 'F:\app\HOME\oradata\clonedb1\UNDOTBS01.DBF';
    SET NEWNAME FOR DATAFILE 4 TO 'F:\app\HOME\oradata\clonedb1\USERS01.DBF';
    SET NEWNAME FOR DATAFILE 5 TO 'F:\app\HOME\oradata\clonedb1\EXAMPLE01.DBF';
    SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';
    DUPLICATE DATABASE TO clonedb
    pfile 'D:\TESTDELETE\initclonedb1.ora'
    BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'
    LOGFILE GROUP 1 ('F:\APP\HOME\ORADATA\ORCL\REDO01.LOG') SIZE 60M REUSE,
    GROUP 2 ('F:\APP\HOME\ORADATA\ORCL\REDO02.LOG.rdo') SIZE 60M REUSE,
    GROUP 3 ('F:\APP\HOME\ORADATA\ORCL\REDO03.LOG') SIZE 60M REUSE;
    Error it shown is in rman backup creation is as follows
    <part>>
    sql statement: alter system set db_name = ''ORCL'' comment= ''Modified by RMAN
    duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area 640286720 bytes
    Fixed Size 1376492 bytes
    Variable Size 314576660 bytes
    Database Buffers 318767104 bytes
    Redo Buffers 5566464 bytes
    Starting restore at 20-DEC-11
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=133 device type=DISK
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
    output file name=F:\APP\HOME\ORADATA\CLONEDB1\CONTROL01.CTL
    output file name=F:\APP\HOME\FLASH_RECOVERY_AREA\CLONEDB1\CONTROL02.CTL
    Finished restore at 20-DEC-11
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/20/2011 07:07:11
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01102: cannot mount databa
    se in EXCLUSIVE mode
    RMAN> EXIT
    how can i prevent rman setting db_name=orcl which is already exists in the db.. i need to create db from rman backups with different dbname...
    whould someone help me out, how can i create database from another database rman backups with different dbname/sid on same host..
    My pfile has new db_name , but while db creation rman setting to db_name to source dbname.. it should be new db name that i want create with new db name...
    is there any RMAN command to specify new DB name it should set while running
    sql statement: alter system set db_name = newdbname -- as part rman script execution...
    it appears to be i should not touch the soruce db.. i have access to only source db rman backups and need to create another db with different dbname/sid.. please do help...

    When you performing RMAN duplicate why you making your script so complicated?
    Your instance name and DB name can be different, But what is the contents in your pfile "D:\TESTDELETE\initclonedb1.ora" ? please do post
    Have you started any other services related to ORACLE? check in start --> run --> services.msc any other active oracles services, Make sure you have clonedb1.
    Startup in nomount
    check the connectivity to target server.
    SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';Why you mentioning SET NEWNAME FOR DATAFILE ? You have option of db_file_name_convert/log_file_name_convert in case if your file system different in Target & auxiliary.
    BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'When you have backup in same location why you are mentioning this clause?
    First run duplicate from auxiliary server as
    rman target sys/*****@prod auxiliary /
    RMAN> duplicate target database to "db_name";
    Am not sure what you are trying to do. is it 11gR1 or 11gR2?
    You have option of duplicate from active database without having backup also..
    here some links please check it.
    http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmdupdb.htm#BGBFDJHB
    RMAN 11GR2 : DUPLICATE WITHOUT CONNECTING TO TARGET DATABASE [ID 874352.1]
    knowledgespring      
         Newbie
    Handle:      knowledgespring
    Status Level:      Newbie (10)
    Registered:      Dec 26, 2007
    Total Posts:      243
    Total Questions:      77 (75 unresolved)
    So sad that forum was able to help only in two answers out of your 77 questions :(
    Edited by: CKPT on Dec 21, 2011 5:12 PM

  • Restoring Rman backup on New Host with different directory structure

    Hi,
    I have a following scenario to clone the database.
    1. clone the database on new server
    2. source is non - ASM and target is ASM
    3. On source incremental level 0 backup taken on disk connecting to catalog, the backup is moved to target host to different directory structure
    4. source is running on 32-bit Linux two node Rac and Target is running on 64-bit Linux two node Rac
    I did the following steps and getting below error:
    1. I copied incremental Level 0 backup to target server(where we need to build new db) to different directory structure
    2. On target i created pfile and build the instance, as dbf file are in multiple locations in source i put following tow parameters in init.ora of target database
    *.db_file_name_convert =(/u02/oradata/app1p/,+QADATA2/udev/datafile),(/u03/oradata/app1p/,+QADATA1/udev/datafile),(/u12/oradata/app1p/,+QADATA1/udev/datafile,),(/u99/oradata/app1p/,+QADATA1/udev/datafile),(/u09/oradata/app1p/,+QADATA1/udev/datafile),(/u14/oradata/app1p/,+QADATA1/udev/datafile),(/u07/oradata/app1p/,+QADATA1/udev/datafile),(/u06/oradata/prod/,+QADATA1/udev/datafile'),(/u05/oradata/app1p/,+QADATA1/udev/datafile)
    *.log_file_name_convert =("/u99/oradata/app1p/","+QADATA2/udev/onlinelog/")
    3. connected to rman -->> started db in nomount -->> restored the controlfile --> cataloged the backup piece and then i am trying to restore
    All the above steps i did using the Doc id *How To Restore Rman Backups On A Different Node When The Directory Structures Are Different [ID 419137.1]*
    script i am using is :
    RMAN> run {
    2> set until time "to_date('DEC/20/2010 05:30:00','Mon/DD/YYYY HH24:MI:SS')";
    3> allocate channel c1 device type disk;
    4> allocate channel c2 device type disk;
    5> allocate channel c3 device type disk;
    6> allocate channel c4 device type disk;
    7> set newname for datafile 1 to '+QADATA1/UDEV/DATAFILE';
    8> set newname for datafile 2 to '+QADATA1/UDEV/DATAFILE';
    9> set newname for datafile 3 to '+QADATA1/UDEV/DATAFILE';
    10> set newname for datafile 4 to '+QADATA1/UDEV/DATAFILE';
    11> set newname for datafile 5 to '+QADATA1/UDEV/DATAFILE';
    12> set newname for datafile 6 to '+QADATA1/UDEV/DATAFILE';
    13> set newname for datafile 54 to '+QADATA1/UDEV/DATAFILE';
    set newname for datafile 63 to '+QADATA1/UDEV/DATAFILE';
    14> 15> set newname for datafile 67 to '+QADATA1/UDEV/DATAFILE';
    16> set newname for datafile 68 to '+QADATA1/UDEV/DATAFILE';
    17> set newname for datafile 50 to '+QADATA1/UDEV/DATAFILE';
    18> set newname for datafile 39 to '+QADATA1/UDEV/DATAFILE';
    19> set newname for datafile 38 to '+QADATA1/UDEV/DATAFILE';
    20> set newname for datafile 7 to '+QADATA1/UDEV/DATAFILE';
    21> set newname for datafile 9 to '+QADATA1/UDEV/DATAFILE';
    22> set newname for datafile 8 to '+QADATA1/UDEV/DATAFILE';
    23> set newname for datafile 11 to '+QADATA1/UDEV/DATAFILE';
    24> set newname for datafile 10 to '+QADATA1/UDEV/DATAFILE';
    25> set newname for datafile 66 to '+QADATA1/UDEV/DATAFILE';
    26> set newname for datafile 48 to '+QADATA1/UDEV/DATAFILE';
    27> set newname for datafile 47 to '+QADATA1/UDEV/DATAFILE';
    28> set newname for datafile 12 to '+QADATA1/UDEV/DATAFILE';
    29> set newname for datafile 13 to '+QADATA1/UDEV/DATAFILE';
    30> set newname for datafile 14 to '+QADATA1/UDEV/DATAFILE';
    31> set newname for datafile 15 to '+QADATA1/UDEV/DATAFILE';
    32> set newname for datafile 16 to '+QADATA1/UDEV/DATAFILE';
    33> set newname for datafile 18 to '+QADATA1/UDEV/DATAFILE';
    34> set newname for datafile 17 to '+QADATA1/UDEV/DATAFILE';
    35> set newname for datafile 19 to '+QADATA1/UDEV/DATAFILE';
    36> set newname for datafile 69 to '+QADATA1/UDEV/DATAFILE';
    37> set newname for datafile 60 to '+QADATA1/UDEV/DATAFILE';
    38> set newname for datafile 59 to '+QADATA1/UDEV/DATAFILE';
    39> set newname for datafile 55 to '+QADATA1/UDEV/DATAFILE';
    40> set newname for datafile 53 to '+QADATA1/UDEV/DATAFILE';
    41> set newname for datafile 44 to '+QADATA1/UDEV/DATAFILE';
    set newname for datafile 22 to '+QADATA2/UDEV/DATAFILE';
    42> 43> set newname for datafile 21 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 20 to '+QADATA2/UDEV/DATAFILE';
    44> 45> set newname for datafile 72 to '+QADATA2/UDEV/DATAFILE';
    46> set newname for datafile 70 to '+QADATA2/UDEV/DATAFILE';
    47> set newname for datafile 65 to '+QADATA2/UDEV/DATAFILE';
    48> set newname for datafile 64 to '+QADATA2/UDEV/DATAFILE';
    49> set newname for datafile 57 to '+QADATA2/UDEV/DATAFILE';
    50> set newname for datafile 56 to '+QADATA2/UDEV/DATAFILE';
    51> set newname for datafile 49 to '+QADATA2/UDEV/DATAFILE';
    52> set newname for datafile 45 to '+QADATA2/UDEV/DATAFILE';
    53> set newname for datafile 26 to '+QADATA2/UDEV/DATAFILE';
    54> set newname for datafile 25 to '+QADATA2/UDEV/DATAFILE';
    55> set newname for datafile 24 to '+QADATA2/UDEV/DATAFILE';
    56> set newname for datafile 23 to '+QADATA2/UDEV/DATAFILE';
    57> set newname for datafile 27 to '+QADATA2/UDEV/DATAFILE';
    58> set newname for datafile 28 to '+QADATA2/UDEV/DATAFILE';
    59> set newname for datafile 29 to '+QADATA2/UDEV/DATAFILE';
    60> set newname for datafile 30 to '+QADATA2/UDEV/DATAFILE';
    61> set newname for datafile 73 to '+QADATA2/UDEV/DATAFILE';
    62> set newname for datafile 32 to '+QADATA2/UDEV/DATAFILE';
    63> set newname for datafile 31 to '+QADATA2/UDEV/DATAFILE';
    64> set newname for datafile 34 to '+QADATA2/UDEV/DATAFILE';
    65> set newname for datafile 33 to '+QADATA2/UDEV/DATAFILE';
    66> set newname for datafile 35 to '+QADATA2/UDEV/DATAFILE';
    67> set newname for datafile 36 to '+QADATA2/UDEV/DATAFILE';
    68> set newname for datafile 37 to '+QADATA2/UDEV/DATAFILE';
    69> set newname for datafile 51 to '+QADATA2/UDEV/DATAFILE';
    70> set newname for datafile 43 to '+QADATA2/UDEV/DATAFILE';
    71> set newname for datafile 40 to '+QADATA2/UDEV/DATAFILE';
    72> set newname for datafile 41 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 71 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 58 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 52 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 46 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 42 to '+QADATA2/UDEV/DATAFILE';
    73> 74> 75> 76> 77> 78> set newname for datafile 62 to '+QADATA2/UDEV/DATAFILE';
    79> set newname for datafile 61 to '+QADATA2/UDEV/DATAFILE';
    80> set newname for datafile 74 to '+QADATA2/UDEV/DATAFILE';
    81> restore database;
    82> switch datafile all;
    83> recover database;
    84> alter database open resetlogs;
    85>
    86> release channel c1;
    87> release channel c2;
    88> release channel c3;
    89> release channel c4;
    90> }
    Getting the following error, copied lines from the error i am getting.
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 27-DEC-10
    released channel: c1
    released channel: c2
    released channel: c3
    released channel: c4
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 12/27/2010 08:09:08
    RMAN-06026: some targets not found - aborting restore
    RMAN-06100: no channel to restore a backup or copy of datafile 74
    RMAN-06100: no channel to restore a backup or copy of datafile 73
    Please advice...
    Thanks,
    Tanveer Mohammed

    If you would like, please refer the link:-
    http://gavinsoorma.com/2010/04/creating-an-asm-duplicate-database-from-a-non-asm-database/

  • Create a database from 32bit rman backup with NEW name on a 64bit system

    Hello,
    i'm more programmer than database admin but i need to set up a 10gR2 apex development server based on our productive instance in a short time.
    For that i want to use a rman backup of the productive machine (SLES 10 32bit, DB10GR2+ASM, APEX 3.1).
    Because of the less time i got, i want to use an existing machine (SLES 11 64bit, DB10GR2+ASM) as destination.
    On this machine i want to create a new instance from the backup i took. I Already read note 881395.1 but i'm quite unsure about 2 things
    a) It's VERY IMPORTANT that the development instance has another name than the productive instance.
    When i follow 881395.1 and set the enviromental variable ORACLE_SID to another new name. Will this be all? Or will there be problems using another SID because of references in the controlfile or sth. like that?
    b) It's VERY IMPORTANT that the datafiles aren't stored in the same path and with the same names as the productive instance. It is another server but there is already a copy of the database (our dba tried to set up a standby solution on this machine) and i don't want to bother this!
    How can i rename the datafiles before restoring the backup from scatch?
    I found this: set newname for datafile 1 to '<filesystem based filename>';
    Will this help? Do i need to rename every single file? Or is it possible to set a path in which all datafiles will be restored?
    c) What about the 32bit to 64 bit thing? Will this work? Or do i need to convert the database? How? RMAN Convert?
    Or could RMAN convert anyhow used to realize the whole thing?
    Thank you very much for your support!
    Regards
    Daniel

    Hello,
    i'm more programmer than database admin but i need to set up a 10gR2 apex development server based on our productive instance in a short time.
    For that i want to use a rman backup of the productive machine (SLES 10 32bit, DB10GR2+ASM, APEX 3.1).
    Because of the less time i got, i want to use an existing machine (SLES 11 64bit, DB10GR2+ASM) as destination.
    On this machine i want to create a new instance from the backup i took. I Already read note 881395.1 but i'm quite unsure about 2 things
    a) It's VERY IMPORTANT that the development instance has another name than the productive instance.
    When i follow 881395.1 and set the enviromental variable ORACLE_SID to another new name. Will this be all? Or will there be problems using another SID because of references in the controlfile or sth. like that?
    b) It's VERY IMPORTANT that the datafiles aren't stored in the same path and with the same names as the productive instance. It is another server but there is already a copy of the database (our dba tried to set up a standby solution on this machine) and i don't want to bother this!
    How can i rename the datafiles before restoring the backup from scatch?
    I found this: set newname for datafile 1 to '<filesystem based filename>';
    Will this help? Do i need to rename every single file? Or is it possible to set a path in which all datafiles will be restored?
    c) What about the 32bit to 64 bit thing? Will this work? Or do i need to convert the database? How? RMAN Convert?
    Or could RMAN convert anyhow used to realize the whole thing?
    Thank you very much for your support!
    Regards
    Daniel

  • How to create new database with rman backup

    hi,
    i took a rman backup with nocatelog. can i make a new database with that rman backup.
    if yes then how ? i m using oracle 9i.
    thxs

    'NEW' doesn't seem to be the right word here, but you can DUPLICATE (clone) an existing database or restore it to a new host:
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/toc.htm
    Werner

  • Restore RMAN backup on new server

    Hi
    I took RMAN backup of a database with control file autobackup on...I copied the backup
    to a new server restored the spfile from the backup and modified the parameters
    bdump,udump,control file because the directory structure is different from the original
    machine.I restored the control file and it was restored properly.
    Now I need to restore the datafiles in the new path so I used set newname and switch
    but I get some error ....I have posted the error please look at it
    RMAN> run
    2> {
    3> set newname for datafile 1 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\SYSTEM01.DBF';
    4> set newname for datafile 2 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\UNDOTBS01.DBF';
    5> set newname for datafile 3 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\SYSAUX01.DBF';
    6> set newname for datafile 4 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\USERS01.DBF';
    7> set newname for datafile 5 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\TSDATA_01.DBF';
    8> set newname for datafile 6 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\TSIDX01.DBF';
    9> set newname for datafile 7 to
    'E:\ORACLE\METAGRID\ORADATA\METAGRID\TSDATA_AUDIT01.DBF';
    10> restore database;
    11> switch datafile all;
    12> recover database;
    13> }
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 11-NOV-10
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to E:\ORACLE\METAGRID\ORADATA\METAGRID\SYSTEM01.DBF
    restoring datafile 00002 to E:\ORACLE\METAGRID\ORADATA\METAGRID\UNDOTBS01.DBF
    restoring datafile 00005 to E:\ORACLE\METAGRID\ORADATA\METAGRID\TSDATA_01.DBF
    restoring datafile 00006 to E:\ORACLE\METAGRID\ORADATA\METAGRID\TSIDX01.DBF
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/11/2010 12:38:24
    ORA-19693: backup piece E:\RMAN\DB_0FLSLJH1_1_1 already included

    Try to clear and recatalog the backups to be used, before the restore:
    rman target /
    crosscheck backup;
    delete expired backup;
    catalog start with 'path_to_your_backup';

  • Restoring a RMAN backup to a new database instance

    Hi Mates,
    I have an issue with restoring a RMAN backup that i have with me to a new database instance. What i have with me are:
    1. Backup of SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_.BKP)
    2. Backup of Control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP)
    3. Full database backup (O1_MF_NNSNF_FULLPROD_BU_92DVGW9H_.BKP)
    I have received these files from a customer environment and I need to restore these to a new database instance in a local machine. I have given a attempt as follows (in Oracle 10g):
    1, Created a new database instance (Test75) using Oracle Database Configuration Assistant
    2. SET ORACLE_SID = Test75
    3. Connected to this instance using RMAN
    4. Tried to restore the SPFILE from the received BKP file.
    I am getting errors and cannot proceed. I am not sure whether I am executing the correct steps. Please help me out by telling me how should I achieve this.
    Thank you.

    1. Backup of SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_.BKP)
    2. Backup of Control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP)
    The first backuppiece looks like a ControlFile and the second one looks like an SPFILE'
    >I am getting errors and cannot proceed
    What is the error ?  (I assume that you tried to restore the SPFILE from O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP
    Note that you also have to SET DBID before you restore the controlfile 
    Hemant K Chitale

  • Restore an RMAN backup to a new db instance name.

    I have a old copy of an RMAN backup of a production database from 2 months ago. I want to restore it to a new instance name. The backup no longer shows in the RMAN backup listing from the control file of the current production system.
    The backup I have does have the control file as well as the other backup pieces, Is there a procedure to restore this to a new instance since the backup is no longer in the current production control file?
    I have used the duplicate command of RMAN and have successfully restored databases to a new instance name by using the newname option.
    But the backups were always in the control file.
    Can this be done? If so, how?

    You need to restore the controlfile first and copy it into all locations where init.ora specify them. then startup mount, and 'rman / target' will give you access to the old contents of the controlfile at that time.. If the rest of the back is on tape, you need to restore the rman backupset first to disk on same location specified in the backupsets paths. same for the archivelogs.
    Then you can decide to go for a duplicate database to target <newname> or a restore DB (must have the same name). but was the DB a cold backup ? then remember than Rman does not takes the redo logs, so that your shutdown before must be clean (shutdown immediate at most). If it is an hot you may need need to dump the arc and possible do a recover manual (case you forgot to put the arcchives or the archives names is not the same in the init.ora than original for you include the db name in it).
    In that case the archive logs may be renamed to what ever is in the init.ora. and there are many others possbilities. you did not specified enough data on the backup

  • Error , ORA-19809 & ORA-19804 While restoring RMAN backup .

    Hi Experts,
    I am restoring production RMAN backup to UAT . Using below steps
    1)rman target=/
    2)RMAN> startup nomount;
    3) RMAN> restore controlfile from '/orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl';
    Starting restore at 05-AUG-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=3 device type=DISK
    channel ORA_DISK_1: copied control file copy
    output file name=+DATA_ACME/acme/controlfile/current.256.724845209
    output file name=+DATA_ACME/acme/controlfile/current.257.724845209
    Finished restore at 05-AUG-10
    4) RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    5) RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME1/current/%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
    new RMAN configuration parameters are successfully stored
    6) RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    new RMAN configuration parameters are successfully stored
    released channel: ORA_DISK_1
    7) RMAN> CATALOG START WITH '/orabkdump/Rman_Bak/ACME';
    searching for all files that match the pattern /orabkdump/Rman_Bak/ACME
    List of Files Unknown to the Database
    =====================================
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
    File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
    File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
    File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
    File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
    File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
    List of Files Which Where Not Cataloged
    =======================================
    File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
    RMAN-07517: Reason: The file header is corrupted
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
    RMAN-07517: Reason: The file header is corrupted
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
    RMAN-07517: Reason: The file header is corrupted
    8) RMAN> run {
    2> set until sequence 1789 thread 2;
    3> restore database;
    4> recover database;
    5> sql 'alter database open resetlogs';
    6> }
    executing command: SET until clause
    Starting restore at 06-AUG-10
    using channel ORA_DISK_1
    Finished restore at 06-AUG-10
    Starting recover at 06-AUG-10
    using channel ORA_DISK_1
    starting media recovery
    channel ORA_DISK_1: starting archived log restore to default destination
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=2803
    channel ORA_DISK_1: restoring archived log
    archived log thread=2 sequence=6051
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=2804
    channel ORA_DISK_1: reading from backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/06/2010 23:10:38
    ORA-19870: error while restoring backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 49283072 bytes disk space from 5218762752 limit
    ** My UAT database should be in noarchival mode . Generally such errors have been observed during backup , but have no clue why they occurred during recovery .Please advice .
    Thanks
    Edited by: user11981514 on Aug 6, 2010 9:46 AM

    Hi,
    Since the error ORA-19809 indicates the lack of space in flash recovery area during the media recovery, I suggested increasing the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
    Yes, during the media recovery the RMAN will restore the archived log to the default destination (only if the required archived logs are not already on the disks).You can confirm the restore location of the archived log in RMAN restore log/destination specified by parameters log_archive_dest_1/db_recovery_file_dest.
    Regards,
    Vaibhav

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

  • Issue Creating Duplicate Database on Different host using RMAN Backup

    HI friends..
    I m trying to create a duplicate db on different host ....... 27
    i have live production db on ............. 15
    its up 24*7.
    i know how to create dup db using cold backup..but dont know how to create it using RMAN Backup..
    I have googled..but getting issues..
    Steps Taken till now
    Note- I dont have catalog created on live db..
    I already have set the tnsnames.ora on both servers
    1) Took full backup plus archivelog plus control file on 15
    2) moved it to another host..ie 27
    3) now on live db..
    I conected to rman target /
    so i m now connected to prod db
    than i try to conect to rman auxiliary sys/sys@dubpd..
    But it gives me insufficient privilages error..
    Can you tell me what to do next..Coz unless i get into mount phase on sever 27( new server)..i cannot use the control file from backup).my dupdb is up in nomount phase..but what enxt i can do..to restore the control file and than restore the backup after cataloging them to right path..
    Thanks in advance frieds...

    sai121 wrote:
    Nope ..on live db..
    @comand prompt when i type sqlplus sys/sys@dupdb..
    its says 0ra-12518...Listener cannot hand off client connection..
    My tns name for live server is..*primary* on live server .. whose ip is 15..(lIVE SERVER).
    i also have another entery with tns names- standby .on live server .. whose ip is 27..(other server for duplicated db).
    now @command prompt..@live server.. i did sqlplus sys/sys@standby
    It gives me ORA-12518
    Am i missing something..1- It could be a network problem. You may enable tracing on listener (and examine the logs).
    2- Add "DIRECT_HANDOFF_TTC_LISTENER=OFF" to listener.ora, then reload the listener
    3- You may want to increase "large_pool_size"

  • Need Advice on RMAN backup script

    Hi;
    Can any one advice if any error or guide to make RMAN backup proper :
    Backup Policy are:
    1.     0 level backup
    2.     current log file is arvhived before backing up
    3.     backup whole database (datafiles)
    4.     backup separate control file
    5.     backup is done on disk
    6.     control file auto backup ON
    7.     only 7 days archive log are need to be preserve ; old need to be deleted
    ### one time paramters seting
    RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    ### Command for weekly 0 level backup
    run {
    allocate channel c1 type disk;
    sql 'alter system archive log current';
    backup incremental level 0 tag = weekly_database format 'o:\rman\backup\full_weekly_%d_%s_%p_%t'(database);
    release channel c1;
    configure controlfile autobackup format for device type disk to 'o:\rman\backup\auto_ctrl_weekly_%f';
    allocate channel c1 type disk;
    backup tag = weekly_arch archivelog until time 'sysdate-7' format 'o:\rman\backup\archive_weekly_%d_%s_%p_%t';
    delete archivelog until time 'sysdate-7';
    release channel c1;
    Regards
    Smith

    Dear Pierre F.;
    Actually, I just added in my backup plan to have daily backup through RMAN, instead of COLD backup.
    I have planned to take cold backup once a week. here is the side of data:
    *** datafile 410
    *** size of database : 86 GM
    *** relog files size : 250MB
    *** daily archive logs are : 250MB * 4(number of files) = 1GM aprox.
    yes, time constraint is there; just because of the size of database. and we r going for 24/7
    Is this script going to run only one per week ?
    Ans: no I this was level 0 backup; i will take level 1 incremental backup with same script daily too.
    Do you have any other RMAN script ?
    ANS: no, I will modify same script for incremental.
    after local copy of backup all backup files (RMAN) will be copy over network to backup server or we can install LTO tape device to copy directly from database server.
    kindly advise me I am new in RMAN.
    regards;
    SMITH

Maybe you are looking for