If RMAN incremental level-1 backup fails...

Hi there,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Best regards

Hi,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Check the V$BACKUP_SET dictionary to confirm whether the last backup has been touched by data dictionary. If the failed incremental backup is picked up then the previous incremental backup will be required in case of the next DIFFERENTIAL INCREMENTAL LEVEL 1 backup.
But to be on safe side , it is recommended you take a LEVEL 01 CUMILATIVE INCREMENTAL backup from Level 0 till date. So that the recovery process can go through even  if the previous backup is not valid.
Thanks &
Best Regards

Similar Messages

  • Block Media Recovery and RMAN Incremental Level 1 backup

    Hi
    I have read somewhere that Block Media Recovery will not work if a database is backed up using rman incremental 1. Is this true, and if so is there a work around?
    I cannot seem to find this in oralce's documentation.
    Regards
    Me

    Hi,
    1) is Full Backup = Incremental level 0 backup?
    Yes
    2) When oralce say BMR does not work with incremental, will it work in the case I put forward. becuase Im doing an incremental 0...
    But does you have the Archive logs available.. ?? If yes then it will Support.
    3) Im my case will BMR work...that is use Incr level 0 on Sunday and then use archive logs for mon, tues etc
    Yes, I believe.
    @Hemanth .. am I right.. ?? Wait for your inputs...
    - Pavan Kumar N

  • Backup RMAN Incremental Level 1 without Level 0 - 10gR2

    Hi,
    I'm a bit confused after some tests.
    The Question: It's mandatory to perform backup incremental level 0 before the level 1 using Oracle 10gR2 ?
    On Oracle 11.2 it's mandatory but on Oracle 10.2.0.5 I don't know.
    Test on 11.2. If doesn't exists level 0 rman take care about it and perform automaticaly level 0 before level1
    RMAN> backup incremental level 1 database;
    Starting backup at 29-APR-11
    using channel ORA_DISK_1
    no parent backup or copy of datafile 1 found
    channel ORA_DISK_1: starting incremental level 0 datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    ...Docs said:
    Incremental backups capture only those blocks that change between backups in each datafile.
    In a typical incremental backup strategy, a level 0 incremental backup is used as a starting point. A level 0 backup captures all blocks in the datafile.
    So, on Oracle 10.2.0.5 this not happen like on 11.2:
    Perfoming backup level 1 without level 0:
    RMAN> list backup;
    RMAN> backup incremental level 1 database;
    Starting backup at 29-APR-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting incremental level 1 datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=+DG_ORCL/db10g/datafile/system.260.749756975
    channel ORA_DISK_1: starting piece 1 at 29-APR-11
    channel ORA_DISK_1: finished piece 1 at 29-APR-11
    piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
    channel ORA_DISK_1: starting incremental level 1 datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current control file in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 29-APR-11
    channel ORA_DISK_1: finished piece 1 at 29-APR-11
    piece handle=+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449 tag=TAG20110429T190340 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
    Finished backup at 29-APR-11
    RMAN> backup archivelog all delete input;
    Starting backup at 29-APR-11
    current log archived
    using channel ORA_DISK_1
    Finished backup at 29-APR-11
    RMAN> shutdown abort;
    Oracle instance shut downDelete all files on ASM (except SPFILE).
    ASMCMD> cd +DG_ORCL/DB10g
    ASMCMD> ls
    PARAMETERFILE/
    spfiledb10g.oraSo, let's perfom restore of database
    oracle@butao:/home/oracle> rman target /
    Recovery Manager: Release 10.2.0.5.0 - Production on Fri Apr 29 19:06:52 2011
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount
    Oracle instance started
    Total System Global Area     293601280 bytes
    Fixed Size                     2095872 bytes
    Variable Size                 92275968 bytes
    Database Buffers             192937984 bytes
    Redo Buffers                   6291456 bytes
    RMAN> restore controlfile from '+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449';
    Starting restore at 29-APR-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
    output filename=+DG_ORCL/db10g/controlfile/current.263.749761699
    output filename=+DG_FRA/db10g/controlfile/current.263.749761699
    Finished restore at 29-APR-11
    RMAN> startup mount
    database is already started
    database mounted
    released channel: ORA_DISK_1
    RMAN> restore database;
    Starting restore at 29-APR-11
    Starting implicit crosscheck backup at 29-APR-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 29-APR-11
    Starting implicit crosscheck copy at 29-APR-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 29-APR-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/ncsnn1_TAG20110429T190340_0.262.749761449
    File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/annnf0_TAG20110429T190442_0.264.749761485
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to +DG_ORCL/db10g/datafile/system.260.749756975
    restoring datafile 00002 to +DG_ORCL/db10g/datafile/undotbs1.261.749757085
    restoring datafile 00003 to +DG_ORCL/db10g/datafile/sysaux.262.749757095
    restoring datafile 00004 to +DG_ORCL/db10g/datafile/users.264.749757107
    channel ORA_DISK_1: reading from backup piece +DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421
    channel ORA_DISK_1: restored backup piece 1
    piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:26
    Finished restore at 29-APR-11
    RMAN> recover database;
    Starting recover at 29-APR-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 27 is already on disk as file +DG_FRA/db10g/onlinelog/group_3.259.749756971
    archive log thread 1 sequence 28 is already on disk as file +DG_FRA/db10g/onlinelog/group_1.257.749756963
    archive log filename=+DG_FRA/db10g/onlinelog/group_3.259.749756971 thread=1 sequence=27
    archive log filename=+DG_FRA/db10g/onlinelog/group_1.257.749756963 thread=1 sequence=28
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 29-APR-11
    RMAN> alter database open resetlogs;
    database opened
    RMAN>See I don't need level 0 backup to restore level 1.
    Thanks,
    Levi Pereira

    Hi Gokhan,
    Thank you for point this.
    After spending a time studying about this I find out this:
    Your expanation apply only in Oracle 10gR1/R2.
    Because there is differences between RMAN Version 10gR1/R2 and 11gR1/R2 about Incremental Level 1 and this confuse me.
    Oracle 10gR1/R2 run only one backup incremental level 1 even if level 0 not exists .
    Oracle 11gR1/R2 run two backups incremental if level 0 not exists. i.e level 0 first and after that level 1.
    Oracle 10gR2
    If no level 0 backup is available, then the behavior depends upon the compatibility mode setting. If compatibility is >=10.0.0, RMAN copies all blocks changed since the file was created, and stores the results as a level 1 backup. In other words, the SCN at the time the incremental backup is taken is the file creation SCN.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm
    Thats means wich RMAN run level 0 with name level 1. (i.e: Only one Backup) This is confuse.
    Oracle 11gR1
    If no level 0 backup is available in either the current or parent incarnation, then the behavior varies with the compatibility mode setting. If compatibility is >=10.0.0, RMAN copies all blocks that have been changed since the file was created. Otherwise, RMAN behaves as it did in previous releases, by generating a level 0 backup.
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmcncpt.htm#BRADV89500
    Oracle 11gR2
    If no level 0 backup is available in either the current or parent incarnation, then the behavior varies with the compatibility mode setting. If compatibility is >=10.0.0, RMAN copies all blocks that have been changed since the file was created. Otherwise, RMAN generates a level 0 backup.
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV89500
    Thats means wich RMAN run (automatically) level 0 first after finish level 0 backup RMAN run level 1 backup (i.e Two Backups). This seems right.
    Regards,
    Levi Pereira

  • What is the right TAG for incremental level 1 backup?

    We have a sunday level 0 backup like this:
    run {
    backup as compressed backupset
    filesperset 1
         incremental level 0 database
         tag='LEVEL_0_BACKUP'
         include current controlfile
         plus archivelog delete input;
    SQL 'alter database backup controlfile to trace';
    And Monday to Saturday incremental level 1 backup as this:
    run {
    backup as compressed backupset
         incremental level 1 database
         tag='LEVEL_1_BACKUP'
         include current controlfile
         plus archivelog delete input;
    SQL 'alter database backup controlfile to trace';
    Those scripts existed a while ago. I wonder if level 1 tag should be same as level 0 so they can all combined together?
    Please kindly advice.

    849425 wrote:
    Thanks for all your response.
    What I think is with block change tracking enabled, is that the incremental should roll into the level 0 full backup?
    What makes you think that?  Block change tracking simply allows rman to avoid having to scan every block to see if it needs to be backed up.
    I've never heard of an incremental (level 1) "rolling into" a level 0.
    Recovery starts with restoring the files from a level 0.  Followed by restoring individual blocks from the Level 1.  Followed by applying changes from the archived redo.  Followed by (if necessary) applying changes from the online redo.
    As stated earlier, tags are just user-defined labels.  Use them however seems appropriate -- after fully understanding what they are and what they are not. User-specified tags are not even required. I'd be cautious about changing them in an already defined and running system.

  • Larger backups for cumulative incremental level 1 backups

    I am noticing some strange behaviour for backup of data files in the RMAN cumulative incremental level 1 backup for certain days. I would explain that with an elaboration- the cumulative backup sizes are around 2GB, 19GB, 19GB, 1GB for the dates of 10th Dec, 5th Dec, 3rd Dec and 28th Nov respectively.
    Can there be so much difference between the values of backup size for the RMAN cumulative incremental level 1 backup as they are fluctuating from 19GB->1GB?
    I hope, my question is clear.
    Please revert with the reply to my query.
    Regards

    975148 wrote:
    Thanks for your reply. Level 0 backup happened twice between 5th Dec and 10th Dec. I guess, a block which has changed multiple times would be backed up once with all the changes done in a backup on a particular day. The same changes should get reflected in the subsequent level 0 backup.
    Regards
    Yes, obviously any backup (of any kind, of any product) is only capable of backing up the state of things as they exist at the time of the backup.
    The recoverability of "intermediate" states (say a given block was modified 5 times between backups, the next backup only gets the 5th state of the block) is done by applying redo - archived or online, as is needed.
    So to make an example to replicate what you report
    Day 1 - backup level 0
    - block # 1 modified
    Day 2  - backup level 1 - backs up Block #1 - backup size 8k
    - block # 1 modified
    - block # 2 modified
    - block # 1 modified
    - block # 3 modified
    - block # 1 modified
    - block # 4 modified
    Day 3 - backup level 1 - backs up Blocks 1,2,3,4 - backup size 32k
    - block # 5 modified
    - block # 2 modified
    - block # 7 modified
    - block # 3 modified
    - block # 6 modified
    - block # 4 modified
    Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
    - block # 5 modified
    Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
    Day 6 - backup level 0 - all blocks - size ???
    - block # 3 modified
    Day 7 - backup level 1 - backs up block 3 - backup size 8 k

  • Rman incremental level 1 merge with level 0

    from my reading of the rman backup document, it seems the merger incremental level 1to level 0 for recover only apply to merge with image copy, not the backupset. Is that true? However, such backup scheme will create a huge backup image copy, almost fill up my assigned backup depository directory. Is the following script works as merging with level 0 ?
    {backup as compressed backupset incremental level 1 for recover of tag 'bk$LEVEL0' database;}
    It run without error and created a very small incr file size, but not sure it has the same meaning of "for recover of copy" as in other document.

    If that is true, why we need to create an incremental level 0 backupset as the base for recover? I have one compressed backupset level 0 at beginning, then incremental level 1 for recover. with the "recover of copy with tag", it seems to create a redundant full backup. Also Iam confused, The "recover of copy with tag" is actually an image copy of the full backupset or the image copy of the original database.
    My script as for full backup at beginning
    { backup as compressed backupset incremental level 0 cumulative device type disk tag 'Baanbk$LEVEL0' database; }
    then incremental
    { backup as compressed backupset incremental level 1 for recover of  tag 'Baanbk$LEVEL0' database; }
    Should I modify the full backupset script?

  • EM12c Create non-cumulative incremental (level 1) backups against target DB

    Is this not available? It appears that we can only create cumulative RMAN incremental backups through Cloud 12c (this is against an 11gR2 DB). Are non-cumulative incrementals no longer supported?

    When scheduling a backup through the wizard, the last step displays the RMAN script the wizard has generated for you. Have you tried clicking the 'Edit RMAN Script' and removing the word "cumulative" from the generated script?
    I run backups using scripts stored in the recovery catalog so I don't use the click-through backup wizard, but does it not result in a differential incremental backup if you edit the script?

  • Resume a failed RMAN incremental 0 cold backup to disk

    Linux x86-64 10.2.0.4
    I'm taking an incremental 0 backup to disk of a database that's mounted. I'm backing up the database to an NFS volume. I lost the NFS mount. Is there any way to resume a backup where it left off at? It complains "ORA-27038: created file already exists" if I restart it. RMAN can easily resume a restore. I don't have the time to redo the whole thing all again. The database is over 10TB. The target isn't up. Is there anything I could do?

    Hemant K Chitale wrote:
    I lost the NFS mount point, as in it was no longer mounted to the host. If it was any other scenario, I wouldn't be attempting to resume it.and
    I still have the previously restored files. I wouldn't be recieving "ORA-27038: created file already exists" otherwise. I am still confused.
    I guess that you are talking of a BACKUP not a RESTORE (unlike the sentence that says "previously restored files").I meant backup. I'm also doing a restore for another purpose, so it was on my mind. It was some sort of phsychological slip.
    >
    "The NFS mount point is no longer mounted.". So what happened to the files that did get written to the NFS mount point ? Did you copy them to tape before the NFS mount point got unmounted ? Or is the NFS server still up and running, with the partial backup intact on it, except that the remote mount is disabled ?
    We had a network problem and we lost the NFS mount. Most of the files are there, just not the whole database. I didn't copy them to tape. The whole purpose was to use the backup as a clone by manually recreating the controlfle, and pulling it into another ASM instance on another cluster. We first need to pull it out of the current ASM instance. The NFS volume was remounted, but my concern is being able to resume the backup from where it left off at.
    How about running
    BACKUP ... NOT BACKED UP SINCE TIME 'date_string'From the documentation : "This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up."I'll have to give that a try. It sounds promising.
    >
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

  • RMAN Incremental Lvl 0 backup vs Full Backup

    Hi all professionals,
    If my RMAN backup script did not specify the incremental backup strategy, what is the default strategy it would adopt?
    say for example: backup as compressed backup set database plus archive log delete input;
    Will it use full backup or lvl 0 incremental backup?
    There is a RMAN script (similar with the above) running as scheduled job daily and I will also use backup exec to backup the database to tape (manually scheduled to run for each time but not daily) at the same time.
    Will the scheduled daily rman script backup affect the scn of the backup using backup exec so that it could not be restore the tape backup using backup exec to a testing db as usual?
    (checked that backup exec also use rman script to backup but it uses incremental lvl 0)
    Welcome your professional comments and sharing.
    Thanks,
    Calvin
    Edited by: Calvin CS Ng on Aug 8, 2010 9:29 PM

    backup as compressed backup set database plus archive log delete input;
    Will it use full backup or lvl 0 incremental backup?
    It will be a full backup.
    There is a RMAN script (similar with the above) running as scheduled job daily and I will also use backup exec to backup the database to tape (manually scheduled to run for each time but not daily) at the same time.
    Will the scheduled daily rman script backup affect the scn of the backup using backup exec so that it could not be restore the tape backup using backup exec to a testing db as usual?There should be no impact on restore/recovery.
    Doc http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1011483 says:
    >
    The only difference between a level 0 incremental backup and a full backup is that a full backup is never included in an incremental strategy.

  • RMAN incremental

    Dears,
    Hi,
    sorry if i can not write English well,
    my database size(datafiles) is about 1.4 GB.
    i take RMAN incremental level 0 backup and size of output file is about 1.1 GB
    after this i insert on record to one table (for test change)
    and i take incremental level 1 backup and size of output file is about 1.1 GB(same level 0)
    but i think the level 1 just changed block and should be small than level 0.
    RMAN> backup incremental level 0 database FORMAT 'd:\rm\L0_%d_t%t_s%s_p%p';
    RMAN> backup incremental level 1 database FORMAT 'd:\rm\L1_%d_t%t_s%s_p%p';
    why size for level 0 and 1 is same?
    Best regards and thanks
    Hassan

    In theory, the L1 backup should be smaller as it should capture only changed blocks (it is not a requirement that you create a BCT file -- a BCT file helps speed up the incremental backup , it's presence or absence has no relation to the size of the L1 incremental backup).
    You need to determine if there were other, multiple, changes to the database that also occurred between the two backups.
    Hemant K Chitale

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

  • Incremental level backup

    If I take incremental level 0 backup on Monday, full database image copy backup on Tuesday, incremental level 1 on Wednesday and Incremental level 2 backup on Thursday;
    Can i do complete recovery on Friday by applying incremental level 1 & 2 backup on the image copy backup???

    Atiq wrote:
    If I take incremental level 0 backup on Monday, full database image copy backup on Tuesday, incremental level 1 on Wednesday and Incremental level 2 backup on Thursday;
    Can i do complete recovery on Friday by applying incremental level 1 & 2 backup on the image copy backup???There is no incremental level 2 backup in oracle, only level zero and level one. Or do you mean a second incremental level one?
    Your first incremental level 1 will have all the changes since the incremental level 0. The fact that you took an image copy will not be considered by that backup.
    was your image copy taken when the db was cleanly shut down? Did it include the control files?

  • Full (Level 0) backup to local/NFS disk

    I am new to SAP's BR*Tools, and need advice in configuring it to use RMAN.  
    1. My backups are to be written to a staging area on our SAN.
    2. What specific parameters do I need to configure in the initSID.sap file to achive Full (Level 0) backup to local/NFS disk - preferably using RMAN?
    3. I have successfully performed a Full (Level 0) backup without RMAN to local disk.  Also, I have successfully done an incremental (Level 1) backup using BRTools with RMAN.  I want to get BRTools + RMAN based Full (Level 0) backup to local/NFS disk.
    --VJ

    You need to set the values for the following.
    tape_address
    archive_copy_dir
    tape_size =
    backup_mode =
    backup_dev_type =
    backup_type =
    backup_root_dir
    volume_archive
    volume_backup
    tape_pos_cmd
    Cheers
    Shaji

  • Incremental Level n and Incremental Level n Cumulative

    Hello,
    Working on Oracle 10.2.0.3.0 on AIX 5.2. Taking backup through scripts using recovery catalog.
    (Incremental level 0 cumulative)
    RMAN> run {execute script cuml_level_0; }
    executing script: cuml_level_0
    Starting backup at 18-DEC-07
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=146 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=14 recid=13 stamp=641645002
    channel ORA_DISK_1: starting piece 1 at 18-DEC-07
    channel ORA_DISK_1: finished piece 1 at 18-DEC-07
    piece handle=/dbbkup/06j3teel_1_1 tag=TAG20071218T104332 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
    Finished backup at 18-DEC-07
    Starting backup at 18-DEC-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting incremental level 0 datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=/dbprod5/BACKUPTEST/BACKUPTEST/system01.dbf
    input datafile fno=00003 name=/dbprod5/BACKUPTEST/BACKUPTEST/sysaux01.dbf
    input datafile fno=00005 name=/dbprod5/BACKUPTEST/BACKUPTEST/example01.dbf
    input datafile fno=00002 name=/dbprod5/BACKUPTEST/BACKUPTEST/undotbs01.dbf
    input datafile fno=00004 name=/dbprod5/BACKUPTEST/BACKUPTEST/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 18-DEC-07
    channel ORA_DISK_1: finished piece 1 at 18-DEC-07
    piece handle=/flash_recovery/BACKUPTEST/backupset/2007_12_18/o1_mf_nnnd0_TAG200712
    18T104351_3pgqjy4b_.bkp tag=TAG20071218T104351 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
    Finished backup at 18-DEC-07
    Starting backup at 18-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=15 recid=14 stamp=641645163
    channel ORA_DISK_1: starting piece 1 at 18-DEC-07
    channel ORA_DISK_1: finished piece 1 at 18-DEC-07
    piece handle=/dbbkup/08j3tejt_1_1 tag=TAG20071218T104620 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    Finished backup at 18-DEC-07
    Starting Control File and SPFILE Autobackup at 18-DEC-07
    piece handle=/flash_recovery/BACKUPTEST/autobackup/2007_12_18/o1_mf_s_641645187_3p
    gqoo2m_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 18-DEC-07(Incremental level 0 backup)
    RMAN> run {execute script incr_level_0;}
    executing script: incr_level_0
    Starting backup at 18-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=14 recid=13 stamp=641645002
    input archive log thread=1 sequence=15 recid=14 stamp=641645163
    input archive log thread=1 sequence=16 recid=15 stamp=641645676
    channel ORA_DISK_1: starting piece 1 at 18-DEC-07
    channel ORA_DISK_1: finished piece 1 at 18-DEC-07
    piece handle=/dbbkup/0aj3tf3h_1_1 tag=TAG20071218T105440 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:08
    Finished backup at 18-DEC-07
    Starting backup at 18-DEC-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting incremental level 0 datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=/dbprod5/BACKUPTEST/BACKUPTEST/system01.dbf
    input datafile fno=00003 name=/dbprod5/BACKUPTEST/BACKUPTEST/sysaux01.dbf
    input datafile fno=00005 name=/dbprod5/BACKUPTEST/BACKUPTEST/example01.dbf
    input datafile fno=00002 name=/dbprod5/BACKUPTEST/BACKUPTEST/undotbs01.dbf
    input datafile fno=00004 name=/dbprod5/BACKUPTEST/BACKUPTEST/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 18-DEC-07
    channel ORA_DISK_1: finished piece 1 at 18-DEC-07
    piece handle=/flash_recovery/BACKUPTEST/backupset/2007_12_18/o1_mf_nnnd0_TAG200712
    18T105449_3pgr5d2l_.bkp tag=TAG20071218T105449 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:58
    Finished backup at 18-DEC-07
    Starting backup at 18-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=17 recid=16 stamp=641645812
    channel ORA_DISK_1: starting piece 1 at 18-DEC-07
    channel ORA_DISK_1: finished piece 1 at 18-DEC-07
    piece handle=/dbbkup/0cj3tf7r_1_1 tag=TAG20071218T105659 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    Finished backup at 18-DEC-07
    Starting Control File and SPFILE Autobackup at 18-DEC-07
    piece handle=/flash_recovery/BACKUPTEST/autobackup/2007_12_18/o1_mf_s_641645826_3p
    gr9m7x_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 18-DEC-07There are certain differences. Any comments.
    Thank you,
    Adith

    I think you are taking backup with backup plus archive log,archive log backup does the
    following steps chronologically
    1. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.
    2. Runs BACKUP ARCHIVELOG ALL. Note that if backup  
       optimization is enabled, then RMAN skips logs that it
       has already backed up to the specified device.
    3. Backs up the rest of the files specified in BACKUP
       command.
    4. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command again
       cuase right now it will  Backs up any remaining
       archived logsgenerated during the backup.
    SQL> archive log list
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     83
    Next log sequence to archive   85
    Current log sequence           85
    You can see next log sequence to be archived is 85
    RMAN> backup database plus archivelog
    2> ;
    Starting backup at 26-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=85 recid=89 stamp=642354039
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
    F_ANNNN_TAG20071226T154039_3Q4CX955_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
    Finished backup at 26-DEC-07
    Starting backup at 26-DEC-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF
    input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.DBF
    input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.DBF
    input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NNNDF_TAG20071226T154044_3Q4CXG9X_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:58
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NCSNF_TAG20071226T154044_3Q4CZ8GR_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 26-DEC-07
    Starting backup at 26-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=86 recid=90 stamp=642354108
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_ANNNN_TAG20071226T154148_3Q4CZFVO_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    Finished backup at 26-DEC-07
    SQL> archive log list
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     85
    Next log sequence to archive   87
    Current log sequence           87
    RMAN> backup database plus archivelog
    2> ;
    Starting backup at 26-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=85 recid=89 stamp=642354039
    input archive log thread=1 sequence=86 recid=90 stamp=642354108
    input archive log thread=1 sequence=87 recid=91 stamp=642354774
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
    F_ANNNN_TAG20071226T155255_3Q4DNBSM_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
    Finished backup at 26-DEC-07
    Starting backup at 26-DEC-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF
    input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.DBF
    input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.DBF
    input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
    F_NNNDF_TAG20071226T155302_3Q4DNJ28_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
    F_NCSNF_TAG20071226T155302_3Q4DOYL6_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 26-DEC-07
    Starting backup at 26-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=88 recid=92 stamp=642354835
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
    F_ANNNN_TAG20071226T155355_3Q4DP4SQ_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    Finished backup at 26-DEC-07
    RMAN>
    RMAN> show backup optimization
    2> ;
    RMAN configuration parameters are:
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    RMAN> configure backup optimization on
    2> ;
    new RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters are successfully stored
    SQL> archive log list
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     87
    Next log sequence to archive   89
    Current log sequence           89
    RMAN> backup database plus archivelog
    2> ;
    Starting backup at 26-DEC-07
    current log archived
    using channel ORA_DISK_1
    skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_85_3Q4CX5XS_.ARC; already backed up 2 time(s)
    skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_86_3Q4CZCZ1_.ARC; already backed up 2 time(s)
    skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_87_3Q4DN5MZ_.ARC; already backed up 1 time(s)
    skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_88_3Q4DP351_.ARC; already backed up 1 time(s)
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=89 recid=93 stamp=642355243
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_ANNNN_TAG20071226T160049_3Q4F3GYM_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:09
    Finished backup at 26-DEC-07
    Starting backup at 26-DEC-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF
    input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.DBF
    input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.DBF
    input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NNNDF_TAG20071226T160111_3Q4F3ZXF_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NCSNF_TAG20071226T160111_3Q4F69NO_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:06
    Finished backup at 26-DEC-07
    Starting backup at 26-DEC-07
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=90 recid=94 stamp=642355360
    channel ORA_DISK_1: starting piece 1 at 26-DEC-07
    channel ORA_DISK_1: finished piece 1 at 26-DEC-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_ANNNN_TAG20071226T160240_3Q4F6L09_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 26-DEC-07
    RMAN>Khurram

  • Difference between Full backup and lncremental level 0 backup

    Hi,
    What is the difference between Full backup and lncremental level 0 backup?
    what I understand is:
    Actually incremental backup backups all the block containing data and skips the blocks that are unused.
    Similarly full backup backups all the blocks containing data.(does it skip unused blocks ?????).
    The only difference that I feel is that the level 0 backup is recorded as an incremental backup in the RMAN repository, so it can be used as the parent for a level 1 backup where Full database backup is not recorded in the Rman respository and cannot be used as parent for level 1 backup.
    (if you still feel you have some more points to share regarding the difference between backups, I request to share with me)
    so my question here is
    Can we use Incremental level 0 backup for full database recovery. Else is there any compulsion like we must only use full database backup for full database recovery?
    can anyone throw light on this
    with regards;
    Boo

    nowhere in this thread we talked about the image copies as we are only talking about the incremental backup.
    The word "always" has a meaning. If you now wish to say, "well, RMAN will mostly use a level 0 or full backup, except when there are image copies around" then the word "always" doesn't fit your newly-revised description. That would make it an inappropriate word to use. And indeed, it's a factually wrong word to use.
    If you want to get really picky about it, incidentally, the words 'datafile copy' appear in a post from me at Aug 4, 2007 6:03 PM whereas your post (in which the "always" word was used) only appears Aug 4, 2007 8:32 PM -a full 2 and a half hours (and and two posts) AFTER the concept of image copies had been mentioned.
    But regardless of times: you can't just pretend image copies don't exist just because they haven't been mentioned so far in a thread. If you post "this is the way something ALWAYS works", you'd better be completely right about it, because "ALWAYS" is a big word. And there's no grey about this: either "always" is right, or it's wrong. And in this case, it's wrong: there are many times when RMAN will not do what you baldly asserted it would do. Image copies aren't some rare, exotic beast, either... so the occasions when your 'rule' breaks down are many and common.
    until now I was simply beliving in what Oracle docs and metalink notes says
    Try not to do that. Because you will fall into error after error if you do. Metalink is not the Holy Gospel of Oracle. Testing is, and it's because I've been testing this stuff since 1999 I will, on this occasion, decline your kind invitation to do "a small test". Been there, done that.
    All of which leaves us discussing things that are of no relevance to the original poster, and I have no desire to take the thread off into silly areas of dispute. So I will leave it there, and I have nothing further to say on the matter. RMAN does what it does, and what it does is not what you said it would do. End of story.

Maybe you are looking for