Multiple dbs RMAN backup

Hello

I have a question about RMAN.

I have 2 DBs in 2 different servers and I do a daily backup of the DBs with RMAN (catalog, simply the rman script) the two DBs are connected via an application that writes about the two DBs of data shared and connected to the applicazion it self, so if a db will stop and the other ceases to work the data I find on my request will become inconsistens (or at least I'll have some differences between the dbs).

Is there a way to create a single RMAN script that performs a backup of archive logs and db the two DBs simultaniously while I'm 100% sure that the data are taken exactly at the same time, and I don't have to worry about having differences of opinion between the two dbs in the case of a restore procedure? because if a db is in need of restoration, I'll have to restore the TWO dbs so that the application works correctly!

(I hope that explaied it pretty well)

I have Oracle 10.2.0.4 on Windows Server 2003 R2 SP2 EE

Thanks to you all!

You need to run two backups for databases.  What you can do is force archivelog switch and run backups, archivelog almost at the same time - as close as possible.

Backups isn't really the problem.  When RECOVERING after a RESTORE, you will need to do a RECOVERY with an UNTIL clause of TIME which is defined both on the two databases.  However, this does not really guarantee that the two databases are synchronized exactly because Oracle translated a SNA approximate TIME and did a cover of a SNA.  Thus, until "17 June 2013 13:04:05" could mean that a data base of operations until a second before 13:04:05, and another has transactions up to three seconds before 13:04:05.  You will need to determine ways of check data - for example to identify common tables and data of common tables.

Hemant K Collette

Tags: Database

Similar Questions

  • The user managed based backup Rman backup cold cold vs

    Hi all

    I just want to know the advantages and disadvantages for backup managed user cold and cold backup Rman.

    What is the best cold backup?

    Some some can help me?

    Thank you

    Cedric Joshi

    Hello

    Both are good only... If you took the clod backup (managed by the user), you can also do with RMAN catalog.

    I feel clod RMAN backup is good.

    Reason:

    ======

    ++ with RMAN you can avoid used used block, you can only backup used blocks

    ++ RMAN has its own compression algorithm

    ++ We also have the ability to assign multiple channels to parallelize the backup

  • location of RMAN backup

    Hello

    Oracle: 11.2.0.3

    I use after a command to back up the database, however the backup is performed in the oracle_home/dbs directory, rather than the format of my. No idea why?

    BACKUP incremental level 0 AS COMPRESS BACKUPSET of base of DATA PLUS ARCHIVELOG NO SAVED 2 TIME FORMAT ' / orastage/rman/backups/${ORACLE_SID}/backupset_%d_%u_%s_%T';

    Please try the below command

    Run {}

    Disc format type ALLOCATE CHANNEL c1 ' / orastage/rman/backups/${ORACLE_SID}/backupset_%d_%u_%s_%T';

    BACKUP incremental level 0 AS COMPRESSED BACKUPSET of base of DATA PLUS ARCHIVELOG NO SAVED 2 TIMES

    }

  • Hot RMAN backup fails every time in R12.

    Hi experts,

    Please suggest me that I have to plan rman backup hot. I have "write" command to perform hot backup. When I take backup hot of 1st time the backup completed successfully. but when I run the same command resume backup for the second day. it is impossible to give space issue I havhot e calendar for daily use rman backup.

    I had to take the backup hot daily and I want backup overwrite the backup file according to the daily backup.

    Please suggest me what I need to make changes in the configuration of rman and the rman command.

    OS - réhèl 5.6

    Database - 11.1

    EBS - r12.3

    configuration of RMAN:

    RMAN > show all.

    Database with db_unique_name UAT RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / d06/UAT/rman_hot_backup/Backup_daily%d_DB_%u_%s_%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / d06/UAT/db/tech_st/11.1.0/dbs/snapcf_UAT.f'; # by default

    RMAN >


    ##############################################################################################################


    RMAN command that I used to make hot extra strength 0 cumulative backup.


    RMAN > run
    {
    allocate channels c1 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    allocate channel c2 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    allocate channels c3 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    allocate channel c4 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    cumulative incremental database backup level 1 more archivelog;
    output channel c1;
    output channel c2.
    output channel c3.
    output channel c4.
    }

    If something bad in the configuration of rman and my order please suggest me to take the backup hot every day with success.


    concerning

    pritesh Rodriguez

    Hi Pritesh, thanks for the update. You can mark this thread as answered if your questions have been answered. cordially Karan

  • RAC RMAN backup

    Hello

    DB is 10.2.0.4 OS = BSG (CARS with 2 nodes BD01, db02). Here are the types of automated RMAN backups taken on db01.

    -OCR
    -Voting record
    -Talespaces Snapshot
    -Archivelog (hourly)
    -Backup incremental level 0 (SUNDAY)
    -backup incremental level 1 (Mon - Sat)
    -Automatic backup of the control file and SPFILE (CONTROLFILE AUTOBACKUP ON)

    Two big questions please. First of all, are these types of backups/backup are enough to RESTORE FULL speaking of RMAN backup on a RAC environment with 2 nodes? Otherwise please suggest what I need to backup?

    Second, home backup location is /rman that I can see on db01 ONLY. This directory of /rman that I don't see on db02. My question is what db02 failure can I restore from directory /rman? or do I need to automate the backup also schedules on db02 separately?
    [root@db01~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  2.9G  814M  79% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  225M  3.5G   6% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  379M  3.4G  11% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  8.7G  2.6G  78% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px
/dev/mapper/36001ec9000d5ea810000061349015d98
                      1.3T  551G  665G  46% /rman
    [root@db02~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  887M  2.9G  24% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  261M  3.5G   7% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  355M  3.4G  10% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  6.5G  4.8G  58% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px
    [oracle@db01~]$ rman target /

Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: F1 (DBID=1245145263)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 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 '/rman/f1/fullbackup/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default
    # Script for backup

level0 ()
run {
  allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
  allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
  backup incremental level 0 tag = weeklyfull database channel c1 
  plus archivelog tag = ARCH_$TODAY delete all input channel c2;
  release channel c1;
  release channel c2;
}

run {
  allocate channel c1 type disk;
  delete noprompt obsolete;
  release channel c1;
}
    Bundle of thanks.

    Kind regards

    Published by: 910385 on February 24, 2012 03:00

    Hi 910385,
    The error on the node db02

    ORA-19504: cannot create the file ' / rman/fp1/backup/c-1245145263-20120210-11.

    is caused by your installation.
    You have a /rman of mount point visible only on the node db01.
    The controlfile autobackup setting triggers the creation of a backup of the controlfile:
    -during the rman backup (this seems to work only on db01)
    -in the case of a structural change in the database (eg. Adding a data file).
    Sessions to make a structural change can be connected to one of your two instances, but the instance on db02 cannot create controlfile autobackup in /rman.
    You must change the configuration and put the backup on a shared disk that is seen by the two systems.
    Strangely, you have a shared file system:

    10.10.28.140:/vol/px4cinconso 40G 1.4 G 39G 4% /inconso_px

    Better would be to make a second for rman...
    Kind regards
    Tycho

  • Purge the rman backup

    Hello, since the alert.log file find this error:

    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc3_25352.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC3: 19809 creation error archive log file ' DATA01'+.
    Sea 25 09:51:58 Jan 2012
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19815: WARNING: 59055800320 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
    ************************************************************************
    You have choice to free up space in the recovery area:
    + 1. Consider changing the RMAN RETENTION POLICY. If you are using Data Guard +.
    then consider changing POLICY of DELETE ARCHIVELOG RMAN.
    + 2. Back up files on a tertiary device such as a tape using RMAN.
    SAFEGUARDING RECOVERY AREA command.
    + 3. Add disk space and increase the db_recovery_file_dest_size setting to +.
    reflect the new space.
    + 4. Delete unnecessary files by using the RMAN DELETE command. If operation +.
    the system control has been used to remove the files, and then use the RMAN DUPLICATION and
    Commands DELETE has EXPIRED.
    ************************************************************************
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC0: error creating 19809 archive log file ' DATA01'+.

    So I'm trying to purge the rman backup, but I have an error message:


    rman target = oratest@oraprdlnx1:~$ /+.
    Recovery Manager: release 11.2.0.1.0 - Production on sea Jan 25 09:47:30 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: TEST (DBID = 2044700519)

    + RMAN > show all; +.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name TEST are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/oratest/product/11.2.0/dbhome_1/dbs/snapcf_TEST1.f'; # by default

    + RMAN > allocate channel for maintenance of type; disc +.

    allocated channel: ORA_MAINT_DISK_1
    channel ORA_MAINT_DISK_1: SID = 237 instance = type of TEST1 = DISK

    + RMAN > crosscheck backup; +.

    "" element of verified backup: turned out to be "AVAILABLE"
    backup handle piece = RECID = 68 = 758320264 STAMP DATA01/test/autobackup/2011_08_04/s_758320263.794.758320265 +.
    Cut objects 1

    RMAN > delete obsolete; ** +

    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Backup Set 25 July 4, 11
    Backup total 25 4 July 11 1omgk64v_1_1
    Backup Set 26 July 4, 11
    Backup total 26 July 4, 11 1pmgk650_1_1
    Backup Set 24 July 4, 11
    Total backup, 24 4 July 11 1qmgk650_1_1
    Backup Set 21 July 4, 11
    Backup total 21 4 July 11 1rmgk650_1_1
    Backup Set 28 July 4, 11
    28 1vmgk69v_1_1 July 4, 11 total backup
    Save game 29 July 4, 11
    Backup total 29 July 4, 11 20mgk6a0_1_1
    Backup Set 30 July 4, 11
    Backup total 30 4 July 11 21mgk6a0_1_1
    Save game 31 July 4, 11
    Backup total 31 July 4, 11 22mgk6a0_1_1
    Backup Set 34 4 July 11
    Backup total 34 4 July 11 c-2044700519-20110704-07
    Backup Set 35 July 4, 11
    Total backup, 35 26mgk8ib_1_1 4 July 11
    Backup Set 36 4 July 11
    Backup total 36 4 July 11 c-2044700519-20110704-08
    Backup Set 41 4 July 11
    Backup total 41 4 July 11 28mgk94i_1_1
    Backup Set 42 4 July 11
    Backup total 42 4 July 11 29mgk94j_1_1
    Backup Set 37 July 4, 11
    Backup total 37 4 July 11 2amgk94j_1_1
    Backup Set 40 July 4, 11
    Backup total 40 July 4, 11 2bmgk94j_1_1
    Backup Set 38 July 4, 11
    Backup total 38 4 July 11 2cmgk95c_1_1
    Backup Set 39 July 4, 11
    Backup total 39 4 July 11 2dmgk95k_1_1
    Backup Set 43 July 4, 11
    Backup total 43 July 4, 11 c-2044700519-20110704-09
    Backup Set 46 4 July 11
    Backup total 46 4 July 11 2fmgk99f_1_1
    Backup Set 47 July 4, 11
    Backup total 47 4 July 11 2gmgk99g_1_1
    Backup Set 44 4 July 11
    Backup total 44 4 July 11 2hmgk99g_1_1
    Backup Set 48 4 July 11
    Backup total 48 4 July 11 2imgk99g_1_1
    Backup Set 45 4 July 11
    Backup total 45 4 July 11 2jmgk9a9_1_1
    Backup Set 50 4 July 11
    Backup total 50 4 July 11 2kmgk9aq_1_1
    Backup Set 49 July 4, 11
    Backup total 49 4 July 11 2lmgk9aq_1_1
    Backup Set 51 4 July 11
    51 4 July total backup has 11 c-2044700519-20110704-0
    Backup Set 56 4 July 11
    Total backup 56 2rmgk9qb_1_1 July 4, 11
    Backup Set 55 July 4, 11
    Backup total 55 4 July 11 2smgk9qb_1_1
    Backup Set 58 4 July 11
    Backup total 58 4 July 11 b c-2044700519-20110704-0
    Backup Set 60 4 July 11
    Total backup 60 2umgk9tb_1_1 July 4, 11
    Backup Set 61 4 July 11
    Backup total 61 4 July 11 2vmgk9tc_1_1
    Backs up the entire 62 4 July 11
    Backup total 62 4 July 11 30mgk9tc_1_1
    Backup Set 66 4 July 11
    Backup total 66 4 July 11 34mgk9ua_1_1
    Backs up the entire 65 4 July 11
    Backup total 65 4 July 11 35mgk9ua_1_1
    Backup Set 67 4 July 11
    Total backup, July 4, 11 c-2044700519-20110704-0 67C
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    How can I purge the db dest file recovery?

    Thank you!!!

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    There is a metalink note that talks about this error.

    Met RMAN-03002 and RMAN-06091 when deleting obsolete backups [567555.1 ID]
    RMAN could not remove obsolete in right Backupsets change Sbt_tape to disk and again Server [ID 1287755.1]

    HTH

    Kind regards
    Nagendra Chillale

    Published by: NC on January 25, 2012 17:00

  • How can I remove the old files of RMAN backup

    Hi all

    We have configured the RMAN backup for one of our customers [10.2.0.3] PROD instance in December 2010.

    Now my doubt is how can I delte old backup files in December and January, only this two months files backup only i need to delte.

    Please suggest me.

    The parameters are:
    CONFIGURE THE RETENTION NONE POLICY;
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / ebiz/backup/PROD-%F';
    SET UP THE DEVICE TYPE DISK BACKUP FOR PARALLELISM BACKUPSET TABLET 1 TYPE;
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / ebiz/backup/PROD-%U';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / ebiz/oracle/proddb/10.2.0/dbs/snapcf_PROD.f'; # by default


    Concerning
    Shaik

    Hello

    You can use this:

    DELETE BACKUP COMPLETED BEFORE TO_DATE('01/31/2011 00:00:00','MM/DD/YY HH24:MI:SS');

    Kind regards
    Sylvie

  • RMAN backup optimization CANCEL 11g

    Hi all?

    I tested 11g RMAN CANCEL backup optimization
    1 I filled out by manipulation sql undo tablespace and not commit
    2nd undo_ts backed up by RMAN (size 24 m)
    3rd I made a commit
    Then the tablespace undo supported again but the backup_size column has not changed (24 m)
    Then I did some more manipulations and supported undo_ts again. This reduced time backup_size column. (11 m)
    Then I rebooted db and saved to undo_ts again. Size of backup at this time became what I expected (600K)

    The question is why did not reduce the size 11 g rman undo tablespace backups after validation?
    According to 11 g cancel optimization to

    ...
    SQL > select sum (bytes) of dba_free_space where nom_tablespace = 'UNDOTBS2 ';
    SUM (BYTES)
    13172736
    SQL > start
    because me 1.100000 loop
    insert into testundo values (i);
    end loop;
    end;
    /
    2 3 4 5 6
    PL/SQL procedure successfully completed.
    SQL > SQL > update of testundo game
    ID = 2 where id > 0;
    2
    Update testundo set
    *
    ERROR on line 1:
    ORA-30036: unable to extend segment by 8 in undo tablespace "UNDOTBS2".
    SQL > select sum (bytes) of dba_free_space where nom_tablespace = 'UNDOTBS2 ';
    Sum (bytes)
    RMAN > backup datafile 6;

    RMAN > backup from the list of the 6 data file;


    List of backup sets
    ===================

    Time of accomplishment BS key Type LV size device Type elapsed time
    10 full * 24.54M* DISK 00:00:04 June 10, 10
    BP key: 10 location: AVAILABLE Tablet: NO Tag: TAG20100610T142437
    Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
    List of files of data backup set 10
    Name of file LV Type cash SNA cash time
    6 integer 577669 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10


    SQL > commit;

    Full validation.
    RMAN > backup datafile format 6 "after commit.backup";

    RMAN > backup from the list of the 6 data file;

    List of backup sets
    ===================

    Time of accomplishment BS key Type LV size device Type elapsed time
    11 full * 24.54M* DISK 00:00:02 June 10, 10
    BP key: 11 location: AVAILABLE Tablet: NO Tag: TAG20100610T142541
    Item name: / home/oracle/product/11/Db_1/dbs/after commit.backup
    List of files of data backup set 11
    Name of file LV Type cash SNA cash time
    6 integer 577705 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10
    SQL > alter system archive log current;
    Modified system.
    SQL > commit;
    Validation complete.
    SQL > select count (*) in the testundo;
    COUNT (*)
    100000
    SQL > delete from testundo;
    100000 deleted rows.
    SQL > commit;
    Validation complete.
    SQL > insert into testundo values (1);
    1 line of creation.
    SQL > commit;
    Validation complete.
    SQL > alter system flush buffer_cache;
    Modified system.
    RMAN > backup datafile 6;

    RMAN > backup from the list of the 6 data file;


    List of backup sets
    ===================

    Time of accomplishment BS key Type LV size device Type elapsed time
    13 full * 11.03M* DISK 00:00:01 June 10, 10
    BP key: 13 status: AVAILABLE Tablet: NO Tag: TAG20100610T143359
    Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
    List of files to backup data value 13
    Name of file LV Type cash SNA cash time
    6 integer 578410 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10

    RMAN >
    SQL > shutdown immediate;
    The database is closed.
    The database is dismounted.
    ORACLE instance stops.
    SQL > startup
    ORACLE instance started.

    Total System Global Area 393375744 bytes
    Bytes of size 1300156 fixed
    352323908 variable size bytes
    33554432 buffers of data bytes
    Redo buffers 6197248 bytes
    Mounted database.
    Open database.
    SQL >
    RMAN > backup datafile 6;
    RMAN > backup from the list of the 6 data file;


    List of backup sets
    ===================

    Time of accomplishment BS key Type LV size device Type elapsed time

    Full 14 * DISK 00:00:02 600.00K* 10 June 10
    BP key: 14 location: AVAILABLE Tablet: NO Tag: TAG20100610T152843
    Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
    List of defined backup data files 14
    Name of file LV Type cash SNA cash time

    6 integer 580347 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10

    Thanks in advance
    Turkel

    Hi Turkel,
    Space used to cancel is also linked to the undo retention implementation.
    As it seems do you an update of test and perform backups on:
    -14: 24:37 (-> 25 M)
    -14: 25:41 (-> 25 M)
    -14:33:59 (-> 11 M)
    -15: 28:43 (-> 600 K)
    The first two backups are probably still in the retention period to cancel the update.
    The third backup shows a cancellation partly empty (is your setting 900?).
    The last falls outside the period of retention for the update, resulting the small size of backup.
    Kind regards
    Tycho

  • What is the diff between backupset and element of RMAN backup

    Hello

    Please help me understand the diff backupset with RMAN backup element

    Thank you

    Hello

    Are you can, use the BACKUP AS BACKUPSET command, you can have a multiple backupsets.

    Kind regards
    Delphine K

  • recover the database on windows xp linux rman backup

    Hi guys,.

    I am recovering a xp database that runs on Centos 5.3 on windows xp.

    That's what I did.
    backup database
    Run {}
    maxcorrupt for the data file the value 2 to 1;

    CONFIGURE REDUNDANCY 5 RETENTION STRATEGY;
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/snapcf_XE.f'; # by default
    compressed backup backupset database;
    backup current controlfile;
    backup SPFile;
    }

    FTP files on Windows
    SQL > startup mount restrict exclusive;
    SQL > drop database;

    SQL > startup nomount;
    RMAN > set dbid = 7898909
    RMAN > recover automatic backup controlfile;

    And then the problems begin.
    because the controlfile contains the former locations of tablespaces (linux).
    I try with set newname for data file does not work because old tablespaces are not there.
    If I try to backup the controlfile to find and change the locations, it still does not because I don't have the files of data in place.

    In short; How to restore and recover the database from a backup of linux on windows?

    Hello

    Rman backups are not portable between operating system platforms.
    You must use the convert command.
    Please follow the link which explains the controls and the procedure below.
    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14191/dbxptrn.htm#CHDCFFDI

    Kind regards
    Tycho

  • Import of schemas and tables of RMAN backup

    Hi all

    I have here are 3 requirements:

    (1) is it possible that I can import a single table using RMAN backup, because I have no more than one day of EXPDP dump file and the requirement is to store the data of three days.

    (2) is it possible that I can import a single SCHEMA using RMAN backup, because I have no more than one day of EXPDP dump file and the requirement is to store the data of three days.

    (3) can I import a package from the RMAN backup?

    I have incremental backup of level 1 and level 0.

    My database is 11.2.0.3

    Thank you and best regards,

    Mukesh

    Hi Mukesh,

    All of your needs can be met with output up to 11g using RMAN database, but beyond of 12 c, you can restore a single table RMAN backup (RMAN BACK TABLE new feature to the 12 c (Doc ID 1521524.1) Oracle database). For your condition impdp/expdp is the best Utilities option until oracle provided up to version 11 g.

    I hope this helps.

    Kind regards

  • RMAN backup location must change and remove obsolete

    Dear Experts,

    I'm working on the following environment,

    Operating system: Windows server 2012 R2

    Oracle version: 11.2.0.1.0 release

    Type of RMAN backup: Cumulative (preferred by the direction and I can't change it in differential backup)

    My current situation,

    I set up RMAN and H: drive for purposes of backup and G: for Archivelog.

    Recently, my city was covered by the flood waters and the server works not for a week so that we delete obsolete level 0 does not work.

    Currently there is not enough space to run a level 1 and level 0, while I should change the backup location.

    My Question is,

    (1) I need to change this location of drive H: to G: drive backup backup correctly without error not enough space.

    (2) after having taken a level 1 and level 0, depending on my 1 redundancy, RMAN mechanism should delete obsolete backup disk without failure G: and H:.

    Kindly help me how to get to my need. This will help me, thanks in advance

    You can

    1. replace the DB_RECOVERY_FILE_DEST G:

    2 run backups

    3. wait for the DELETE OBSOLETE delete obsolete backups of H:

    and then

    4. change the DB_RECOVERY_FILE_DEST return h as it was more early

    In this way, you don't have to use the FORMAT or CHANNEL of CONFIGURE commands (I was referring to CONFIGURE CHANNEL, not ALLOCATE CHANNEL) to change the destination of the backup

    Hemant K Collette

  • Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

    Here's my question after tons of research and test without have the right solutions.

    Target:

    (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

    (2) I created physical standby database "stbydb" on the server "node2".

    (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

    (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

    (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

    (6) I do RMAN backup (database and archivelog) on the site of relief only.

    (7) I want to use this backup for full restore of the database on the primary database.

    He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

    Here is how to save, on the database pending:

    (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

    (2) RMAN > backup database;

    (3) RMAN > backup archivelog all;

    I got elements of backup and copied to primary db Server something like:

    /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

    /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

    /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

    So here's how to restore, on the main site:

    I clean all the files (data files, controlfiles oder all gone).

    (1) restore spfile from pfile

    RMAN > startup nomount

    RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    (2) modify pfile to convert to db primary content. pFile shows below

    *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

    * .audit_trail = "db".

    * full = '12.1.0.2.0'

    *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

    * .db_block_size = 8192

    * .db_domain = "

    *.db_file_name_convert='/testdb/','/testdb /'

    * .db_name = "testdb".

    * .db_recovery_file_dest ='/ orafra'

    * .db_recovery_file_dest_size = 10737418240

    * .db_unique_name = "testdb".

    *.diagnostic_dest='/opt/Oracle/DB '

    * .fal_server = "stbydb".

    * .log_archive_config = 'dg_config = (testdb, stbydb)'

    * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

    * .log_archive_dest_state_2 = 'ENABLE '.

    *.log_file_name_convert='/testdb/','/testdb /'

    * .memory_target = 1800 m

    * .open_cursors = 300

    * runoff = 300

    * .remote_login_passwordfile = "EXCLUSIVE."

    * .standby_file_management = "AUTO".

    * .undo_tablespace = "UNDOTBS1.

    (3) restart db with updated file pfile

    SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

    SQLPLUS > the judgment

    SQLPLUS > startup nomount

    (4) restore controlfile

    RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    RMAN > change the editing of the database

    (5) all elements of backup catalog

    RMAN > catalog starts by ' / home/oracle/backupset / '.

    (6) restore and recover the database

    RMAN > restore database;

    RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

    (7) open resetlogs

    RMAN > alter database open resetlogs;

    Everything seems perfect, except one of the file log roll forward pending is not generated

    SQL > select * from v$ standby_log;

    ERROR:

    ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

    ORA-27037: unable to get file status

    Linux-x86_64 error: 2: no such file or directory

    Additional information: 3

    no selected line

    I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

    So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

    And I got the same missing log file.

    The problem is:

    (1) complete alert.log filled with this error, not the concern here

    (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

    (3) I can't delete and re-create this log file

    Then I tried several and found:

    The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

    For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

    ---------- ---------- ---------- ----------

    4 19 ACTIVE 133632

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    So until I take the backup, I tried on the primary database:

    SQL > alter system set log_archive_dest_state_2 = delay;

    This was the Group of standby_log side Eve #4 was released:

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

    ---------- ---------- ---------- ----------

    4 0 0 UNASSIGNED

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    Then, the backup has been restored correctly without missing standby logfile.

    However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

    Finally, my real questions come:

    (1) what I do may not do on parameter change?

    (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

    I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

    And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

    I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

    Your idea is very much appreciated.

    Thank you!

    Hello

    1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

    2nd--> when we opened the ORL database should be deleted and created

    3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

    DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

    THREAD # SEQUENCE # GROUP # STATUS

    ---------- ---------- ---------- ----------

    1 233 4 ACTIVE

    1 238 5 ACTIVE

    DR sys@cdb01 SQL > select * from v$ logfile;

    GROUP # STATUS TYPE MEMBER IS_ CON_ID

    ---------- ------- ------- ------------------------------ --- ----------

    3 /u03/cdb01/cdb01/redo03.log no. 0 online

    /U03/cdb01/cdb01/redo02.log no. 0 2 online

    1 /u03/cdb01/cdb01/redo01.log no. 0 online

    4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

    /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

    DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

    DR sys@cdb01 SQL > alter database force claire logfile 4;

    change the database group claire logfile 4

    *

    ERROR on line 1:

    ORA-01156: recovery or current flashback may need access to files

    DR sys@cdb01 SQL > alter database recover managed standby database cancel;

    Database altered.

    DR sys@cdb01 SQL > change the database group claire logfile 4;

    Database altered.

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

    DR sys@cdb01 SQL >

    If you do, you can recreate the controlfile without waiting for redo log entry...

    If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

    Thank you

  • RMAN backup gets already

    Hi all;

    RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";

    new RMAN configuration settings:

    CONFIGURE the CHANNEL 1 DEVICE TYPE DISK FORMAT ' / u01/rmanbkp ";

    new RMAN configuration settings are stored successfully

    output channel: ORA_DISK_1

    RMAN > list backup;

    specification does not match the backups in the repository

    RMAN > backup database tag = "NORMAL_BKP_15_jul_15";

    From 25 July 15 backup

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 20 type of device = DISK

    channel ORA_DISK_1: from complete compressed datafile backup set

    channel ORA_DISK_1: specifying datafile (s) in the backup set

    Enter a number of file datafile = 00005 name=/u03/app/oracle/oradata/crms/tbs02.dbf

    Enter a number of file datafile = 00001 name=/u02/app/oracle/oradata/crms/system01.dbf

    Enter a number of file datafile = name=/u01/crmsx4.dbf 00024

    channel ORA_DISK_1: starting piece 1 to July 25, 15

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 25/07/2015 10:30:26

    ORA-19504: cannot create the file ' / u01/rmanbkp.

    ORA-27038: created file already exists

    Additional information: 1

    There is no file physically in/u01/rmanbkp

    DB version: 11.2.0.1 on (Redaht)

    RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";


    Specify format with extension, something like below

    RMAN > set up the channel 1 device type disk format ' / u01/rmanbkp/backup%U';

    http://docs.Oracle.com/CD/B28359_01/backup.111/b28273/rcmsubcl010.htm

  • content managed rman backup crushing and selection procedure of the tape media

    Hello Experts.

    I have a question about the backupset rman tape media manage tape of the osb.

    [ENV]

    Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.

    1 Appendix backup on OS crontab

    -Each backup full day at 00:00 AM

    2 rman view all:

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    using the control file of the target instead of recovery catalog database

    RMAN settings for database with db_unique_name TESTDW are:

    CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;

    CONFIGURE BACKUP OPTIMIZATION # by default

    CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';

    SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    3 rman backup scirpts

    Run {}

    allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';

    allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';

    Backup section size 900g database;

    output channel c01;

    output channel c02;

    output channel c03;

    output channel c04;

    }

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.

    and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)

    So, I issue the command 'lsvol - a - c' and could not display expired on all media content.

    Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.

    Why OSB does not have the expired status of rman content on tape media?

    -> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?

    Q2 > selection procedure for the tape media all backup rman

    Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.

    Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)

    If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?

    Advanced thanks.

    If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

    the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

    Yes.

    I use the catalog of recovery on a different database and backup script has catalog db connection string.

    And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

    Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

    After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

    Kind regards

    Mitja

Maybe you are looking for