RMAN level 0 backup with bigfile tablespaces

We noticed that our rman backup process for PROD database is not working properly.
  PROD is a 8 TB size database having two bigfile tablespaces each having more than 2 TB datafile.
  PROD is a 11gR1 (11.1.0.7) RAC database with ASM storage.
   We are taking weekly incremental level 0 backup for entire database and level 1 backup every day.
  As per v$session_longops, the approx completion time for the two tablespaces is 5 days.
We can use "SECTION SIZE" parameter to take rman backup for bigfile tablespaces and exclude them from the level 0 backup.
However, in this case our level 0 backup wont include the two bigfile tablespaces and the daily level 1 backup will not include them.
Will you pls advise us on how to take backup in this scenario.
we have only 4TB of LUN allocated for backup and have to keep 7 days of backup on disk.
Thanks in advance !
DR

We can use "SECTION SIZE" parameter to take rman backup for bigfile tablespaces and exclude them from the level 0 backup.
How do you think that the backup will be useful if you exclude some files from level 0 or base backup? You will find difficulties or you can't restore the database in case of disaster.
Yes you can use section size parameter for paralleled big file tablespace backup.
Check below for explanation and example.
Backing Up the Database: Advanced Topics
http://www.oracle-base.com/articles/11g/rman-enhancements-11gr1.php#multisection_backups
You can use the below note for your case which will be of help.
Reducing RMAN backup time for unevenly sized tablespaces « Oracle DBA – A lifelong learning experie…
Thank you!!

