Howto: RMAN catalog backupset in different location

Hi,
How can I tell RMAN catalog that the location of backup set has changed.
For example: after my RMAN backup all my backup pieces went to C:\first_location\
directory. I am using a catalog while running backup.
Now I moved the backup pieces to D:\new_location\ directory. Say C:\first_location\ directory is no longer for some reason. How do I tell my catalog that the backup pieces about the new location D:\new_location\
Catalog, Rman, database all in 10.2 version.
thank you in advance

Thank you for your response to my question.
Can someone help me with syntax and usage of new location of backup pieces in a backup set to be reflected in my catalog. Catalog, target and rman all 10g version.
thanks in advance

Similar Messages

  • RMAN backup to 3 different locations

    Hi,
    I'm trying to backup my database to 3 different locations. If one location is unavailiable backup fails. Is there a possibility to make backup to other 2 locations when one is unavailiable? For example second location from following code is unavailiable. Here is my code:
    RUN
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/location1/%d_DB_%u_%s_%p', '/backup/location2/%d_DB_%u_%s_%p', '/backup/location3/%d_DB_%u_%s_%p';
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 3;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 3;
    BACKUP DATABASE PLUS ARCHIVELOG SKIP INACCESSIBLE;
    }

    Hello again;
    I was able to find an example of your other question :
    If you specify a nonexistent directory, RMAN displays output such as the following:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/29/2001
                14:36:04
    ORA-19504: failed to create file "/nosuchdisk/0cd2momi_1_1"
    ORA-27040: skgfrcre: create error, unable to create file
    SVR4 Error: 2: No such file or directory
    Source
    Spreading a Backup Across Multiple Disk Drives: Example
    Database Backup and Recovery Advanced User's Guide
    So it really looks like it errors, ORA-19504 appears to be the key.
    Unable to find any Oracle note regarding skip. Interesting question.
    Best Regards
    mseberg

  • RMAN Backup then moving to different location.

    Hi,
    Any help is much appreciated.
    I have a situation where I must backup a 1TB database to a different location than where the database resides using rman, there is also an rman catalog being used, the backup location is NFS mounted on the database server.
    If I backup directly to the NFS mount, it takes about 5 hours.
    If I backup locally on the server the database resides, the backup is completed in just over 1 hour.
    One option I have is to backup the database locally then immediately after wards copy the backup files to the backup location over NFS. However, when it comes to backing up the database he following day, it assumes the backup no longer exists.
    The question is :
    If I do 1 level 0 backups and 6 level 1 backups per week and each day rman finds no backup files, how will it know at what point the level 1 backup should start from ? Will the backups valid in the event of a restore ?
    In the event of a restore, if I copied over the backup files from the nfs mounted backup location to the local disk, will rman be able to identify that these are the backup files it had created and now can be used for a restore ?
    Below are 2 copies of the backup script, Level 0 and level 1 :
    rman target $TARGET_DB@$ORACLE_SID catalog $CATALOG_DB <<EOD1
    crosscheck archivelog all;
    crosscheck backup;
    resync catalog;
    run {
    CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$BACKUP_DIR/CTL_%F';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '$BACKUP_DIR/DB_L0_%d_%U';
    backup spfile;
    BACKUP INCREMENTAL LEVEL 0 DATABASE include current controlfile filesperset 4;
    EOD1
    rman target $TARGET_DB@$ORACLE_SID catalog $CATALOG_DB <<EOD1
    crosscheck archivelog all;
    crosscheck backup;
    resync catalog;
    run {
    CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$BACKUP_DIR/CTL_%F';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '$BACKUP_DIR/DB_L1_%d_%U';
    backup spfile;
    BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE include current controlfile filesperset 20;
    EOD1

    Where shall I start?
    This is yet again a post where including the four digit version number was considered irrelevant, though functionality of RMAN changes with every new release. Whether this is Oracle 9i or Oracle 10g, who can tell.
    It is at least 9i style code, with many misunderstandings on how RMAN works.
    First of all, by relocating your backup to a NFS mounted drive you make it unavailable to the catalog.
    By running crosscheck the status of the backup will go to expired, so it will not be considered anymore.
    Secondly, making a RMAN backup on a NFS device is dangerous. You don't specify an OS (also irrelevant) but I had to observe a backup to a correctly mounted NFS device (with a 32k read buffer and a 32k write buffer) couldn't be restored
    in a later stage as the backup was 'corrupt'.
    Thirdly, 'restore database' will only consider level 0 backups. This means: when the level 0 backup is no longer available, you can not restore your database, l1 backups are only used in the recover phase.
    Fourthly, there are few minor problems in the backup scripts, as when datafile 0 is being backed up the spfile and controlfile are included. Also you don't seem to autobackup the controlfile.
    All in all, my crystal ball tells me in the event of disaster, you will have no backup at all.
    Time to review this situation. Urgently!
    Sybrand Bakker
    Senior Oracle DBA

  • RMAN - Cataloging a backupset

    Hi all,
    On 9i how i can include a backupset on RMAN catalog ?
    On 10g I know that using this command bellow run ok.
    catalog start with 'D:\backup\' noprompt;
    can anybody help me?
    Wander(Brazil)

    You cannot catalog a backup set with Oracle 9i according to the documentation.

  • Backup archivelogs from different location

    DB : 10.2.0.4
    OS : HEHL5
    due to space issue i moved the archived to different location from log_archive_dest_1.
    is it possible to backup the archivelogs from different location as i moved them?
    Thanks.

    My bad , it's not a must! Please see,
    bash-3.2$ ls
    o1_mf_1_34_8jk60c7b_.arc  o1_mf_1_35_8jkz3p0l_.arc  o1_mf_1_36_8jlcqpky_.arc
    bash-3.2$ mkdir /tmp/archivelognewloc
    bash-3.2$ cp *.* /tmp/archivelognewloc
    bash-3.2$ rman target /
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 30 14:40:17 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    allconnected to target database: **** (DBID=1228973204)
    RMAN>
    RMAN> catalog start with '/tmp/archivelognewloc';
    searching for all files that match the pattern /tmp/archivelognewloc
    List of Files Unknown to the Database
    =====================================
    File Name: /tmp/archivelognewloc/o1_mf_1_36_8jlcqpky_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_35_8jkz3p0l_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_34_8jk60c7b_.arc
    Do you really want to catalog the above files (enter YES or NO)? yes
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /tmp/archivelognewloc/o1_mf_1_36_8jlcqpky_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_35_8jkz3p0l_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_34_8jk60c7b_.arc
    RMAN>
    Update : A little better demo
    SQL*Plus: Release 11.2.0.1.0 Production on Wed Jan 30 15:00:32 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, Oracle Label Security, OLAP, Data Mining
    and Real Application Testing options
    SQL> alter system switch logfile;
    System altered.
    SQL> /
    System altered.
    SQL> alter system checkpoint;
    System altered.
    SQL> alter system switch logfile;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, Oracle Label Security, OLAP, Data Mining
    and Real Application Testing options
    bash-3.2$ ls
    o1_mf_1_38_8jldnkog_.arc  o1_mf_1_40_8jlfdnph_.arc
    o1_mf_1_39_8jlfdmoq_.arc  o1_mf_1_41_8jlff2nn_.arc
    bash-3.2$ pwd
    /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
    [root@EDHDR3P0 ~]# ls /tmp/archivelognewloc/
    [root@EDHDR3P0 ~]# exit
    logout
    bash-3.2$
    bash-3.2$
    bash-3.2$ pwd
    /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
    bash-3.2$ ls
    o1_mf_1_38_8jldnkog_.arc  o1_mf_1_40_8jlfdnph_.arc
    o1_mf_1_39_8jlfdmoq_.arc  o1_mf_1_41_8jlff2nn_.arc
    bash-3.2$ ls /tmp/archivelognewloc/
    bash-3.2$ ls -l /tmp/archivelognewloc/
    total 0
    bash-3.2$ cp * /tmp/archivelognewloc/
    bash-3.2$ ls -l /tmp/archivelognewloc/
    total 3620
    -rw-r----- 1 oracle oinstall  549888 Jan 30 15:02 o1_mf_1_38_8jldnkog_.arc
    -rw-r----- 1 oracle oinstall 3117568 Jan 30 15:02 o1_mf_1_39_8jlfdmoq_.arc
    -rw-r----- 1 oracle oinstall    1024 Jan 30 15:02 o1_mf_1_40_8jlfdnph_.arc
    -rw-r----- 1 oracle oinstall   19456 Jan 30 15:02 o1_mf_1_41_8jlff2nn_.arc
    bash-3.2$ pwd
    /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
    bash-3.2$ rm -rf *
    bash-3.2$ ls
    bash-3.2$ rman target /
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 30 15:03:13 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: AMER (DBID=1228973204)
    RMAN> backup archivelog all;
    Starting backup at 30-JAN-13
    current log archived
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=151 device type=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 01/30/2013 15:03:32
    RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
    ORA-19625: error identifying file /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_38_8jldnkog_.arc
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    RMAN> catalog start with '//tmp/archivelognewloc';
    searching for all files that match the pattern //tmp/archivelognewloc
    List of Files Unknown to the Database
    =====================================
    File Name: /tmp/archivelognewloc/o1_mf_1_39_8jlfdmoq_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_41_8jlff2nn_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_40_8jlfdnph_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_38_8jldnkog_.arc
    Do you really want to catalog the above files (enter YES or NO)? yes
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /tmp/archivelognewloc/o1_mf_1_39_8jlfdmoq_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_41_8jlff2nn_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_40_8jlfdnph_.arc
    File Name: /tmp/archivelognewloc/o1_mf_1_38_8jldnkog_.arc
    RMAN> backup archivelog all;
    Starting backup at 30-JAN-13
    current log archived
    using channel ORA_DISK_1
    archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_38_8jldnkog_.arc not found or out of sync with catalog
    trying alternate file for archived log of thread 1 with sequence 38
    archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_39_8jlfdmoq_.arc not found or out of sync with catalog
    trying alternate file for archived log of thread 1 with sequence 39
    archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_40_8jlfdnph_.arc not found or out of sync with catalog
    trying alternate file for archived log of thread 1 with sequence 40
    archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_41_8jlff2nn_.arc not found or out of sync with catalog
    trying alternate file for archived log of thread 1 with sequence 41
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=38 RECID=45 STAMP=806079846
    input archived log thread=1 sequence=39 RECID=42 STAMP=806079846
    input archived log thread=1 sequence=40 RECID=44 STAMP=806079846
    input archived log thread=1 sequence=41 RECID=43 STAMP=806079846
    input archived log thread=1 sequence=42 RECID=41 STAMP=806079812
    input archived log thread=1 sequence=43 RECID=46 STAMP=806079851
    channel ORA_DISK_1: starting piece 1 at 30-JAN-13
    channel ORA_DISK_1: finished piece 1 at 30-JAN-13
    piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp tag=TAG20130130T150411 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 30-JAN-13
    RMAN> list backup of archivelog all;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    1       981.94M    DISK        00:01:15     30-JAN-13     
            BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: TAG20130130T143224
            Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp
      List of Archived Logs in backup set 1
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    5       830546     25-JAN-13 841823     25-JAN-13
      1    6       841823     25-JAN-13 866733     25-JAN-13
      1    7       866733     25-JAN-13 889743     25-JAN-13
      1    8       889743     25-JAN-13 912846     26-JAN-13
      1    9       912846     26-JAN-13 931109     26-JAN-13
      1    10      931109     26-JAN-13 952239     26-JAN-13
      1    11      952239     26-JAN-13 979268     26-JAN-13
      1    12      979268     26-JAN-13 1004465    26-JAN-13
      1    13      1004465    26-JAN-13 1021707    26-JAN-13
      1    14      1021707    26-JAN-13 1040437    27-JAN-13
      1    15      1040437    27-JAN-13 1068031    27-JAN-13
      1    16      1068031    27-JAN-13 1091450    27-JAN-13
      1    17      1091450    27-JAN-13 1114656    27-JAN-13
      1    18      1114656    27-JAN-13 1137779    27-JAN-13
      1    19      1137779    27-JAN-13 1165125    27-JAN-13
      1    20      1165125    27-JAN-13 1199499    28-JAN-13
      1    21      1199499    28-JAN-13 1228282    28-JAN-13
      1    22      1228282    28-JAN-13 1249640    28-JAN-13
      1    23      1249640    28-JAN-13 1270613    28-JAN-13
      1    24      1270613    28-JAN-13 1291570    28-JAN-13
      1    25      1291570    28-JAN-13 1312497    28-JAN-13
      1    26      1312497    28-JAN-13 1332622    28-JAN-13
      1    27      1332622    28-JAN-13 1365097    28-JAN-13
      1    28      1365097    28-JAN-13 1395297    28-JAN-13
      1    29      1395297    28-JAN-13 1407058    28-JAN-13
      1    30      1407058    28-JAN-13 1437549    29-JAN-13
      1    31      1437549    29-JAN-13 1469773    29-JAN-13
      1    32      1469773    29-JAN-13 1504608    29-JAN-13
      1    33      1504608    29-JAN-13 1522578    29-JAN-13
      1    34      1522578    29-JAN-13 1553706    30-JAN-13
      1    35      1553706    30-JAN-13 1586954    30-JAN-13
      1    36      1586954    30-JAN-13 1603625    30-JAN-13
    BS Key  Size       Device Type Elapsed Time Completion Time
    2       538.00K    DISK        00:00:01     30-JAN-13     
            BP Key: 2   Status: AVAILABLE  Compressed: NO  Tag: TAG20130130T144745
            Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp
      List of Archived Logs in backup set 2
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    38      1604067    30-JAN-13 1604680    30-JAN-13
    BS Key  Size       Device Type Elapsed Time Completion Time
    3       3.64M      DISK        00:00:00     30-JAN-13     
            BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: TAG20130130T150411
            Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp
      List of Archived Logs in backup set 3
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    38      1604067    30-JAN-13 1604680    30-JAN-13
      1    39      1604680    30-JAN-13 1606046    30-JAN-13
      1    40      1606046    30-JAN-13 1606049    30-JAN-13
      1    41      1606049    30-JAN-13 1606057    30-JAN-13
      1    42      1606057    30-JAN-13 1606303    30-JAN-13
      1    43      1606303    30-JAN-13 1606353    30-JAN-13
    RMAN> crosscheck backup of archivelog all;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp RECID=1 STAMP=806077945
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp RECID=2 STAMP=806078865
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp RECID=3 STAMP=806079851
    Crosschecked 3 objects
    RMAN> list backup of archivelog all;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    1       981.94M    DISK        00:01:15     30-JAN-13     
            BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: TAG20130130T143224
            Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp
      List of Archived Logs in backup set 1
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    5       830546     25-JAN-13 841823     25-JAN-13
      1    6       841823     25-JAN-13 866733     25-JAN-13
      1    7       866733     25-JAN-13 889743     25-JAN-13
      1    8       889743     25-JAN-13 912846     26-JAN-13
      1    9       912846     26-JAN-13 931109     26-JAN-13
      1    10      931109     26-JAN-13 952239     26-JAN-13
      1    11      952239     26-JAN-13 979268     26-JAN-13
      1    12      979268     26-JAN-13 1004465    26-JAN-13
      1    13      1004465    26-JAN-13 1021707    26-JAN-13
      1    14      1021707    26-JAN-13 1040437    27-JAN-13
      1    15      1040437    27-JAN-13 1068031    27-JAN-13
      1    16      1068031    27-JAN-13 1091450    27-JAN-13
      1    17      1091450    27-JAN-13 1114656    27-JAN-13
      1    18      1114656    27-JAN-13 1137779    27-JAN-13
      1    19      1137779    27-JAN-13 1165125    27-JAN-13
      1    20      1165125    27-JAN-13 1199499    28-JAN-13
      1    21      1199499    28-JAN-13 1228282    28-JAN-13
      1    22      1228282    28-JAN-13 1249640    28-JAN-13
      1    23      1249640    28-JAN-13 1270613    28-JAN-13
      1    24      1270613    28-JAN-13 1291570    28-JAN-13
      1    25      1291570    28-JAN-13 1312497    28-JAN-13
      1    26      1312497    28-JAN-13 1332622    28-JAN-13
      1    27      1332622    28-JAN-13 1365097    28-JAN-13
      1    28      1365097    28-JAN-13 1395297    28-JAN-13
      1    29      1395297    28-JAN-13 1407058    28-JAN-13
      1    30      1407058    28-JAN-13 1437549    29-JAN-13
      1    31      1437549    29-JAN-13 1469773    29-JAN-13
      1    32      1469773    29-JAN-13 1504608    29-JAN-13
      1    33      1504608    29-JAN-13 1522578    29-JAN-13
      1    34      1522578    29-JAN-13 1553706    30-JAN-13
      1    35      1553706    30-JAN-13 1586954    30-JAN-13
      1    36      1586954    30-JAN-13 1603625    30-JAN-13
    BS Key  Size       Device Type Elapsed Time Completion Time
    2       538.00K    DISK        00:00:01     30-JAN-13     
            BP Key: 2   Status: AVAILABLE  Compressed: NO  Tag: TAG20130130T144745
            Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp
      List of Archived Logs in backup set 2
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    38      1604067    30-JAN-13 1604680    30-JAN-13
    BS Key  Size       Device Type Elapsed Time Completion Time
    3       3.64M      DISK        00:00:00     30-JAN-13     
            BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: TAG20130130T150411
            Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp
      List of Archived Logs in backup set 3
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    38      1604067    30-JAN-13 1604680    30-JAN-13
      1    39      1604680    30-JAN-13 1606046    30-JAN-13
      1    40      1606046    30-JAN-13 1606049    30-JAN-13
      1    41      1606049    30-JAN-13 1606057    30-JAN-13
      1    42      1606057    30-JAN-13 1606303    30-JAN-13
      1    43      1606303    30-JAN-13 1606353    30-JAN-13
    RMAN> HTH
    Aman....
    Edited by: Aman.... on Jan 30, 2013 3:06 PM

  • RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법

    제품 : RMAN
    작성날짜 : 2001-05-28
    RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법
    ===============================================
    1) UNREGISTER 하고자 하는 Database를 RMAN CATALOG에서 확인한다.
    SELECT * FROM RC_DATABASE;
    2) UNREGISTER하고자 하는 DATABASE에 속한 BACKUPSET들을 모두 제거한다.
    - 제거하고자 하는 BACKUPSET을 알아내는 방법
    RMAN> list backupset of database;
    - BACKUPSET을 제거하는 방법
    RMAN> allocate channel for delete type disk;
    RMAN> change backupset XXX delete;
    * 위에서는 DISK에대해 CHANNEL을 설정하였지만 TAPE에 대해 CHANNEL설정을
    하려면 아래와 같은 COMMAND를 수행한다.
    RMAN> allocate channel for delete type 'sbt_tape';
    또한 XXX는 'list backupset of database'의 결과 중에서 'LIST OF KEY'의
    값을 의미한다.
    3) 다음과 같은 PROCEDURE를 RECOVERY CATALOG에서 수행함으로써 DATABASE를 UNREGISTER한다.
    execute dbms_rcvcat.unregisterdatabase (db_key, db_id)
    * DB_KEY와 DB_ID는 다음과 같은 QUERY문에서 알아낼 수 있다.
    SVRMGR> select * from rc_database;
    EXAMPLE:
    ========
    Unregistering ORCL database:
    1) The following will list the backupset for the database that we want to
    uncatlog.
    RMAN> list backupset of database;
    RMAN-03022: compiling command: list
    RMAN-06230: List of Datafile Backups
    RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
    RMAN-06232: ------- ---- ------------ -- --------------- ---------
    RMAN-06233: 858 1 Full 16-SEP-98 253487 16-SEP-98
    RMAN-06233: 858 2 Full 16-SEP-98 253487 16-SEP-98
    RMAN-06233: 858 3 Full 16-SEP-98 253487 16-SEP-98
    RMAN-06233: 858 4 Full 16-SEP-98 253487 16-SEP-98
    ==================================
    2) The following will show allocation of a delte channel, deleting the
    backupset, and running the list command to confirm that the backupsets were
    removed. The delete command will remove the backupsets from the backup location.
    RMAN> allocate channel for delete type disk;
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: delete
    RMAN-08500: channel delete: sid=10 devtype=DISK
    RMAN> change backupset 858 delete;
    RMAN-03022: compiling command: change
    RMAN-03023: executing command: change
    RMAN-08073: deleted backup piece
    RMAN-08517: backup piece handle=C:\ORANT\DATABASE\RMANORCLBACKUP\DF_344180532_30
    _1 recid=27 stamp=344180538
    RMAN-03023: executing command: partial resync
    RMAN-08003: starting partial resync of recovery catalog
    RMAN-08005: partial resync complete
    RMAN> list backupset of database;
    RMAN-03022: compiling command: list
    RMAN-06230: List of Datafile Backups
    RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
    RMAN-06232: ------- ---- ------------ -- --------------- ----------
    ================================
    3) From the recovery catalog:
    SVRMGR> select * from rc_database;
    DB_KEY DBINC_KEY DBID NAMERESETLOGS_ RESETLOGS
    584 585 868345165 ORCL 192881 18-AUG-98
    1 row selected.
    SVRMGR> execute dbms_rcvcat.unregisterdatabase(584,868345165);
    Statement processed.
    SVRMGR> select * from rc_database;
    DB_KEY DBINC_KEY DBID NAME RESETLOGS_ RESETLOGS
    0 rows selected.

  • Setting backup on two different location

    Hello, people. I am a newbie DBA and at my work place , Using RMAN for my backup strategy I want to set up a backup to two different location ( e.g A:\backup and B:\backup), I have configure two channels, and also set configure device type disk parallelism 2, but I seem not to be getting the result i need.
    What does configure device type disk parallelism actually do?
    For me to proceed, what do i need to do? thank you.

    Question is, do you want A:\ & B:\ backup locations to by synchronized? If so, you'll need to use the COPIES parameter (could also copy the backupset once the backup is complete). Setting the PARALLELISM alone will not synchronize the two backup locations.
    In your case, it would appear that you manually allocated multiple channels with a format specified, therefore RMAN produced the three pieces in A:\ and the one piece in B:\ .
    What you'll experience with multiple copies AND multiple channels (parrlelism 2 for example) is that one channel will grab a group of files and begins backing up to the multiple locations while channel two grabs another group of files and begins backing up to the multiple locations at the same time.
    Hope this helps.

  • What is the best way to work on the same InDesign file in different locations?

    I'm the creative director for an in-house creative department. We produce 37 catalogs and a multitude of print and electronic advertising each year, plus a variety of other items. Our problem is that we have two locations. In the current set-up, if I want someone at one location to work on a project but the files are at the other location, I have someone at the one location package all the materials involved with that project and either upload them to DropBox or copy them to an external drive and ship it. Not very efficient.
    We have servers at both locations but there are different files at each location. I'm able to remote from my computer into a computer at the other location, but if everyone were to do that we would need double the number of CC subscriptions and computers, and it would bog down the internet connection that the entire company uses. I'm also connected to the server at the other location (again, over the internet) and have opened InDesign files that reside on the server there and tried to work on them here (over the internet) but that is much slower than remoting in.
    The only way I can think of to alleviate this problem is to run duplicate servers at each location, but this would be an update and back-up nightmare (unless I'm missing something). Is anyone operating this same way and, if so, how are you dealing with it?
    We can't be the only company that works like this. Maybe I'm just missing something.
    Thanks,
    Lloyd

    We have servers at both locations but there are different files at each location. I'm able to remote from my computer into a computer at the other location, but if everyone were to do that we would need double the number of CC subscriptions and computers, and it would bog down the internet connection that the entire company uses. I'm also connected to the server at the other location (again, over the internet) and have opened InDesign files that reside on the server there and tried to work on them here (over the internet) but that is much slower than remoting in.
    One tiny thing bothers me about your setup. And you said it above, you would need double the number of CC subscriptions and computers. Are you using two people to access under the same CC subscription. Even if they are working in two different time zones, it is technically violating the rules and spirit of the rules of being able to install on two machines at the same time.
    You're allowed to install for two machines for one person working at the office and then at home. One person wouldn't be in two different locations at the same time.
    Meanwhile, regards your problem, I remember reading about a system many years ago that was pretty simple. It was based on an old newspaper/magaizine system of "who has the folder." (Created before computers) In the old days, if someone was working on a file, they left a folder with their name in its place.
    In the computer age, one person, working on a file, would move it to their desktop. Then, they would leave an empty folder with that document's name where it had been as well as their initials. So if I took "Shoes and Socks Fall 2015.indd" out, I would leave a folder named "Shoes and Socks Fall 2015_smsc" in its place.
    And if it was necessary for me to have the images, I would make a copy of them onto my machine so I wouldn't tax the network. Then when I was finished, I would copy the file back to the server. The links should show up. If not, we could relink later.
    With the empty folder on the server, anyone could tell who is working on a project. So if they were late getting it back, you could email them.
    It relies on the people being disciplined enough to make the folders, move the docs, etc. But since you've ruled out all the systems for companies with dumb employees, you're going to have to make them follow the rules.

  • Question: Which is better and why....RMAN catalog or Flashback Recovery

    Hey All,
    Newly testing and reading up on 10g. I am on information overload and would appreciate pro's advice on which to choose and why.
    Thanks,
    d.

    Different things, not necessarily alternative. That is, RMAN catalog is normally (at least should be) on another machine, and does not contain physical backups, but only information about them : physical backups are normally stored on external devices, like tapes.
    Flashback Recovery technique is based on Flashback logs in Flash Recovery Area, which is a disk area on local machine, and so cannot be unlimited.
    Therefore, Flashback Recovery is much faster than Media Recovery, since you don't need to restore anything, but you have limits in using that : your disks size.
    On the other hand, RMAN backups are safer, being physically elsewhere.
    See http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#g1023042

  • Unregistering of a database from RMAN Catalog

    Hello,
    We had set up RMAN backup though RMAN Catalog for one of our database.
    We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
    1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
    2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
    We know that the tapes don't have the backup of this database.
    Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
    Thanks!

    Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
    I have another question though -
    We have compressed backup for one of the database/
    If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
    BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
    select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
    Question - How to check the compressed size of the backupset from the Catalog tables/views?
    Thanks for your help on this!
    Thanks!
    ,

  • Schedule a crontab in rman catalog

    Hi,
    I am trying to schedule a crontab in rman catalog side but it wasn't work.
    I prepared a scripts and I dont know why it was not worked.
    Please can anyone tell me how can I schedule my crontab in rman.
    The scripts is this,
    00 01 * * 0 ksh /u01/app/oracle/product/10.2.0/bin/ora_rman.sh >/dev/null 2>&1
    vi ora_rman.sh
    ORACLE_SID=p001
    ORACLE_BASE=/orahome/p001
    ORACLE_HOME=$ORACLE_BASE/10.0.2
    PATH=$ORACLE_HOME/bin:$PATH
    $ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 /u01/app/oracle/product/10.2.0/bin/ora_rman.sh <<EOF
    run {
    backup incremental level 0 as compressed backupset database plus archivelog;
    delete noprompt archivelog all completed before 'sysdate-7';
    00 19 * * * ksh /u01/app/oracle/product/10.2.0/bin/ora01_rman.sh >/dev/null 2>&1
    vi ora01_rman.sh
    ORACLE_SID=p001
    ORACLE_BASE=/orahome/p001
    ORACLE_HOME=$ORACLE_BASE/10.0.2
    PATH=$ORACLE_HOME/bin:$PATH
    $ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 u01/app/oracle/product/10.2.0/bin/ora01_rman.sh <<EOF
    run {
    backup incremental level 1 as compressed backupset database plus archivelog;
    delete noprompt archivelog all completed before 'sysdate-7';
    waiting for your replies,
    Thanks & Regards

    Here's my working stuff:
    I use an .env file. Here's the crontab entry, script and env file.
    00 16 * * 0-6 /u01/app/oracle/dba_tool/PRIMARY/db_rman_full.sh > /tmp/PRIMARY_rmanfull.out
    #!/bin/bash
    # Name: db_rman_full.sh
    # Purpose: Database rman backup
    # Usage : db_rman_full <DBNAME>
    . /u01/app/oracle/dba_tool/env/PRIMARY.env
    echo "Starting RMAN..."
    $ORACLE_HOME/bin/rman target / catalog <catalog_user>/@<catalog_db> << EOF
    run { allocate channel d1 type disk;
    backup full as compressed backupset
    database plus archivelog;}
    crosscheck backup;
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-5';
    DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
    exit
    EOF
    echo `date`
    echo
    echo 'RMAN Full on PRIMARY Complete'
    env
    ORACLE_BASE=/u01/app/oracle
    ULIMIT=unlimited
    ORACLE_SID=PRIMARY
    ORACLE_HOME=$ORACLE_BASE/product/11.2.0
    ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
    LIBPATH=$LD_LIBRARY_PATH:/usr/lib
    TNS_ADMIN=$ORACLE_HOME/network/admin
    PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
    export TERM=vt100
    export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
    export ORACLE_HOME
    export LIBPATH LD_LIBRARY_PATH ORA_NLS33
    export TNS_ADMIN
    export PATH
    ----If you find this helpful please mark it so----

  • Setting backup on two different locations

    Hello, people. I am a newbie DBA and at my work place , Using RMAN for my backup strategy I want to set up a backup to two different location ( e.g A:\backup and B:\backup), I have configure two channels, and also set configure device type disk parallelism 2, but I seem not to be getting the result i need.
    What does configure device type disk parallelism actually do?
    For me to proceed, what do i need to do? thank you.

    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\oracle\backup\data_%U', '\\atapp\data\olu\backup\data_%U';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\ORACLE9I\DATABASE\SNCFTESTER.ORA'; # default
    this is my configuration and it works fine, A copy of the backup are on both servers, the same size the and there is only copy of the archive log and controlfile on one of the servers which is fine

  • One 8i instance and two rman catalogs 8i and 8

    Can I have a single 8i instance for RMAN only with two catalogs, one for 8i and one for 8.0?

    Robert,
    Yes you can use a single database for 2 recovery catalogs. You can create 2 different schemas for each RMAN catalog version and each of those schemas can hold a different version of the RMAN catalog.
    The only reason I can think that you would need 2 different catalogs is because you have an 8.1.X target and a 8.0.5 target? If so, make sure to have the RMAN catalog be the latest 8.1.x release.
    In general, the rules of RMAN compatibility are as follows:
    o The RMAN catalog schema version should be greater than or equal to the catalog database version. See "Note 1: 8.1 or Later Catalog Schemas in 8.0 Catalog Databases".
    o The RMAN catalog is backwards compatible with target databases from earlier releases. See "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases".
    o The versions of the RMAN executable and the target database should be the same.
    Note 1: 8.1 or Later Catalog Schemas in 8.0 Catalog Databases
    RMAN cannot create release 8.1 or later catalog schemas in 8.0 catalog databases.
    Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases
    Restore operations for an 8.0.4 or 8.0.5 target with an 8.1 or later catalog schema do not work when both these conditions are met:
    The target database is mounted or open
    You are connected to a recovery catalog
    If any of these conditions is not met, then you can use an 8.1 or later catalog schema with an 8.0.4 or 8.0.5 target database.
    Note 3: 8.1.6 Catalog Schema and Pre-8.1.6 RMAN Executable
    Using a pre-8.1.6 release of the RMAN executable with recovery catalog schema of release 8.1.6.0 or 8.1.6.1 (newly created by 8.1.6 RMAN executable using the CREATE
    CATALOG command) requires the following update at the catalog database:
    SQL> UPDATE CONFIG SET VALUE='080004' WHERE NAME='COMPATIBLE';
    null

  • Rman catalog files

    We have 11g rac one node implemented on windows 2008, i took complete backup using rman from the production database and I copied the files to the test server and when am doing
    restore database validate it is still pointing to production backup location :
    c:\rman\ (test location)
    e:rman (production location)
    Am getting the error :
    channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
    Wondering why am getting the above error as I didn't catalog any backup piece on that location and the location is taken from production.
    test worklog
    RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
    Starting restore at 26-JAN-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL01.CTL
    output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL02.CTL
    Finished restore at 26-JAN-12
    RMAN> catalog backuppiece 'C:\rman\DATA_73_1_29N1OG00_1_1.BAK';
    released channel: ORA_DISK_1
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_73_1_29N1OG00_1_1.BAK RECID=34 STAMP=773622357
    RMAN> catalog backuppiece 'C:\rman\'DATA_74_1_2AN1OG00_1_1.BAK';
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "comma, ;"
    RMAN-01008: the bad identifier was: DATA_74_1_2AN1OG00_1_1
    RMAN-01007: at line 1 column 31 file: standard input
    RMAN> catalog backuppiece 'C:\rman\DATA_74_1_2AN1OG00_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_74_1_2AN1OG00_1_1.BAK RECID=35 STAMP=773622388
    RMAN> catalog backuppiece 'C:\rman\DATA_75_1_2BN1OG00_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_75_1_2BN1OG00_1_1.BAK RECID=36 STAMP=773622401
    RMAN> catalog backuppiece 'C:\rman\DATA_76_1_2CN1OG01_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK RECID=37 STAMP=773622413
    RMAN> catalog backuppiece 'C:\rman\DATA_77_1_2DN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK RECID=38 STAMP=773622427
    RMAN> catalog backuppiece 'C:\rman\DATA_78_1_2EN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK RECID=39 STAMP=773622439
    RMAN> catalog backuppiece 'C:\rman\DATA_79_1_2FN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK RECID=40 STAMP=773622501
    RMAN> catalog backuppiece 'C:\rman\DATA_80_1_2GN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK RECID=41 STAMP=773622513
    RMAN> catalog backuppiece 'C:\rman\DATA_81_1_2HN1OG03_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK RECID=42 STAMP=773622525
    RMAN> catalog backuppiece 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_82_1_2IN1OG3N_1_1.BAK RECID=43 STAMP=773622546
    RMAN> catalog backuppiece 'C:\rman\DATA_83_1_2JN1OG3N_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_83_1_2JN1OG3N_1_1.BAK RECID=44 STAMP=773622560
    RMAN> catalog backuppiece 'C:\rman\DATA_84_1_2KN1OG75_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_84_1_2KN1OG75_1_1.BAK RECID=45 STAMP=773622574
    RMAN> restore database validate;
    Starting restore at 26-JAN-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=350 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=407 device type=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: SID=466 device type=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: SID=524 device type=DISK
    allocated channel: ORA_DISK_5
    channel ORA_DISK_5: SID=582 device type=DISK
    allocated channel: ORA_DISK_6
    channel ORA_DISK_6: SID=640 device type=DISK
    channel ORA_DISK_1: starting validation of datafile backup set
    channel ORA_DISK_2: starting validation of datafile backup set
    channel ORA_DISK_3: starting validation of datafile backup set
    channel ORA_DISK_4: starting validation of datafile backup set
    channel ORA_DISK_5: starting validation of datafile backup set
    channel ORA_DISK_6: starting validation of datafile backup set
    channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
    channel ORA_DISK_3: reading from backup piece C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK
    channel ORA_DISK_4: reading from backup piece C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK
    channel ORA_DISK_5: reading from backup piece C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK
    channel ORA_DISK_6: reading from backup piece C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK
    channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
    _1_1.BAK
    channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    tag=TAG20120126T174849
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: validation complete, elapsed time: 00:00:46
    channel ORA_DISK_2: errors found reading piece handle=E:\RMAN\DATA_81_1_2HN1OG03
    _1_1.BAK
    channel ORA_DISK_2: failover to piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
    tag=TAG20120126T174849
    channel ORA_DISK_2: restored backup piece 1
    channel ORA_DISK_2: validation complete, elapsed time: 00:00:56
    channel ORA_DISK_6: piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_6: restored backup piece 1
    channel ORA_DISK_6: validation complete, elapsed time: 00:01:26
    channel ORA_DISK_3: piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_3: restored backup piece 1
    channel ORA_DISK_3: validation complete, elapsed time: 00:01:36
    channel ORA_DISK_5: piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_5: restored backup piece 1
    channel ORA_DISK_5: validation complete, elapsed time: 00:01:36
    channel ORA_DISK_4: piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_4: restored backup piece 1
    channel ORA_DISK_4: validation complete, elapsed time: 00:02:07
    Finished restore at 26-JAN-12Kai

    Those "prod" locations are found in the backup controlfile:
    >
    RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
    >
    >
    channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
    _1_1.BAK
    channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    tag=TAG20120126T174849
    >
    You can see how RMAN noticed it couldn't find that piece and then found one that you had previously cataloged. Looks good to me.

  • RMAN Backup using Rman Catalog

    Hi
    can we take backup of oracle9i database using oracle10g RMAN Catalog?
    Thanks
    With Regards
    OH

    I guess this is related to backward compatibility support principle. Target database's controlfile and RMAN catalog is synchronized and different version may have different structure and feature. When we need to completely restore an Oracle instance from backup, RMAN catalog must be able to support target database, and it may not be possible if RMAN catalog version is lower than target database. I hope I get the message across.
    Pls anybody correct me if I am wrong

Maybe you are looking for

  • Data Transfer b/w Target and host using DMA FIFO's

    Dear NI,      Am facing a problem while writing data into the DMA in the Host environment, Steps i did: 1. Invoked the FIFO in the Host environment. 2.Connected it to the VI reference. 3.Configured the DMA Depth. 4.Started the FIFO. 5.An Array is ini

  • History of Article Purchase Price (ERP)

    Hi! The only way that I know to get the calculated purchase price for an article in ERP is by using the function EINA_E_SINGLE_READ. However, this function always returns the today's price. Is there a way to get the price from the past, on given date

  • Problem in F4 help in Tcode PSV1

    Dear All In PSV1, when I select a business event and goto menu Attendance -> Correspondance -> Manual Output. A F4 help dialog appears. When I select a value from this F4 help it by default passes the last value entry. I even debugged the code and ch

  • Where can I find the recalibration procedure for the battery in my older Macbook Pro 15"

    Would appreciate a link or description of the procedure.  Just replaced the battery and after full charge, I removed the power cord and the battery dropped to 14% after only a couple hours of use of just browsing and email. 

  • Creating XML from XSD, Only create The First Element

    Hi, I create a XML File from a xsd schema by this way:             DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();           factory.setNamespaceAware(true);           factory.setValidating(true);                factory.setAttr