RMAN procedure

Hi All,
What are the steps to do the RMAN Backup and Recovery. I am using Oracle 9i. I have only theriodical knowledge or RMAN.
Kindly explain in detail about RMAN usage....
Cheers,
Moorthy.GS

There are many different types of recovery.
At the most basic level recovery follows the following steps
1) Restore - copy the datafiles in as they existed at the time of the backup
2) Recover - recover the datafiles to a moment in time
There are many variations of the above. Partial recovery (some datafiles), point in time recovery ( some point in the past).
I'd suggest taking a look at the documentation, it's really quite good.

Similar Messages

  • How to arrange a backup set in RMAN

    I have configured the RMAN parametrs for my database. when I'm going to take the backups it gives an error called no backupset found
    screen is like this
    RMAN> BACKUP BACKUPSET ALL;
    Starting backup at 25-JUL-07
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 07/25/2007 08:41:42
    RMAN-06462: no backupsets found on device DISK that match specification
    my RMan configuration is below
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    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 'G:\backup\cf_ba
    ckup\cf%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # defa
    ult
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 3 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 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 DISK FORMAT 'G:\backup\%U';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'G:\ORACLE\PRODUCT\10.1.0\DB_2\DATABASE\S
    NCFNEW10G.ORA'; # default
    how would I create a backupset in this case
    thanks
    buddhike

    Sigh. You wouldn't be willing to spend some time in the manuals, would you?
    RMAN actually consists of 2 parts:
    - the shell, which you invoke;
    - the rman procedure, which is inside the Oracle database kernel.
    Your request is sent to the kernel, and is executed by the kernel. Therefore the kernel must be running.
    If your database is in ARCHIVELOG mode, you can do a hot backup - simply go into RMAN and tell it to backup the database.
    However, if you are in NOARCHIVELOG mode, you must ensure that nothing can change in the database files. Therefore you can not have the database in the OPEN state.
    In the NOARCHIVELOG mode, you MUST shut down the database, then re-start it using STARTUP MOUNT. Then you can get RMAN to do it's backup, after which you can then ALTER DATABASE OPEN;
    The other advantage of ARCHIVELOG mode is that the database can be restored to virtually any point in time, whereas a NOARCHIVELOG database can ONLY be restored to the backup point in time.
    However, the advantage does come at a price - disk space for the archive logs which are used to reconstruct any point in time.

  • New Oracle DBA - Need help with backup & restore procedure via RMAN

    Hello everyone,
    I've been a SQL Server DBA for 12 years now, but new to the Oracle space. My first assignment at work was to refresh our training environment with production. So with that said, I took a full backup of our production database via RMAN and backed up the Control File. I then copied both the Control File and full backup from our production environment to training. I followed the procedures listed in the URL below:
    http://www.dba-oracle.com/t_rman_clone+copy_database.htm
    I then connected to RMAN and executed a 'show all' which is as follows:
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    The CONFIGURE CONTROLFILE AUTOBACKUP was set to ON but received a message that the database needed to be mounted, so, I mounted the database and made the changes, but when I shutdown the database and performed the startup nomount again, the settings were gone. Are these settings valid only when the database is mounted? How can I successfully refresh this training environment with production data? I'm at a standstill here so any help would be very much appreciated.
    Thank you,
    Pete

    The CONFIGURE CONTROLFILE AUTOBACKUP was set to ON but received a message that the database needed to be mounted, so, I mounted the database and made the changes, but when I shutdown the database and performed the startup nomount again, the settings were gone. These settings are persistent settings.So these information retain in control files.To reading information from control files database instance must be MOUNT or OPEN stage.Due to you have mount instance and try SHOW ALL command through RMAN.
    Are these settings valid only when the database is mounted? Not only MOUNT also OPEN stage.
    How can I successfully refresh this training environment with production data? I'm at a standstill here so any help would be very much appreciated.
    There are several ways like duplication.But you take full backup from production database using BACKUP DATABASE through rman.In this case you will get also AUTOBACKUP for controlfiles/spfiles.Then copy these backup files and all available archive logs to training server and perform below steps.
    1) You have set properly ORACLE_HOME and ORACLE_SID environment variable.After that first need restore spfile as
    rman target /
    startup force nomount;
    restore spfile from 'autobackup_location';
    startup force nomount;2) Now you have to restore controlfiie as
      rman>restore controlfile from  'autobackup_location';
    rman>alter database mount;
      3) Now need catalog(it means register) all backup files and archivelogs in new restored controlfile as
       rman>catalog start with 'backuplocation';
       4) Finally you can restore and recover your database as below
       rman>restore database;
    rman>recover database;
    rman>alter database open resetlogs;
       If you want restore database to new location then before executing RESTORE DATABASE command you can use SET NEWNAME FOR DATAFILE clause.Firstly refer backup recovery guide in online documentation.

  • RMAN script in procedure

    Hi All,
    I want to hide my backup script(oracle 9iR2). For this I want to embed my script into a procedure, so that I may wrap it.
    May we put RMAN script in a PL/SQL procedure?
    Thanx

    Hi,
    Use
    RUN
    SQL ' BEGIN scott.update_log; END; ' ;
    where scott.update_log is the pl/sql procedure.
    Navneet

  • Backup procedure using RMAN for 11i Instance

    Hi,
    we have 11.5.10.2 instance
    Node 1 = Application Tier ( 11.5.10.2)
    Node 2 = DB Tier ( 9.2.0.7)
    as of now, we are taking daily cold backup of both instances.
    we want to implement RMAN online backup for DB and take cold backup every week end only.
    so, what are the best procedures for implementing RMAN for 11i Database.
    Please share your experience, if you have anybody implemented?
    which one you prefer in RMAN backup ( backupsets or copy option or backupsets with compressed option) interms of performance.. our db size is 60 GB only.
    we apply apps tier patches very rarely . so we want to take RMAN online backup for DB daily and take cold backup for entire apps and db in the week ends.

    Hi,
    This time, i am going to implement for Oracle 11i Database. thats why, i need you guys advice regarding 11i Database.Well, the same is applicable to 11i/R12 databases. You just need to configure RMAN the same way you configure it on any standalone database.
    If you have implemented any where RMAN, can you share, how you are taking RMAN backup? I can share the scripts we use for backup using RMAN. If you are interested, let me know and I shall send it by email.
    if we want to clone, are you cloning the TEST instance with RMAN backup or using cold backup.We use both, depends on the time frame of the cloning task and whether it is possible to use cold backup for cloning or not.
    Please have a look at the following notes, it should be helpful.
    Note: 230672.1 - Cloning Oracle Applications Release 11i with Rapid Clone
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=230672.1
    Note: 760772.1 - Cloning Oracle Application 11i /R12 with Rapid Clone - Database (9i/10g/11g) Using Hot Backup on Open Database
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=760772.1
    Note: 362473.1 - Cloning E-Business Suite Using Hot Backup for Minimal Downtime of Source Environment
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=362473.1
    Regards,
    Hussein

  • RMAN Copy to DEV Procedure - Opinions Needed

    Hi All,
    Wanted some opinions/advice on a problem I'm having. My goal is to have a nice easy script (that I can give to an inexperienced DBA) that copies a prod database to DEV. I've been googling around and found similar problems but noe seem to apply to me, and the procedures given seem to be missing things...The details are:
    10.2.0.4 on both sides. Prod is in archivelogmode. Backups run to tape normally but since we have no netbackup license for DEV I'm doing a special backup to disk. Backup script is:
    export ORACLE_HOME=/u01/app/oracle/product/10.2
    export PATH=$ORACLE_HOME/bin:$PATH
    export ORACLE_SID=PLTPRD01
    rman nocatalog target=sys/prodpw@PLTPRD01 log=/home/oracle/logs/full_rman_to_disk.log <<-EOF
       configure backup optimization on;
       configure default device type to disk;
       configure device type disk parallelism 1 backup type to compressed backupset;
       configure datafile backup copies for device type disk to 1;
       configure maxsetsize to unlimited;
       run {
         allocate channel ch1 type Disk maxpiecesize = 1900M;
         allocate channel ch2 type Disk maxpiecesize = 1900M;
         allocate channel ch3 type Disk maxpiecesize = 1900M;
         allocate channel ch4 type Disk maxpiecesize = 1900M;
         allocate channel ch5 type Disk maxpiecesize = 1900M;
         allocate channel ch6 type Disk maxpiecesize = 1900M;
         backup full database noexclude
         include current controlfile
         format '/u10/PLTPRD01/backup/datafile_%s_%p.bak'
         tag 'datafile_daily';
       run {
         allocate channel ch1 type Disk maxpiecesize = 1900M;
         allocate channel ch2 type Disk maxpiecesize = 1900M;
         backup archivelog all
         format '/u10/PLTPRD01/backup/archivelog_%s_%p.bak'
         tag 'archivelog_daily';
       run {
          allocate channel ch1 type Disk maxpiecesize = 1900M;
          backup format '/u10/PLTPRD01/backup/controlfile_%s.bak' current controlfile;
       quit
    EOFThat gives me the following files:
    -rwxrwSrwt  1 oracle dba  494244352 Dec  6 01:43 archivelog_6007_1.bak
    -rwxrwSrwt  1 oracle dba  373885952 Dec  6 01:42 archivelog_6008_1.bak
    -rwxrwSrwt  1 oracle dba    2048000 Dec  6 01:43 controlfile_6010.bak
    -rwxrwSrwt  1 oracle dba 1990311936 Dec  6 00:54 datafile_5999_1.bak
    -rwxrwSrwt  1 oracle dba 1990213632 Dec  6 01:15 datafile_5999_2.bak
    -rwxrwSrwt  1 oracle dba 1990303744 Dec  6 01:35 datafile_5999_3.bak
    -rwxrwSrwt  1 oracle dba  388759552 Dec  6 01:39 datafile_5999_4.bak
    -rwxrwSrwt  1 oracle dba 1990254592 Dec  6 00:51 datafile_6000_1.bak
    -rwxrwSrwt  1 oracle dba 1990287360 Dec  6 01:12 datafile_6000_2.bak
    -rwxrwSrwt  1 oracle dba 1990328320 Dec  6 01:33 datafile_6000_3.bak
    -rwxrwSrwt  1 oracle dba  567746560 Dec  6 01:38 datafile_6000_4.bak
    -rwxrwSrwt  1 oracle dba 1990213632 Dec  6 00:52 datafile_6001_1.bak
    -rwxrwSrwt  1 oracle dba 1990221824 Dec  6 01:13 datafile_6001_2.bak
    -rwxrwSrwt  1 oracle dba 1990336512 Dec  6 01:36 datafile_6001_3.bak
    -rwxrwSrwt  1 oracle dba   60645376 Dec  6 01:37 datafile_6001_4.bak
    -rwxrwSrwt  1 oracle dba 1990230016 Dec  6 00:52 datafile_6002_1.bak
    -rwxrwSrwt  1 oracle dba 1990344704 Dec  6 01:12 datafile_6002_2.bak
    -rwxrwSrwt  1 oracle dba 1990311936 Dec  6 01:32 datafile_6002_3.bak
    -rwxrwSrwt  1 oracle dba  233996288 Dec  6 01:34 datafile_6002_4.bak
    -rwxrwSrwt  1 oracle dba 1371709440 Dec  6 00:45 datafile_6003_1.bak
    -rwxrwSrwt  1 oracle dba 1990361088 Dec  6 00:50 datafile_6004_1.bak
    -rwxrwSrwt  1 oracle dba 1990230016 Dec  6 01:11 datafile_6004_2.bak
    -rwxrwSrwt  1 oracle dba 1990230016 Dec  6 01:31 datafile_6004_3.bak
    -rwxrwSrwt  1 oracle dba  713326592 Dec  6 01:38 datafile_6004_4.bak
    -rwxrwSrwt  1 oracle dba    2048000 Dec  6 00:45 datafile_6005_1.bakSo, I move over to the target server and database (UAT in this case) and run a restore using those files. But, it won't restore the archlog files and gives the old "RMAN-06102: no channel to restore a backup or copy of log thread" error. I can recover by copying over the relevant archlogs and doing a "recover using backup controlfile until cancel", but I wondered why the restore didn't recover automatically for me? The restore is as follows:
    rman nocatalog target sys/prodpw@PLTPRD01 AUXILIARY sys/UATpw@UAT cmdfile='/home/oracle/scripts/oracle/duplicate_database.rman' log=/home/oracle/logs/UAT_restore_201112080930.log(script is)
    RUN
      ALLOCATE AUXILIARY CHANNEL aux1 TYPE DISK FORMAT '/u10/PLTPRD01/backup/datafile_%s_%p.bak';
      ALLOCATE AUXILIARY CHANNEL aux2 TYPE DISK FORMAT '/u10/PLTPRD01/backup/datafile_%s_%p.bak';
      ALLOCATE AUXILIARY CHANNEL aux3 TYPE DISK FORMAT '/u10/PLTPRD01/backup/datafile_%s_%p.bak';
      ALLOCATE AUXILIARY CHANNEL aux4 TYPE DISK FORMAT '/u10/PLTPRD01/backup/datafile_%s_%p.bak';
      ALLOCATE AUXILIARY CHANNEL aux5 TYPE DISK FORMAT '/u10/PLTPRD01/backup/datafile_%s_%p.bak';
      ALLOCATE AUXILIARY CHANNEL aux6 TYPE DISK FORMAT '/u10/PLTPRD01/backup/datafile_%s_%p.bak';
      ALLOCATE AUXILIARY CHANNEL aux7 TYPE DISK FORMAT '/u10/PLTPRD01/backup/archivelog_%s_%p.bak';
      SET NEWNAME FOR DATAFILE  1 TO '/u07/oradata/UAT/system01.dbf';
      SET NEWNAME FOR DATAFILE  2 TO '/u07/oradata/UAT/undotbs01.dbf';
      SET NEWNAME FOR DATAFILE  3 TO '/u07/oradata/UAT/sysaux01.dbf';
      SET NEWNAME FOR DATAFILE  4 TO '/u07/oradata/UAT/users01.dbf';
      SET NEWNAME FOR DATAFILE  5 TO '/u07/oradata/UAT/bidata_index.dbf';
      SET NEWNAME FOR DATAFILE  6 TO '/u07/oradata/UAT/bistage_constraint.dbf';
      SET NEWNAME FOR DATAFILE  7 TO '/u07/oradata/UAT/bistage_data.dbf';
      SET NEWNAME FOR DATAFILE  8 TO '/u07/oradata/UAT/bistage_index.dbf';
      SET NEWNAME FOR DATAFILE  9 TO '/u07/oradata/UAT/bss_constraint.dbf';
      SET NEWNAME FOR DATAFILE 10 TO '/u07/oradata/UAT/bss_data.dbf';
      SET NEWNAME FOR DATAFILE 11 TO '/u07/oradata/UAT/bss_index.dbf';
      SET NEWNAME FOR DATAFILE 12 TO '/u07/oradata/UAT/bussrules_constraint.dbf';
      SET NEWNAME FOR DATAFILE 13 TO '/u07/oradata/UAT/bussrules_data.dbf';
      SET NEWNAME FOR DATAFILE 14 TO '/u07/oradata/UAT/bussrules_index.dbf';
    (plus lots more lines of datafile mappings)
      SET NEWNAME FOR TEMPFILE 1 TO '/u07/oradata/UAT/temp01.dbf';
      SET NEWNAME FOR TEMPFILE 2 TO '/u07/oradata/UAT/temp02.dbf';
      DUPLICATE TARGET DATABASE TO UAT
      PFILE='/u01/app/oracle/product/10.2/dbs/initUAT.ora'
      NOFILENAMECHECK
      LOGFILE GROUP 1 ('/u03/redo/oradata/UAT/redo1a.dbf',
                       '/u04/redo/oradata/UAT/redo1b.dbf') SIZE 500M REUSE,
              GROUP 2 ('/u03/redo/oradata/UAT/redo2a.dbf',
                       '/u04/redo/oradata/UAT/redo2b.dbf') SIZE 500M REUSE,
              GROUP 3 ('/u03/redo/oradata/UAT/redo3a.dbf',
                       '/u04/redo/oradata/UAT/redo3b.dbf') SIZE 500M REUSE,
              GROUP 4 ('/u03/redo/oradata/UAT/redo4a.dbf',
                       '/u04/redo/oradata/UAT/redo4b.dbf') SIZE 500M REUSE,
              GROUP 5 ('/u03/redo/oradata/UAT/redo5a.dbf',
                       '/u04/redo/oradata/UAT/redo5b.dbf') SIZE 500M REUSE,
              GROUP 6 ('/u03/redo/oradata/UAT/redo6a.dbf',
                       '/u04/redo/oradata/UAT/redo6b.dbf') SIZE 500M REUSE,
              GROUP 7 ('/u03/redo/oradata/UAT/redo7a.dbf',
                       '/u04/redo/oradata/UAT/redo7b.dbf') SIZE 500M REUSE,
              GROUP 8 ('/u03/redo/oradata/UAT/redo8a.dbf',
                       '/u04/redo/oradata/UAT/redo8b.dbf') SIZE 500M REUSE;
      RELEASE CHANNEL aux1;
      RELEASE CHANNEL aux2;
      RELEASE CHANNEL aux3;
      RELEASE CHANNEL aux4;
      RELEASE CHANNEL aux5;
      RELEASE CHANNEL aux6;
      RELEASE CHANNEL aux7;
    }I tried this with and without the aux7 for the archlogs, along with adding a "set until time", but always get the same errors. The logfile is as follows, but truncated (I can put it all in if anyone really wants it):
    allocated channel: aux1
    channel aux1: sid=155 devtype=DISK
    allocated channel: aux2
    channel aux2: sid=154 devtype=DISK
    allocated channel: aux3
    channel aux3: sid=153 devtype=DISK
    allocated channel: aux4
    channel aux4: sid=152 devtype=DISK
    allocated channel: aux5
    channel aux5: sid=151 devtype=DISK
    allocated channel: aux6
    channel aux6: sid=150 devtype=DISK
    allocated channel: aux7
    channel aux7: sid=149 devtype=DISK
    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
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    (more set newname commands)
    Starting Duplicate Db at 08-DEC-11
    contents of Memory Script:
       set until scn  2076483089;
       set newname for datafile  1 to
    "/u07/oradata/UAT/system01.dbf";
       set newname for datafile  2 to
    "/u07/oradata/UAT/undotbs01.dbf";
       set newname for datafile  3 to
    "/u07/oradata/UAT/sysaux01.dbf";
       set newname for datafile  4 to
    "/u07/oradata/UAT/users01.dbf";
       set newname for datafile  5 to
    "/u07/oradata/UAT/bidata_index.dbf";
       set newname for datafile  6 to
    "/u07/oradata/UAT/bistage_constraint.dbf";
    (more set newname output)
       set newname for datafile  60 to
    "/u07/oradata/UAT/ibmslob_data4.dbf";
       restore
       check readonly
       clone database
    executing Memory Script
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /u07/oradata/UAT/system01.dbf
    restoring datafile 00002 to /u07/oradata/UAT/undotbs01.dbf
    restoring datafile 00005 to /u07/oradata/UAT/bidata_index.dbf
    restoring datafile 00008 to /u07/oradata/UAT/bistage_index.dbf
    restoring datafile 00016 to /u07/oradata/UAT/customiz_data.dbf
    restoring datafile 00020 to /u07/oradata/UAT/galaxybe_data2.dbf
    restoring datafile 00023 to /u07/oradata/UAT/galaxydal_data.dbf
    restoring datafile 00026 to /u07/oradata/UAT/galaxy_data.dbf
    restoring datafile 00029 to /u07/oradata/UAT/ibmsarch_data.dbf
    restoring datafile 00037 to /u07/oradata/UAT/ibmstask_constraint.dbf
    channel aux1: reading from backup piece /u10/PLTPRD01/backup/datafile_6003_1.bak
    channel aux2: starting datafile backupset restore
    channel aux2: specifying datafile(s) to restore from backup set
    restoring datafile 00004 to /u07/oradata/UAT/users01.dbf
    restoring datafile 00007 to /u07/oradata/UAT/bistage_data.dbf
    restoring datafile 00015 to /u07/oradata/UAT/customiz_constraint.dbf
    restoring datafile 00022 to /u07/oradata/UAT/galaxydal_constraint.dbf
    restoring datafile 00028 to /u07/oradata/UAT/ibmsarch_constraint.dbf
    restoring datafile 00032 to /u07/oradata/UAT/ibmsaudit_index.dbf
    restoring datafile 00035 to /u07/oradata/UAT/ibmsdynm_index.dbf
    restoring datafile 00040 to /u07/oradata/UAT/mag_ctl.dbf
    restoring datafile 00043 to /u07/oradata/UAT/odyssey_constraint.dbf
    restoring datafile 00057 to /u07/oradata/UAT/ibmslob_data1.dbf
    channel aux2: reading from backup piece /u10/PLTPRD01/backup/datafile_6002_1.bak
    channel aux3: starting datafile backupset restore
    channel aux3: specifying datafile(s) to restore from backup set
    restoring datafile 00003 to /u07/oradata/UAT/sysaux01.dbf
    restoring datafile 00010 to /u07/oradata/UAT/bss_data.dbf
    restoring datafile 00011 to /u07/oradata/UAT/bss_index.dbf
    restoring datafile 00012 to /u07/oradata/UAT/bussrules_constraint.dbf
    restoring datafile 00017 to /u07/oradata/UAT/customiz_index.dbf
    restoring datafile 00024 to /u07/oradata/UAT/galaxydal_index.dbf
    restoring datafile 00030 to /u07/oradata/UAT/ibmsarch_index.dbf
    restoring datafile 00038 to /u07/oradata/UAT/ibmstask_data.dbf
    restoring datafile 00041 to /u07/oradata/UAT/mag_data.dbf
    restoring datafile 00046 to /u07/oradata/UAT/pilatdba_constraint.dbf
    channel aux3: reading from backup piece /u10/PLTPRD01/backup/datafile_6001_1.bak
    channel aux4: starting datafile backupset restore
    channel aux4: specifying datafile(s) to restore from backup set
    restoring datafile 00006 to /u07/oradata/UAT/bistage_constraint.dbf
    restoring datafile 00014 to /u07/oradata/UAT/bussrules_index.dbf
    restoring datafile 00019 to /u07/oradata/UAT/galaxybe_constraint.dbf
    restoring datafile 00021 to /u07/oradata/UAT/galaxybe_index.dbf
    restoring datafile 00027 to /u07/oradata/UAT/galaxy_index.dbf
    restoring datafile 00034 to /u07/oradata/UAT/ibmsdynm_data.dbf
    restoring datafile 00036 to /u07/oradata/UAT/ibmslob_data.dbf
    restoring datafile 00044 to /u07/oradata/UAT/odyssey_data.dbf
    restoring datafile 00045 to /u07/oradata/UAT/odyssey_index.dbf
    restoring datafile 00060 to /u07/oradata/UAT/ibmslob_data4.dbf
    channel aux4: reading from backup piece /u10/PLTPRD01/backup/datafile_6004_1.bak
    channel aux5: starting datafile backupset restore
    channel aux5: specifying datafile(s) to restore from backup set
    restoring datafile 00009 to /u07/oradata/UAT/bss_constraint.dbf
    restoring datafile 00013 to /u07/oradata/UAT/bussrules_data.dbf
    restoring datafile 00018 to /u07/oradata/UAT/dbcc_repos.dbf
    restoring datafile 00025 to /u07/oradata/UAT/galaxy_constraint.dbf
    restoring datafile 00033 to /u07/oradata/UAT/ibmsdynm_constraint.dbf
    restoring datafile 00039 to /u07/oradata/UAT/ibmstask_index.dbf
    restoring datafile 00042 to /u07/oradata/UAT/mag_index.dbf
    restoring datafile 00048 to /u07/oradata/UAT/pilatdba_index.dbf
    restoring datafile 00050 to /u07/oradata/UAT/ratings_data.dbf
    restoring datafile 00058 to /u07/oradata/UAT/ibmslob_data2.dbf
    channel aux5: reading from backup piece /u10/PLTPRD01/backup/datafile_6000_1.bak
    channel aux6: starting datafile backupset restore
    channel aux6: specifying datafile(s) to restore from backup set
    restoring datafile 00031 to /u07/oradata/UAT/ibmsaudit_data.dbf
    restoring datafile 00047 to /u07/oradata/UAT/pilatdba_data.dbf
    restoring datafile 00049 to /u07/oradata/UAT/ratings_constraint.dbf
    restoring datafile 00051 to /u07/oradata/UAT/ratings_index.dbf
    restoring datafile 00052 to /u07/oradata/UAT/tools.dbf
    restoring datafile 00053 to /u07/oradata/UAT/undotbs02.dbf
    restoring datafile 00054 to /u07/oradata/UAT/workflow_constraint.dbf
    restoring datafile 00055 to /u07/oradata/UAT/workflow_data.dbf
    restoring datafile 00056 to /u07/oradata/UAT/workflow_index.dbf
    restoring datafile 00059 to /u07/oradata/UAT/ibmslob_data3.dbf
    channel aux6: reading from backup piece /u10/PLTPRD01/backup/datafile_5999_1.bak
    channel aux4: restored backup piece 1
    piece handle=/u10/PLTPRD01/backup/datafile_6004_1.bak tag=DATAFILE_DAILY
    channel aux4: reading from backup piece /u10/PLTPRD01/backup/datafile_6004_2.bak
    channel aux2: restored backup piece 1
    piece handle=/u10/PLTPRD01/backup/datafile_6002_1.bak tag=DATAFILE_DAILY
    channel aux2: reading from backup piece /u10/PLTPRD01/backup/datafile_6002_2.bak
    channel aux3: restored backup piece 1
    piece handle=/u10/PLTPRD01/backup/datafile_6001_1.bak tag=DATAFILE_DAILY
    channel aux3: reading from backup piece /u10/PLTPRD01/backup/datafile_6001_2.bak
    channel aux5: restored backup piece 1
    piece handle=/u10/PLTPRD01/backup/datafile_6000_1.bak tag=DATAFILE_DAILY
    channel aux5: reading from backup piece /u10/PLTPRD01/backup/datafile_6000_2.bak
    channel aux6: restored backup piece 1
    piece handle=/u10/PLTPRD01/backup/datafile_5999_1.bak tag=DATAFILE_DAILY
    channel aux6: reading from backup piece /u10/PLTPRD01/backup/datafile_5999_2.bak
    channel aux1: restored backup piece 1
    piece handle=/u10/PLTPRD01/backup/datafile_6003_1.bak tag=DATAFILE_DAILY
    channel aux1: restore complete, elapsed time: 01:48:13
    channel aux4: restored backup piece 2
    piece handle=/u10/PLTPRD01/backup/datafile_6004_2.bak tag=DATAFILE_DAILY
    channel aux4: reading from backup piece /u10/PLTPRD01/backup/datafile_6004_3.bak
    channel aux3: restored backup piece 2
    piece handle=/u10/PLTPRD01/backup/datafile_6001_2.bak tag=DATAFILE_DAILY
    channel aux3: reading from backup piece /u10/PLTPRD01/backup/datafile_6001_3.bak
    channel aux5: restored backup piece 2
    piece handle=/u10/PLTPRD01/backup/datafile_6000_2.bak tag=DATAFILE_DAILY
    channel aux5: reading from backup piece /u10/PLTPRD01/backup/datafile_6000_3.bak
    channel aux6: restored backup piece 2
    piece handle=/u10/PLTPRD01/backup/datafile_5999_2.bak tag=DATAFILE_DAILY
    channel aux6: reading from backup piece /u10/PLTPRD01/backup/datafile_5999_3.bak
    channel aux2: restored backup piece 2
    piece handle=/u10/PLTPRD01/backup/datafile_6002_2.bak tag=DATAFILE_DAILY
    channel aux2: reading from backup piece /u10/PLTPRD01/backup/datafile_6002_3.bak
    channel aux4: restored backup piece 3
    piece handle=/u10/PLTPRD01/backup/datafile_6004_3.bak tag=DATAFILE_DAILY
    channel aux4: reading from backup piece /u10/PLTPRD01/backup/datafile_6004_4.bak
    channel aux5: restored backup piece 3
    piece handle=/u10/PLTPRD01/backup/datafile_6000_3.bak tag=DATAFILE_DAILY
    channel aux5: reading from backup piece /u10/PLTPRD01/backup/datafile_6000_4.bak
    channel aux4: restored backup piece 4
    piece handle=/u10/PLTPRD01/backup/datafile_6004_4.bak tag=DATAFILE_DAILY
    channel aux4: restore complete, elapsed time: 02:49:24
    channel aux2: restored backup piece 3
    piece handle=/u10/PLTPRD01/backup/datafile_6002_3.bak tag=DATAFILE_DAILY
    channel aux2: reading from backup piece /u10/PLTPRD01/backup/datafile_6002_4.bak
    channel aux3: restored backup piece 3
    piece handle=/u10/PLTPRD01/backup/datafile_6001_3.bak tag=DATAFILE_DAILY
    channel aux3: reading from backup piece /u10/PLTPRD01/backup/datafile_6001_4.bak
    channel aux6: restored backup piece 3
    piece handle=/u10/PLTPRD01/backup/datafile_5999_3.bak tag=DATAFILE_DAILY
    channel aux6: reading from backup piece /u10/PLTPRD01/backup/datafile_5999_4.bak
    channel aux3: restored backup piece 4
    piece handle=/u10/PLTPRD01/backup/datafile_6001_4.bak tag=DATAFILE_DAILY
    channel aux3: restore complete, elapsed time: 02:57:18
    channel aux2: restored backup piece 4
    piece handle=/u10/PLTPRD01/backup/datafile_6002_4.bak tag=DATAFILE_DAILY
    channel aux2: restore complete, elapsed time: 02:57:20
    channel aux5: restored backup piece 4
    piece handle=/u10/PLTPRD01/backup/datafile_6000_4.bak tag=DATAFILE_DAILY
    channel aux5: restore complete, elapsed time: 02:57:45
    channel aux6: restored backup piece 4
    piece handle=/u10/PLTPRD01/backup/datafile_5999_4.bak tag=DATAFILE_DAILY
    channel aux6: restore complete, elapsed time: 02:58:50
    Finished restore at 08-DEC-11
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "UAT" RESETLOGS ARCHIVELOG
      MAXLOGFILES     48
      MAXLOGMEMBERS      3
      MAXDATAFILES      400
      MAXINSTANCES     8
      MAXLOGHISTORY     4674
    LOGFILE
      GROUP  1 ( '/u03/redo/oradata/UAT/redo1a.dbf', '/u04/redo/oradata/UAT/redo1b.dbf' ) SIZE 500 M  REUSE,
      GROUP  2 ( '/u03/redo/oradata/UAT/redo2a.dbf', '/u04/redo/oradata/UAT/redo2b.dbf' ) SIZE 500 M  REUSE,
      GROUP  3 ( '/u03/redo/oradata/UAT/redo3a.dbf', '/u04/redo/oradata/UAT/redo3b.dbf' ) SIZE 500 M  REUSE,
      GROUP  4 ( '/u03/redo/oradata/UAT/redo4a.dbf', '/u04/redo/oradata/UAT/redo4b.dbf' ) SIZE 500 M  REUSE,
      GROUP  5 ( '/u03/redo/oradata/UAT/redo5a.dbf', '/u04/redo/oradata/UAT/redo5b.dbf' ) SIZE 500 M  REUSE,
      GROUP  6 ( '/u03/redo/oradata/UAT/redo6a.dbf', '/u04/redo/oradata/UAT/redo6b.dbf' ) SIZE 500 M  REUSE,
      GROUP  7 ( '/u03/redo/oradata/UAT/redo7a.dbf', '/u04/redo/oradata/UAT/redo7b.dbf' ) SIZE 500 M  REUSE,
      GROUP  8 ( '/u03/redo/oradata/UAT/redo8a.dbf', '/u04/redo/oradata/UAT/redo8b.dbf' ) SIZE 500 M  REUSE
    DATAFILE
      '/u07/oradata/UAT/system01.dbf'
    CHARACTER SET UTF8
    contents of Memory Script:
       switch clone datafile all;
    executing Memory Script
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=769350658 filename=/u07/oradata/UAT/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=769350658 filename=/u07/oradata/UAT/sysaux01.dbf
    datafile 4 switched to datafile copy
    (etc)
    datafile 60 switched to datafile copy
    input datafile copy recid=59 stamp=769350674 filename=/u07/oradata/UAT/ibmslob_data4.dbf
    contents of Memory Script:
       set until scn  2076483089;
       recover
       clone database
        delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 08-DEC-11
    starting media recovery
    Oracle Error:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u07/oradata/UAT/system01.dbf'
    released channel: aux1
    released channel: aux2
    released channel: aux3
    released channel: aux4
    released channel: aux5
    released channel: aux6
    released channel: aux7
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/08/2011 12:31:54
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 101913 lowscn 2076390043
    RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 101912 lowscn 2076281132
    RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 101911 lowscn 2076093182
    RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 101910 lowscn 2076023375
    RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 101909 lowscn 2075932322
    RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 101908 lowscn 2075932310
    RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 101907 lowscn 2075896928
    (more no channel errors)
    Recovery Manager complete.Thoughts? Ideas? I'm thinking the backup script is wrong somehow.

    this is also an intereting way to open your DB (or should I say test DB)
    http://practicalappsdba.wordpress.com/2008/04/01/how-to-recover-and-open-the-database-if-the-archive-log-required-for-recovery-is-missing/

  • RMAN through PL/SQL procedure

    Hi there
    I am using oracle 10g 10.2.0.3 in AIX environment
    I want to run RMAN backup from PL/SQL procedure. Is there any provision to do that.
    Please guide me .
    Regards
    hassan

    Hemant K Chitale wrote:
    DBMS_BACKUP_RESTORE is not intended to be used for Database BACKUPS and RESTORES.
    It is to be used with Oracle Support assistance if normal RMAN commands cannot be used (e.g. the backuppiece containing a controlfile backup cannot be identified).
    I do not suggest build your backup recovery strategy using DBMS_BACKUP_RESTORE.Its just learning how to restore/recover database using this package( internally how work/do RMAN session).So if you want build your backup policy of course you have to refer first documentation (backup recovery guide).

  • Backing up and restoring tablespaces with RMAN

    We have some tables that we want to backup and other tables that we don't.
    We are separating these tables by tablespaces and schema.
    SchemaA uses tablespaceA
    SchemaB uses tablespacesB
    We are also backing up
    sys
    sysaux
    undo
    tablespaces.
    Lets say we lose our tablespaces and do a restore. I am assuming that all my stored procedures can be restored no matter which schema I save them in. even if I save them in a schema that has a default tablespace that is not being backed up because the code in is in the System tablespace.
    Is my assumption correct?

    Here the key concept is Mean Time To Recover(MTTR), usually it is faster and easier to use an export backup file for this purpose, but this doesn't mean RMAN is bad :) RMAN was, is and will be the best practice for Oracle's B&R.
    Still you may assist your RMAN backup with a daily norows export backup and also maybe a file system backup depending on your environment and application's need. Backup's backup do not harm :)

  • Migrating with RMAN from 10g to 11g

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

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

  • 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

  • Move large database to other server using RMAN in less downtime

    Hi,
    We have large database around 20TB. We want to migrate (move) the database from one server to other server. We do not want to use standby option.
    1)     How can we move database using RMAN in less downtime
    2)     Other than RMAN is there any option is available to move the database to new server
    For option 1 (restore using RMAN),
    Whether below options are valid?
    If this option is valid, how to implement this?
    1)     How can we move database using RMAN in less downtime
    a)     Take the full backup from source (source db is up)
    b)     Restore the full backup in target (source db is up)
    c)     Take the incremental backup from source (source db is up)
    d)     Restore incremental backup in target (source db is up)
    e)     Do steps c and d, before taking downtime (source db is up)
    f)     Shutdown and mount the source db, and take the incremental backup (source db is down)
    g)     Restore last incremental backup and start the target database (target is up and application is accessing this new db
    database version: 10.2.0.4
    OS: SUN solaris 10
    Edited by: Rajak on Jan 18, 2012 4:56 AM

    Simple:
    I do this all the time to relocate file system files... But the principle is the same. You can do this in iterations so you do not need to do it all at once:
    Starting 8AM move less-used files and more active files in the afternoon using the following backup method.
    SCRIPT-1
    RMAN> BACKUP AS COPY
    DATAFILE 4 ####"/some/orcl/datafile/usersdbf"
    FORMAT "+USERDATA";
    Do as many files as you think you can handle during your downtime window.
    During your downtime window: stop all applications so there is no contention in the database
    SCRIPT-2
    ALTER DATABASE DATAFILE 4 offline;
    SWITCH DATAFILE 4 TO COPY;
    RECOVER DATAFILE 4;
    ALTER DATABASE DATAFILE 4 online;
    I then execute the delete of the original file at somepoint later - after we make sure everything has recovered and successfully brought back online.
    SCRIPT-3
    DELETE DATAFILECOPY "/some/orcl/datafile/usersdbf"
    For datafiles/tablespaces that are really busy, I typically copy them later in the afternoon as there are fewer archivelogs that it has to go through in order to make them consistent. The ones in the morning have more to go through, but less likelihood of there being anything to do.
    Using this method, we have moved upwards 600G at a time and the actual downtime to do the switchover is < 2hrs. YMMV. As I said, this can be done is stages to minimize overall downtime.
    If you need some documentation support see:
    http://docs.oracle.com/cd/E11882_01/server.112/e18951/asm_rman.htm#CHDBDJJG
    And before you do ANYTHING... TEST TEST TEST TEST TEST. Create a dummy tablespace on QFS and use this procedure to move it to ASM to ensure you understand how it works.
    Good luck! (hint: scripts to generate these scripts can be your friend.)

  • Standby database from RMAN backup

    I have been assigned to create a standby database from our RMAN backups in a different machine, as this is my first attempt at recovering, I am struggling a bit. I would appreciate if someone can throw any light on what dumb mistakeI am doing here. I ahve absolutely no control over the back up script which is done by my vendor, but can do anything in the reocvery portion. I did try going through the documentaiton and other help available for the last 2 days.
    Database : Oracle 10G R2
    OS : Windows Server 2003
    My backup script is
    configure channel device type disk format 'J:\RMAN\RMAN_df_%U' maxpiecesize 2048M;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup database;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup current controlfile for standby FORMAT='J:\RMAN\RMAN_sc_%U';
    For recovery of a standby database,
    I have copied the the back up pieces and the archive logs to the standby server where I have just created an instance with the same name as production db.
    set ORACLE_SID=NGINPROD
    set dbid 820336652
    STARTUP NOMOUNT
    RESTORE STANDBY CONTROLFILE FROM 'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    CATALOG BACKUPPIECE 'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_5_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_6_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_7_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2TMIUJLN_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    RESTORE DATABASE;
    Till this step I do not encounter any issues, but when i try to recover the database I am hit with the below error.
    RMAN> recover database;
    Starting recover at 16-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=253340
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/16/2011 09:31:57
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 253340 lowscn 4696173517
    ------------------------------------------------------------------------------------------------------------------------------------------------

    Here's the standard dcoumentation on the procedure :
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377
    Appendix "F Creating a Standby Database with Recovery Manager" of the "Oracle® Data Guard Concepts and Administration" guide.
    I don't see ArchiveLog backups being done by the vendor's script. How do you backup the ArchiveLogs ?
    In your post you state that you have copied the ArchiveLogs. Are they copied to the same log_archive_dest location ? RMAN needs to be "aware" of them. You can use the "CATALOG" command in RMAN to register them into the controlfile.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
    A Standby Database uses a Standby Controlfile which is created from the Primary (with the "ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'locaion';" command) and then copied over to the Standby server.
    Hemant K Chitale

  • How to restore a database from host A to host B by using RMAN

    Hi there
    I wanted to restore 1 database from machine A to machine B with the differente files systemes. I did these steps below, but I have a problem when I restore the controlfile from machine A to machine B.
    1-copy the controlfile from machine A to machine B by using OS utility.
    2-startup nomount the database on machine B.
    3-connect target and catalog RMAN.
    4-I have to restore the controlfile from last full backup of the machine A to machine B (see the procedure RMAN).
    I have the error messages like:
    RMAN> connect target /
    RMAN-06006: connected to target database: dbtest (not mounted)
    RMAN> connect catalog rman/rman@rcattest
    RMAN-06008: connected to recovery catalog database
    RMAN> run {
    2> allocate channel c1 type 'sbt_tape' ;
    3> restore controlfile ;
    4> }
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: c1
    RMAN-08500: channel c1: sid=10 devtype=SBT_TAPE
    RMAN-08526: channel c1: VERITAS NetBackup for Oracle8 - Release 3.2GA
    RMAN-03022: compiling command: restore
    RMAN-03022: compiling command: IRESTORE
    RMAN-03023: executing command: IRESTORE
    RMAN-08016: channel c1: starting datafile backupset restore
    RMAN-08502: set_count=177 set_stamp=419449530 creation_time=19-JAN-01
    RMAN-08021: channel c1: restoring controlfile
    RMAN-08505: output filename=/db/oracle/dbtest/dbtestcontrol01.ctl
    RMAN-03026: error recovery releasing channel resources
    RMAN-08031: released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: restore
    RMAN-03007: retryable error occurred during execution of command: IRESTORE
    RMAN-07004: unhandled exception during command execution on channel c1
    RMAN-10035: exception raised in RPC: ORA-19507: failed to retrieve sequential file, handle="5hcg0ilq_1_1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: sbtrestore: Backup file not found.
    RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIE
    null

    Hi there
    I'm also trying to restore a full RMAN backup to our DR site using Netbackup as MML
    My scenario is:
    We have one tape library at our PROD data center and another one at our DR site both using Netbackup as Storage manager
    I performed a full RMAN backup on 4 DLT tapes with recovery catalog at our PROD datacenter, then I removed the 4 tapes and place it in our tape lib at DR site
    I tried to import the tapes using bpimport from Netbackup which has been successful up to now
    But when I tried to restore controlfile from RMAN, I get the following error:
    connected to target database: prod (not mounted)
    connected to recovery catalog database
    RMAN> run {
    2> allocate channel c1 type 'SBT_TAPE';
    3> allocate channel c2 type 'SBT_TAPE';
    4> allocate channel c3 type 'SBT_TAPE';
    5> allocate channel c4 type 'SBT_TAPE';
    6> set until time '16-AUG-2005 15:00:00';
    7> restore controlfile;
    8> }
    allocated channel: c1
    channel c1: sid=13 devtype=SBT_TAPE
    channel c1: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
    allocated channel: c2
    channel c2: sid=12 devtype=SBT_TAPE
    channel c2: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
    allocated channel: c3
    channel c3: sid=11 devtype=SBT_TAPE
    channel c3: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
    allocated channel: c4
    channel c4: sid=9 devtype=SBT_TAPE
    channel c4: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
    executing command: SET until clause
    Starting restore at 18-AUG-2005:10:28:23
    channel c1: starting datafile backupset restore
    channel c1: restoring controlfile
    output filename=/oracle9i/dba/dbs/control01_drprod.ctl
    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 08/18/2005 10:28:25
    ORA-19507: failed to retrieve sequential file, handle="df_t566491965_s8860_p1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    Failed to process backup file <df_t566491965_s8860_p1>
    Anyone mastering this, please help !!
    thks
    BL

  • Rman Restore from host 2 host

    Dear all,
    here is my situation:
    i have an rman full backup for a database "db1" installed on a server "HOST A" and i need to restore this backup on another database "db2" also another server "HOST B" with a different directory structures.
    Further the problem is that the backup folder used to make the backup on the "host a" must be changed now, so i need to use another folder name to put the backup on the "host b" and start the restore procedure.
    so no more complex like that and i didn't find the solution even when trying to change in the controlfile.
    plz i need your help
    thx for all

    1) Create symbolic links to mirror the backup folders.
    2) Read the fine RMAN Advanced User's Guide for recovery instructions.

  • Need help with rman bkp testing

    Hello,
    I am using oracle 8.0.6.0 on windows 2000 server and in nocatalog mode.As i cannot use duplicate command in this version, I took image copies of all the datafiles,controlfile and archives. I restore whole database on test machine on daily basis to act as RND database. I have same directory structure on both machines. I use same database name for both databases. i copy all the backups from primary database to test database (same bkp location on both machines). I could restore whole database and i use resetlog option. The next day, agian i take the backup and try to restore on test machine, but i am getting errors.
    When i start rman with below commands,
    run{
    allocate channel d1 type disk;
    set until scn 34534345;
    restore database;
    recover database;
    sql 'alter database open resetlogs';
    I am getting rman error as Rman-06088: datafile copy r:\backup\ddatabase\sys1orcl.ora not found or out of sync with catalog.
    When i catalog all the file in backup directory, it gives another error when restoring. rman-06023.
    I do this process on daily basis. Pls advice as i didnt get this error before and got it only today.
    Thanks,

    Hi ateeqrahman,
    i am getting errors (datafile out of sync). Can you post the full error stack?
    1) Do i need to copy old archives (27th March or earlier) to the other server to recover full database from backup of 28th March?As Kamran suggested if you followed the same procedure (but different SCN) with the new 28 March backup you shouldn't need old archives.
    Rgds,
    Tycho

Maybe you are looking for