Similar Messages

  • Restore Database to non-ASM Storage - Issue with Bigfile Tablespace

    I have been testing a restore of my prod database that uses ASM (and oracle managed files) for storage to a different server and non-ASM storage. Oracle version is 10g EE. My database has one bigfile tablespace and it's datafile is about 250GB. The restore fails and it has something to do with the bigfile tablespace.
    Here is the rman restore script:
    run
    set newname for datafile 1 to '/ora01/db/ehr/system01.dbf';
    set newname for datafile 2 to '/ora01/db/ehr/undotbs01.dbf';
    set newname for datafile 3 to '/ora01/db/ehr/sysaux01.dbf';
    set newname for datafile 4 to '/ora01/db/ehr/undotbs02.dbf';
    set newname for datafile 5 to '/ora01/db/ehr/users01.dbf';
    set newname for datafile 6 to '/ora01/db/ehr/apolloaud01.dbf';
    set newname for datafile 7 to '/ora01/db/ehr/apollohist01.dbf';
    set newname for datafile 8 to '/ora01/db/ehr/apolloidx01.dbf';
    set newname for datafile 9 to '/ora01/db/ehr/apollotab01.dbf';
    set newname for datafile 10 to '/ora01/db/ehr/apollotab02.dbf';
    set newname for datafile 11 to '/ora02/db/ehr/apollolob01.dbf';
    set newname for datafile 12 to '/ora01/db/ehr/apollofdb01.dbf';
    set newname for datafile 13 to '/ora01/db/ehr/apolloidx02.dbf';
    set newname for datafile 14 to '/ora01/db/ehr/apolloidx03.dbf';
    set newname for datafile 15 to '/ora01/db/ehr/apolloaud02.dbf';
    set newname for datafile 16 to '/ora01/db/ehr/apollotab03.dbf';
    set until sequence 60298 thread 2;
    restore database;
    switch datafile all;
    recover database;
    Datafile 11 is the datafile in the bigfile tablespace. Here are the weird things about the restore:
    1. The restore output shows this:
    creating datafile fno=11 name=/ora02/db/ehr/apollolob01.dbf
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /ora01/db/ehr/system01.dbf
    restoring datafile 00002 to /ora01/db/ehr/undotbs01.dbf
    restoring datafile 00003 to /ora01/db/ehr/sysaux01.dbf
    restoring datafile 00004 to /ora01/db/ehr/undotbs02.dbf
    restoring datafile 00005 to /ora01/db/ehr/users01.dbf
    restoring datafile 00006 to /ora01/db/ehr/apolloaud01.dbf
    restoring datafile 00007 to /ora01/db/ehr/apollohist01.dbf
    restoring datafile 00008 to /ora01/db/ehr/apolloidx01.dbf
    restoring datafile 00009 to /ora01/db/ehr/apollotab01.dbf
    restoring datafile 00010 to /ora01/db/ehr/apollotab02.dbf
    restoring datafile 00012 to /ora01/db/ehr/apollofdb01.dbf
    restoring datafile 00013 to /ora01/db/ehr/apolloidx02.dbf
    restoring datafile 00014 to /ora01/db/ehr/apolloidx03.dbf
    restoring datafile 00015 to /ora01/db/ehr/apolloaud02.dbf
    restoring datafile 00016 to /ora01/db/ehr/apollotab03.dbf
    Why at the beginning is it "creating" datafile 11? Then it doesnt even say it is "restoring" that datafile. Only restoring datafiles 1,2,3,4,5,6,7,8,9,10,12,13,14,15, and 16.
    When it creates datafile 11 it is only 26GB, that is much smaller than it should be according to v$datafile view on source prod database. Also even though it says it is creating datafile 11 as /ora02/db/ehr/apollolob01.dbf it actually creates it as an oracle managed file at /ora02/db/ehr/EHR/datafile/o1_mf_apollolo_6crxyqs2_.dbf
    After the datafiles are restored the "switch datafile all" command fails:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of switch command at 10/18/2010 13:58:37
    ORA-19625: error identifying file /ora02/db/ehr/apollolob01.dbf
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    So my question is how do I get this database restored to non-ASM (and non omf)?

    So I tried using a different scn with my "set until scn #####" then the restore created 2 datafiles. The datafile for apollolob and apollotab02.dbf. So I think I have narrowed the problem to be that I am not using the correct scn number so RMAN can successfully restore those datafiles and recreates them instead. How do I find the correct scn to use to do a successful restore of the entire database? I have seen different methods on the web, but cant figure it out. Ive used "select archivelog_change#-1 from v$database;" and I also did "list backup of archivelog all" and used the latest sequence number. How can I find the correct scn to use so the entire database will restore?
    Here is the output of "list backup":
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    19724 41.12M DISK 00:00:10 14-OCT-10
    BP Key: 65840 Status: AVAILABLE Compressed: YES Tag: TAG20101014T210022
    Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113195_piece1_copy1_20101014
    List of Archived Logs in backup set 19724
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 50439 3230234843 14-OCT-10 3230268282 14-OCT-10
    1 50440 3230268282 14-OCT-10 3230286806 14-OCT-10
    2 60280 3230234852 14-OCT-10 3230251419 14-OCT-10
    2 60281 3230251419 14-OCT-10 3230268263 14-OCT-10
    2 60282 3230268263 14-OCT-10 3230286809 14-OCT-10
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    19725 Full 126.40G DISK 09:11:51 15-OCT-10
    List of Datafiles in backup set 19725
    File LV Type Ckp SCN Ckp Time Name
    1 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/system.625.609259453
    2 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs1.620.609259461
    3 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/sysaux.768.609259463
    4 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs2.632.609259467
    5 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/users.257.609259471
    6 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.316.619537285
    7 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollohist.629.619538155
    8 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.312.619538169
    9 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.276.619538487
    10 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.576.619539331
    11 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollolob.570.619539593
    12 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollofdb.750.645974339
    13 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.429.651171265
    14 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.705.688680793
    15 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.747.699632315
    16 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.330.715622123
    Backup Set Copy #1 of backup set 19725
    Device Type Elapsed Time Completion Time Compressed Tag
    DISK 09:11:51 20-OCT-10 YES TAG20101014T210039
    List of Backup Pieces for backup set 19725 Copy #1
    BP Key Pc# Status Piece Name
    65851 1 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece1_copy1_20101014
    65862 2 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece2_copy1_20101014
    65873 3 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece3_copy1_20101014
    65884 4 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece4_copy1_20101014
    65895 5 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece5_copy1_20101014
    65901 6 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece6_copy1_20101014
    65902 7 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece7_copy1_20101014
    65903 8 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece8_copy1_20101014
    65904 9 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece9_copy1_20101014
    65841 10 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece10_copy1_20101014
    65842 11 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece11_copy1_20101014
    65843 12 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece12_copy1_20101014
    65844 13 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece13_copy1_20101014
    65845 14 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece14_copy1_20101014
    65846 15 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece15_copy1_20101014
    65847 16 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece16_copy1_20101014
    65848 17 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece17_copy1_20101014
    65849 18 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece18_copy1_20101014
    65850 19 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece19_copy1_20101014
    65852 20 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece20_copy1_20101014
    65853 21 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece21_copy1_20101014
    65854 22 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece22_copy1_20101015
    65855 23 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece23_copy1_20101015
    65856 24 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece24_copy1_20101015
    65857 25 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece25_copy1_20101015
    65858 26 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece26_copy1_20101015
    65859 27 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece27_copy1_20101015
    65860 28 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece28_copy1_20101015
    65861 29 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece29_copy1_20101015
    65863 30 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece30_copy1_20101015
    65864 31 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece31_copy1_20101015
    65865 32 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece32_copy1_20101015
    65866 33 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece33_copy1_20101015
    65867 34 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece34_copy1_20101015
    65868 35 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece35_copy1_20101015
    65869 36 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece36_copy1_20101015
    65870 37 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece37_copy1_20101015
    65871 38 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece38_copy1_20101015
    65872 39 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece39_copy1_20101015
    65874 40 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece40_copy1_20101015
    65875 41 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece41_copy1_20101015
    65876 42 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece42_copy1_20101015
    65877 43 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece43_copy1_20101015
    65878 44 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece44_copy1_20101015
    65879 45 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece45_copy1_20101015
    65880 46 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece46_copy1_20101015
    65881 47 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece47_copy1_20101015
    65882 48 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece48_copy1_20101015
    65883 49 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece49_copy1_20101015
    65885 50 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece50_copy1_20101015
    65886 51 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece51_copy1_20101015
    65887 52 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece52_copy1_20101015
    65888 53 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece53_copy1_20101015
    65889 54 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece54_copy1_20101015
    65890 55 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece55_copy1_20101015
    65891 56 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece56_copy1_20101015
    65892 57 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece57_copy1_20101015
    65893 58 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece58_copy1_20101015
    65894 59 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece59_copy1_20101015
    65896 60 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece60_copy1_20101015
    65897 61 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece61_copy1_20101015
    65898 62 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece62_copy1_20101015
    65899 63 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece63_copy1_20101015
    65900 64 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece64_copy1_20101015
    BS Key Size Device Type Elapsed Time Completion Time
    19726 228.10M DISK 00:00:49 15-OCT-10
    BP Key: 65905 Status: AVAILABLE Compressed: YES Tag: TAG20101015T061242
    Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113197_piece1_copy1_20101015
    List of Archived Logs in backup set 19726
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 50441 3230286806 14-OCT-10 3230331993 14-OCT-10
    1 50442 3230331993 14-OCT-10 3230401945 14-OCT-10
    1 50443 3230401945 14-OCT-10 3230469794 15-OCT-10
    1 50444 3230469794 15-OCT-10 3230555010 15-OCT-10
    1 50445 3230555010 15-OCT-10 3230618396 15-OCT-10
    1 50446 3230618396 15-OCT-10 3230695020 15-OCT-10
    2 60283 3230286809 14-OCT-10 3230304858 14-OCT-10
    2 60284 3230304858 14-OCT-10 3230330891 14-OCT-10
    2 60285 3230330891 14-OCT-10 3230354275 14-OCT-10
    2 60286 3230354275 14-OCT-10 3230366292 14-OCT-10
    2 60287 3230366292 14-OCT-10 3230399805 14-OCT-10
    2 60288 3230399805 14-OCT-10 3230423577 14-OCT-10
    2 60289 3230423577 14-OCT-10 3230446176 15-OCT-10
    2 60290 3230446176 15-OCT-10 3230469756 15-OCT-10
    2 60291 3230469756 15-OCT-10 3230496786 15-OCT-10
    2 60292 3230496786 15-OCT-10 3230524710 15-OCT-10
    2 60293 3230524710 15-OCT-10 3230554981 15-OCT-10
    2 60294 3230554981 15-OCT-10 3230583802 15-OCT-10
    2 60295 3230583802 15-OCT-10 3230610465 15-OCT-10
    2 60296 3230610465 15-OCT-10 3230617887 15-OCT-10
    2 60297 3230617887 15-OCT-10 3230673207 15-OCT-10
    2 60298 3230673207 15-OCT-10 3230695022 15-OCT-10

  • RMAN merge backup with compression

    Hi All,
    Os : solaris 10
    db: 10.2.0.4
    as of now as per our backup strategy we are taking RMAN levle 0 weekly and daily incremental backup as compressed.
    we are planning to take RMAN merge backup like below
    For full backup on sunday
    backup incremental level 0 AS COPY tag 'DEMO_MERGE_DB' database ;rest of the days
    BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'DEMO_MERGE_DB' DATABASE;My question is , while taking as merge is there any option to compress the backup.
    i have gone through but dint see any info regarding this.
    Please help...
    Thanks in Advance
    Mvk

    merge backup , updated backup and image copy are these things are same or any difference inbetween..Image copy of backup copy of the data file
    merge backup means that you take incremental backup of data and merge it with the image backup copy of the datafile so that backup copy is updated all the time and in case of recovery, you don't need to apply all archives since backup copy because his copy is already up to date till the time of last merge backup.
    Now your image copy backup is an updated backup because it is keep on updated with the incremental backups using merge backup strategy.
    Salman

  • RMAN online backup with dbconsole.

    I want to run an online (hot) backup of a 10g enterprise edition database using dbconsole. There is no option for this on the web page that I can see. I thought I could trick the software by selecting 'whole backup' and then edit the RMAN script and enter the command 'backup database plus archivelog'. That command was documented as the way to run an onlne backup in the Oracle Press book 'Oracle Database 10g, RMAN Backup & Recovery'.
    But there was a message stating that the database would be brought down during the backup, obviously ignoring the command mentioned above.
    1. Can I perform a hot backup with dbconsole?
    2. If so, how?

    You can also review the following;
    OBE
    Performing Backups and Recovering Your Database
    Performing Backups
    http://www.oracle.com/technology/obe/10gr2_db_single/ha/rman/rman_otn.htm#t1
    Adith

  • Incremantal Backups with RMAN

    Hello, I was wondering if RMAN incremental backups are cumulative? If I do incrementals every night, would each night consist of every thing since the last full backup? Here is the script that I am using to perform my nightly incremental backups:
    Retention policy is 7 days.
    run{
    allocate channel c1 device type disk format 'F:\rman_backups\ incremental\rman_incr_%n_%T_%s_%p.bak';
    backup level 1 database plus archivelog;
    allocate channel for maintenance device type disk;
    delete archivelog until time 'sysdate - 7' backed up 2 times to disk;
    delete obsolete device type disk;
    Thank you

    Hi David
    What do you mean with "different backup levels"? The differences between the cumulative and the differential backup or what "has been backed up" after a level 1 (cumulative/differential) backup?
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96565/rcmsynta9.htm#78484
    INCREMENTAL LEVEL = integer
    Copies only those data blocks that have changed since the last incremental integer backup, where integer is any integer from 0 to 4. For example, in a level 2 backup RMAN backs up all blocks used since the most recent level 2, level 1, or level 0 backup.
    This type of incremental backup is also called a differential backup to distinguish it from a cumulative backup.
    A level 0 backup must exist as the base backup for an incremental strategy. An incremental backup at level 0 is identical in content to a full backup, but unlike a full backup the level 0 backup is considered a part of the incremental strategy.
    If no level 0 backup exists when you run a level 1 or higher backup, then RMAN makes a level 0 backup automatically.
    Oracle performs checks when attempting to create an incremental backup at a level greater than 0.
    These checks ensure that the incremental backup is usable by a subsequent RECOVER command. Among the checks performed are:
        * A level 0 backup set must exist, or level 0 datafile copies must exist for each datafile in the BACKUP command. These backup sets must not be marked UNAVAILABLE.
    If no level 0 backup exists, then RMAN automatically generates one.
        * Sufficient incremental backups taken since the level 0 must exist and be available such that the incremental backup to be created is usable.
    If you specify INCREMENTAL, then in the backupSpec clause you must set one of the following parameters: DATAFILE, DATAFILECOPY, TABLESPACE, or DATABASE.
    RMAN does not support incremental backups of control files, archived redo logs, or backup sets.
    Note: You cannot make inconsistent incremental backups when the database is in NOARCHIVELOG mode.
    Hence, you cannot generate incremental backups when a NOARCHIVELOG database is open and in use.Here you can find the "top" description about "Incremental Backups";
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc1.htm#458838
    Bye, Aron

  • How to backup read only tablespace in rman

    Hi,
    I am using oracle 10gR2 in solaris 10.
    I am taking Rman full backup using catalog.
    My target database have 5 datafiles, in that one datafile is in read only mode.
    When I issue the backup command in rman. it takes only 4 datafiles. its not taking the readonly datafile.
    I want to take backup of all 5 datafiles.
    kindly help me..
    Many Thanks

    My target database have 5 datafiles, in that one datafile is in read only mode.I presume that you mean to say that 1 Tablespace consisting of 1 datafile is Read Only.
    What does SHOW ALL in RMAN present ?
    If you have BACKUP OPTIMIZATION set to ON, the Read Only Tablespace will not be backed up after the first backup.
    You could still explicitly backup the tablespace with a BACKUP TABLESPACE tablespacename; , although a BACKUP DATABASE would exclude it.
    Hemant K Chitale
    http://hemantoracledba.blogspot.com
    Edited by: Hemant K Chitale on May 3, 2010 12:02 AM

  • RMAN backup with smallest backup size

    Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
    backup incremental level 0 tag 'level_0' database plus archivelog;
    --Other days
    backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
    What are you comments and opinions. Thanks

    Pavan, Thank you for reply. Here are the info requested
    what is size of DB ??
    ~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
    what would be max size of archive logs generated per day ??
    Variable from less than 1 GB to 12 GB
    Are you taking backups to tape or Disk ??
    Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
    Provide the Rman configuration information ??
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name TDEV2 are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    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';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_tdev2.f'; # default

  • Rman backup with  standby database

    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance

    726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance
    "I scanned thru MOS but could find solutions for rman with active DG."
    Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

  • RMAN level 0 and level 1 tablespace/database relationships

    If I take an incremental level 0 backup of an entire database and then take a level 0 of an individual tablespace, does an incremental level 1 backup of that tablespace reference the incremental level 0 of the tablespace or of the entire database? If I change the order of the level 0 backups, does it change the reference of the tablespace's level 1?
    I guess what I'm asking is does the the level 1 incremental reference the latest level 0 regardless of whether it's for the whole database or just the tablespace or does a level 1 always reference it's own level 0?
    Also, if I take a level 0 of the database Sunday night, and then a level 1 of the database every night after that as well as multiple level 1s of a tablespace throughout each day, will Tuesday night's database level 1 include all of Monday's tablespace level 1s?
    I just can't seem to find oracle documentation about these relationships.

    Hemant K Chitale wrote:
    "Database" and "Tablespace" are logical groupings for our convenience.
    RMAN tracks backups at the datafile level.I think that is exactly what I was looking for. I just want to clarify my understanding.
    If I run a level 0 on the database Sunday night, a database differential level 1 each night, and a level 0 on a specific tablespace each morning at 6AM followed by hourly tabelspace differential incrementals only for that tablespace, then Monday night's level 1 will be an incremental of the entire database pointing to Sunday's level 0 except for that specific tablespace for which it will be incremental from that tablespace's last level 1. Does that sound right? If so, then it sounds like to restore the entire database to its state on Tuesday at noon from media, I have to put these backups back on disk before running the RMAN restore:
    - database level 0 from Sunday
    - Monday night's database level 1
    - Tuesday's tablespace level 0
    - Tuesday's tablespace level1s from 7AM - noon
    This means I can avoid putting Monday's tabelspace incrementals back right? From what I gather, the RMAN restore will put the blocks back into the datafiles at their correct SCNs, and then if there are any archive logs after that point in time, the RMAN recover will apply them. Does that all sound correct?

  • Rman archivelog backup fails with rman-03002,ora-19563

    Hi,
    D:\ Oracle- -\BIN\RMAN TARGET / NOCATALOG
    RMAN> backup archivelog all;
    RMAN-03002: Error with backup command on 06-25-2013
    ORA-19563: Header-Validation is not successful.
        fails with the given errors.
    11.2.0.2 PROD DB on Windows Server 2008  R2 Enterpriise.
    When I issue BACKUP INCREMENTAL LEVEL 0 DATABASE; it works fine. but with archivelog it is creating problems. Unfortunatly, I have not found exactly the same problem on google and on Oracle support.
    The DB is using INIT.ORA and last time when I switched the mode to archive log mode I set the parameter like SCOPE=MEMORY as SPFILE was not in use and ALTER SYSTEM with SCOPE=BOTH  FRA destination and size, but after the DB restarting of course that setting is gone and I am having these problems.
    Please suggest.
    Thanks a lot.
    Best Regards,

    Hi,
    Thanks a lot.
    I don't think that archivelogs were relocated, except I changed the location yesterday.
    As I wrote at the start that because of INIT.ORA file being in use instead of SPFILE. I set DB_RECOVERY_FILE_DEST, DB_RECOVERY_DEST_SIZE after changing the DB mode to ARCHIVELOG, but DB was restarted by somebody else, and as the parameter changing was NOT PERMANENT, it rollback.
    LOG_ARCHIVE_DEST was set to d:\oradata\db with archivelog mode but db_recovery_file_dest and size was set to 0. Now here, I have no idea that whether archivelogs were not being backed up or deleted physically, but I guess that as log_archive_dest parameter is deprecated and mode is set to archivelog with no real ARCHIVELOG DESTINATION. Please correct me if I am wrong or totally wrong :-)
    I performed DELETED EXPIRED ARCHIVELOG ALL, and it deleted 49 EXPIRED objects.
    Now CROSSCHECK ARCHIVELOG ALL and LIST ARCHIVELOG ALL shows nothing.
    LIST BACKUP OF ARCHIVELOG ALL has of course those 49 archivelog gap.
    Could you please tell the impacts of those 49 missing archivelogs. Retention policy is set to 14 days. I mean the risk is for 14 days right? As anyhow, the older backups are being DELETED according to retention policy of RMAN.

  • Rollback with rman level 0

    Hello all,
    I am very new to oracle and i wanted to know if i have a full level 0 rman backup (with archive log ) that i have taken today(2/9/2012 13:00 pm cst)....
    and now the questions is...
    is there anyway possible or is oracle is capable of rolling me back to lets say 2 days back with just my backup i have taken 2 days back??...but keep in mind i only have level 0 backup that i took today... lets say i am on version 11.2.0.1
    From my understanding of rman, i can only go back up until 2/9/2012 13:00 pm cst ?? or can i go back to lets says 2/7/2012 13:00 pm cst ??

    In your case RMAN alone cannot rewind back data. You would need to have older backups that the point in time needed and/or to have flasback database enabled (http://docs.oracle.com/cd/E11882_01/backup.112/e10642/flashdb.htm#BRADV180).

  • Restore incremental backup with rman

    Dear Friends
    can u tell me how to restore an incremental backup with rman? i backup my rman with statement below :
    1. backup full database format '/oracle/PRD/sapbackup/%U';
    the results was :
    -rw-r----- 1 oraprd dba 19006996480 Jun 10 12:08 0ojiit4n_1_1
    -rw-r----- 1 oraprd dba 12746752 Jun 10 12:08 0pjiiu6b_1_1
    2. after that i do incremental backup :
    backup incremental level 1 cumulative database format '/oracle/PRD/sapbackup/%U';
    the results was :
    -rw-r----- 1 oraprd dba 173400064 Jun 10 13:44 0ujij2k0_1_1
    -rw-r----- 1 oraprd dba 12746752 Jun 10 13:44 0vjij3qc_1_1
    what statement i need to run for restore the incremental backup?

    run{
    ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
    RESTORE DATABASE;
    RECOVER DATABASE;
    The above command will restore your database from the last good RMAN backup. Your last backup is incremental level backup as you posted. The above command will fullfill your requirements

  • Tablespace level backup using data pump

    Hi,
    Im using 10.2.0.4 on RHEL 4,
    I have one doubt, can we take a tablespace level backup using data pump,
    bt i dnt wnt to use it for transportable tablespace.
    thanks.

    Yes, you can only for the tables in that tablespace only.
    Use the TABLESPACES option to export list of tablespaces.*here all the tables in that tablespaces will be exported*.
    and you must have the EXP_FULL_DATABASE role to use tablespace mode.
    Have a look at this,
    http://stanford.edu/dept/itss/docs/oracle/10g/server.101/b10825/dp_export.htm#i1007519
    Thanks
    Edited by: Cj on Dec 12, 2010 11:48 PM

  • RMAN Automatic backup/recovery with oracle fail safe, windows cluster

    Hello,
    I have question,
    1) Whether it is possible to do "RMAN Automatic Backup and recovery" in environment as ?
    Environment: -
    a. Windows clustering with windows server 2003 Enterprise Edition R2 (Two Node Clustering)
    b. Shared disk ( RAID )
    c. Oracle 10g standard edition one
    d. Oracle fail safe v3.3.3 (for redundancy)
    Here we have single oracle instance operating on single database whose files are located on shared disk.
    2) If answer to above question is yes please specify if there is some good documentation to it.
    Any help regarding this will be greatly appreciated.
    Thanks in advance,
    Rahul

    You just need to make sure that the RMAN scripts are always able to connect to the target database instance whether instance runs on cluster node 1 or cluster node 2
    here, If oracle services(resources) will shift from Node1 to Node2 (due to media or any failure) during RMAN Backup then there will be break in connection, will it destroy my backup or will it get started automatically without any harm?
    and also I want to know,
    Do we need to setup another server which will have RMAN backup script running?

  • RMAN Backup with ASM and Standby in place

    Hi All,
    We are planning to upgrade our database from 10.2.0.2 to 10.2.0.3. We have ASM as storage on primary and phisical standby is in place.
    I want to make a cut of point for backup, i.e if I restore till that poit on primary standby should continue to work. I need not create standby.
    We are using rman for backup and primary db uses asm for data,archive and redolog storage.
    I have a online complete db backup at 12:00PM. At say 6:00pm i take primary down and apply all archives on standby and cancel recovery on standby along with taking it down. On primary i mount db and take controlfile backup and all archive log backup using rman.
    Now i continue with upgrade and many more changes on primary. I will not touch standby. We decide to revertback at 10pm on primary. If I wan to return back to 6:00pm state on primary and standby.
    I believe I will restore controlfile backup taken at 6:00pm with db in mount phase. Restore dbfiles from online backup and recover using archives.
    My question is do i need to open with resetlogs? Then I will lose my standby which was up to date at 6:00pm. Can I not backup redofiles at 6:00pm with db in mount phase and i restore them then i need not open with reset logs and my stnadby will continue from that point.
    Please guide me..Is there way to backup redologs when db is in mount phase and using asm for storage using rman.

    There are quite a bunch of steps involved and you need to do some documentation reading.
    Do you plan to create the test database on the same machine or different RAC system?
    Which version of Oracle are you using? What OS?
    There is plenty of information on the web if you search for "duplicate database RAC ASM". Did you try?

Maybe you are looking for

  • The form could not be certified, possibly because of your password timeout policy

    I am obtaining an error while attempting to distribute a form signed with a digital ID. I can't find any documentation or discussion threads to resolve the problem. Specifically, while attempting to distribute the signed form in Adobe Acrobat X, the

  • How many computers can I download this to?

    Hi there, hope you are all doing well. I'm just wondering if anyone can tell me how many computers I can download one copy of Dreamweaver to? Thanks so much!

  • Alternating background color for BC4J DataTable?

    I am surprised that I couldn't see an example of this anywhere. The documentation in the bc4j.css indicates that it is possible to "enable the alternating colors feature for the HTML Table Control", I would think this is just a checkbox somewhere. Ca

  • Cursor/Track Pad issue (MacBook: OS X 10.5.8)

    I don't know if this is a virus/trojan/spyware/malware, but in the last week of so my MacBook (2009) has developed some serious cursor/trackpad issues: -It will either take many MANY left clicks to select an item, open a link or close a window OR -If

  • Activate a field VTTK-/BEV1/RPFLGNR in screen VT01N

    Dear guru's, As per the client requirement i would like to activate the field /BEV1/RPFLGNR of VTTK table in VT01N  screen for entry. kindly help us in this regard. Regards, Abdul Rahim