DATABASE INCREMENTAL LEVEL 0 BACKUP

Hello experts,

I use 11 GR 2 archivelog. We do full backup every day (to other archivelog backup different 2 delete the entry in the middle of the day, will be completed), connected to the Rman catalog. We would change (progressively) additional. If my first step is change 0 backup full to incremental daily, I couldn t have any difference in my backup sets, a part of the automatic reset of the Bct file.  Is this correct?

Thank you and best regards.

Francesco

Block change tracking only applies to incremental backups level 1 (all blocks are still included in a level 0) and makes your level 1 execution faster backup.

Just read http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV90078 and I think you get the idea.

Concerning

AJ

Tags: Database

Similar Questions

  • Restore cumulative incremental level 0 and cumulative incremental level 1 backups on a new host (not available Archivelogs)

    Hi guys, I have a disaster to manage.


    Due to a shooting incident, I physically lost my Oracle database server. Fortunately, I was doing extra effective Cumulative weekly 0 my databases backups and daily incremental cumulative level 1 of my databases on an external hard drive.


    Now, I need to restore these backups on a new physical server. I don't have backups of the archivelogs.

    Data loss can be allowed in this scenario. I have backup of the control file and the spfile (controlfile autobackup is configured).


    How can I restore and recover my databases on the new server (with a different directory structure)? I do not use a recovery catalog.


    Thanks in advance


    Clamarion

    @Hemant K Collette

    I have good news! I was able to raestore and recover my database with almost no loss of data. I have a ws, helped by a DBA called J.P. Boileau. I did not use the Oracle Support solution because it was too complicated to deploy. That's what I did:

    1. I arrived the last RCS of my backup cumulative incremental level 1 thanks to a list backup command.

    2. then, I used the SNA to make a series until the SNA...

    3. Finally, I did a restore of database; recover the database; and alter database open resetlogs.

    It's the detailed output of a simulation testing of this solution:

    [oracle@cumulative ~] $. oraenv

    ORACLE_SID = [oracle]? ORCL

    ORACLE_HOME = [/ home/oracle]? /U01/app/Oracle/product/11.2.0/dbhome_1

    The Oracle base has been set on/u01/app/oracle

    [oracle@cumulative ~] target rman $ /.

    Recovery Manager: release 11.2.0.3.0 - Production on Thu Oct 3 09:12:30 2013

    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

    connected to the database target (not started)

    RMAN > startup mount;

    Oracle instance started

    mounted database

    Total System Global Area 835104768 bytes

    Bytes of size 2232960 fixed

    574623104 variable size bytes

    251658240 of database buffers bytes

    Redo buffers 6590464 bytes

    RMAN > catalogue start by ' / u01/backup ';

    From implicit overlapping backup 3 October 13

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

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 133 type device = DISK

    Cut 7 objects

    Implicit overlapping backup has completed 3 October 13

    Starting copy implied overlap in October 3, 13

    using channel ORA_DISK_1

    Copy of implicit cross ended up at October 3, 13

    the search for all files in the recovery area

    cataloging files...

    not cataloged files

    the search for all files that match the/u01/backup model

    List of unknown files from the database

    =====================================

    File name: /u01/backup/autobackup/o1_mf_s_827753589_94qxm5o3_.bkp

    File name: /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

    File name: /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

    Do you want to catalog the files above (enter YES or NO)? Yes

    cataloging files...

    cataloging done

    List of cataloged files

    =======================

    File name: /u01/backup/autobackup/o1_mf_s_827753589_94qxm5o3_.bkp

    File name: /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

    File name: /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

    RMAN > overlap backupset;

    using channel ORA_DISK_1

    verified backup item: found to be "EXPIRED".

    handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd0_TAG20130930T114816_94loqk4w_.BKP element of backup RECID = 1 STAMP = 827495297

    verified backup item: found to be "EXPIRED".

    handle=/U01/app/Oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495353_94losbfm_.BKP element of backup RECID = TONE 2 = 827495354

    verified backup item: found to be "EXPIRED".

    handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd1_TAG20130930T115510_94lp4h7v_.BKP element of backup RECID = STAMP 3 = 827495711

    verified backup item: found to be "EXPIRED".

    handle=/U01/app/Oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495755_94lp5w1f_.BKP element of backup RECID = STAMP 4 = 827495756

    verified backup item: found to be "EXPIRED".

    handle=/U01/app/Oracle/fast_recovery_area/ORCL/autobackup/2013_10_02/o1_mf_s_827749047_94qs58bo_.BKP backup RECID piece = 6 = 827749048 STAMP

    verified backup item: found to be "EXPIRED".

    handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.BKP element of backup RECID = STAMP 5 = 827748980

    "" element of verified backup: turned out to be "AVAILABLE"

    handle=/U01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.BKP element of backup RECID = STAMP 8 = 827831641

    verified backup item: found to be "EXPIRED".

    handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.BKP element of backup RECID = STAMP 7 = 827753553

    "" element of verified backup: turned out to be "AVAILABLE"

    handle=/U01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.BKP element of backup RECID = STAMP 9 = 827831641

    Cut 9 objects

    RMAN > list backup;

    List of backup sets

    ===================

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

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

    1 DISK of 1.06 G Incr 0 00:00:51 30-SEP-13

    BP key: 1 situation: EXPIRED compressed: NOT of Tag: TAG20130930T114816

    Part name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd0_TAG20130930T114816_94loqk4w_.bkp

    List of files to backup data value 1

    Name of file LV Type cash SNA cash time

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

    1 0 incr 1123837 /u01/app/oracle/oradata/orcl/system01.dbf 30-SEP-13

    2 0 1123837 /u01/app/oracle/oradata/orcl/sysaux01.dbf incr 30-SEP-13

    3 0 incr 1123837 /u01/app/oracle/oradata/orcl/undotbs01.dbf 30-SEP-13

    4 0 incr 1123837 /u01/app/oracle/oradata/orcl/users01.dbf 30-SEP-13

    5 0 incr 1123837 /u01/app/oracle/oradata/orcl/example01.dbf 30-SEP-13

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

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

    2 full 9.36 M DISC 01:00:00 30-SEP-13

    BP key: 2 location: EXPIRED compressed: NOT of Tag: TAG20130930T114913

    Part name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495353_94losbfm_.bkp

    SPFILE included: Modification Date: 30-SEP-13

    SPFILE db_unique_name: ORCL

    Control file included: cash SNA: 1123870 cash time: 30-SEP-13

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

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

    3 incr 1 DISK of 4.54 M 00:00:39 30-SEP-13

    BP key: 3 location: EXPIRED compressed: NOT of Tag: TAG20130930T115510

    Part name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd1_TAG20130930T115510_94lp4h7v_.bkp

    List of files of data in backup set 3

    Name of file LV Type cash SNA cash time

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

    1 1 incr 1124362 /u01/app/oracle/oradata/orcl/system01.dbf 30-SEP-13

    2 1 incr 1124362 /u01/app/oracle/oradata/orcl/sysaux01.dbf 30-SEP-13

    3 1 incr 1124362 /u01/app/oracle/oradata/orcl/undotbs01.dbf 30-SEP-13

    4 1 incr 1124362 /u01/app/oracle/oradata/orcl/users01.dbf 30-SEP-13

    5 1 incr 1124362 /u01/app/oracle/oradata/orcl/example01.dbf 30-SEP-13

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

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

    4 whole 9.36 M DISC 01:00:00 30-SEP-13

    BP key: 4 location: EXPIRED compressed: NOT of Tag: TAG20130930T115555

    Part name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495755_94lp5w1f_.bkp

    SPFILE included: Modification Date: 30-SEP-13

    SPFILE db_unique_name: ORCL

    Control file included: cash SNA: 1124391 cash time: 30-SEP-13

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

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

    6 whole 9.36 M DISK 00:00:01 2 October 13

    BP key: 6 location: EXPIRED compressed: NOT of Tag: TAG20131002T101727

    Part name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_10_02/o1_mf_s_827749047_94qs58bo_.bkp

    SPFILE included: Date modified: October 2, 13

    SPFILE db_unique_name: ORCL

    Control file included: cash SNA: 1177698 cash time: 2 October 13

    BS key Type LV size

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

    8 0 incr 1.06 G

    List of files to backup set of 8 data

    Name of file LV Type cash SNA cash time

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

    1 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/system01.dbf

    2 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

    3 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

    4 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/users01.dbf

    5 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/example01.dbf

    Backup the exemplary value of the backup set of 8 #1

    Time of accomplishment of the time Type compressed device Tag

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

    00:00:00 DISC 2 OCTOBER 13 NO. TAG20131002T101620

    The list of items to backup the save game 8 copy #1

    Name of the Key BP Pc # status element

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

    5 1 EXPIRED /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

    Backup the exemplary value no. 2 backup set of 8

    Time of accomplishment of the time Type compressed device Tag

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

    DISC 00:00:00 3 OCTOBER 13 NO. TAG20131002T101620

    The list of items to backup the save game 8 copy #2

    Name of the Key BP Pc # status element

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

    8 1 /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp AVAILABLE

    BS key Type LV size

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

    9 incr 1 9,20 M

    List of files to backup data value 9

    Name of file LV Type cash SNA cash time

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

    1 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/system01.dbf

    2 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

    3 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

    4 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/users01.dbf

    5 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/example01.dbf

    The exemplary value value 9 Backup #1 backup

    Time of accomplishment of the time Type compressed device Tag

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

    00:00:00 DISC 2 OCTOBER 13 NO. TAG20131002T113233

    List backup to backup the value 9 #1 copy items

    Name of the Key BP Pc # status element

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

    7 1 EXPIRED /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

    Backup the exemplary value no. 2 backup the value 9

    Time of accomplishment of the time Type compressed device Tag

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

    DISC 00:00:00 3 OCTOBER 13 NO. TAG20131002T113233

    List backup to backup the value 9 #2 copy items

    Name of the Key BP Pc # status element

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

    9 1 /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp AVAILABLE

    RMAN > run {}

    2 > until the SNA 1182056.

    3 > restore database;

    4 > restore database;

    {5 >}

    executing command: SET until clause

    From restoration to 3 October 13

    using channel ORA_DISK_1

    channel ORA_DISK_1: from the restore backup set data file

    channel ORA_DISK_1: specifying datafile (s) to restore from backup set

    channel ORA_DISK_1: restore datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf

    channel ORA_DISK_1: restore datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf

    channel ORA_DISK_1: restore datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf

    channel ORA_DISK_1: restore datafile 00004 in /u01/app/oracle/oradata/orcl/users01.dbf

    channel ORA_DISK_1: restore datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf

    channel ORA_DISK_1: backup /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp piece reading

    channel ORA_DISK_1: room handle=/u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp tag = TAG20131002T101620

    channel ORA_DISK_1: restored the backup part 1

    channel ORA_DISK_1: restore complete, duration: 00:00:47

    Restoration finished in October 3, 13

    From pick up to 3 October 13

    using channel ORA_DISK_1

    channel ORA_DISK_1: from additional data file from the restore backup set

    channel ORA_DISK_1: specifying datafile (s) to restore from backup set

    destination for the restoration of the data file 00001: /u01/app/oracle/oradata/orcl/system01.dbf

    destination for the restoration of the data file 00002: /u01/app/oracle/oradata/orcl/sysaux01.dbf

    destination for the restoration of the data file 00003: /u01/app/oracle/oradata/orcl/undotbs01.dbf

    destination for the restoration of the data file 00004: /u01/app/oracle/oradata/orcl/users01.dbf

    destination for the restoration of the data file 00005: /u01/app/oracle/oradata/orcl/example01.dbf

    channel ORA_DISK_1: backup /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp piece reading

    channel ORA_DISK_1: room handle=/u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp tag = TAG20131002T113233

    channel ORA_DISK_1: restored the backup part 1

    channel ORA_DISK_1: restore complete, duration: 00:00:07

    starting media recovery

    media recovery complete, duration: 00:00:01

    Finished recover to 3 October 13

    RMAN > alter database open resetlogs;

    open database

    RMAN >

    Thanks again for all your help and patience.

    Concerning

    Clamarion.

  • How to restore the Rman incremental level 0 backup if the SID is different?

    Hi Experts,
    I had a little problem with restore rman backup of level 0. I have backup rman for oracle 11.2.0.1.0 - 64 bit and restore the server to Test 11.2.0.1.0 - 64 bit.

    Problem:
    Sid = prd production server
    Sid = prderp test server

    Operating system is Oracle linux 5 on both servers.

    How to restore Rman if the SID is different?

    Hello

    Refer to this http://shivanandarao.wordpress.com/2012/04/19/duplicating-primary-database-to-a-new-host-without-connecting-to-the-primary-database-in-oracle-10g11g/

    You need to restore it under the same name as you have in the production and later change the dbname using the NEST.

    If you don't want to go with this method, then I suggest you to go with the method of double RMAN.

    http://www.Oracle-base.com/articles/11g/duplicate-database-using-RMAN-11gr2.php
    http://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmdupdb.htm

    rman target sys/@prod auxiliary sys/@tst
RMAN>duplicate target database to 'prderp' nofilenamecheck;

    Please close this Re: how to restore the Rman backup if the SID is different? wire by marking as replied.

  • Why the format does not work on my backup incremental level 1 the difference?

    I use following script to make a backup of difference incremental level 1.
    ------------------------------
    Run {}
    allocate channels ch1 disc type;
    Set order id "Monday_INC_1_df";
    backup as compressed backupset database incremental level 1
    format ' / opt/oracle/rman/bk/incr1_df_%d_%U'
    tag "Monday_INC_1_df".
    database more entered archivelog delete;
    output channel ch1.
    }
    -------------------------------

    According to this scenario, all the rman output files are placed in "/ opt/oracle/rman/bk / '...  And his label is 'Monday_INC_1_df'.

    But at the bottom of the newspaper, I find the archived log rman output files located in "/ opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02 / '. And his label is "TAG20141202T210529".
    Also, at the bottom of the newspaper, the output data files rman files was partly on the right path "/ opt/oracle/rman/bk / '. And it seems that the data files has been supported for 2 times. The second time datafile rman output files was badly located in the path "/ opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02 / '. And his label is "TAG20141202T215627".


    ================================================ Detail Log ===================================================================================
    channel ch1: compressed boot archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 1 sequence = 36706 RECID = 2773 STAMP = 865282473
    archived journal entry thread = 1 sequence = 36707 RECID = 2774 STAMP = 865282476
    archived journal entry thread = 1 sequence = 36708 RECID = 2775 STAMP = 865282478
    archived journal entry thread = 1 sequence = 36709 RECID = 2776 STAMP = 865282482
    archived journal thread = 1 sequence = 36710 entry RECID = STAMP 2777 = 865282486
    archived journal entry thread = 1 sequence = 36711 RECID = 2778 STAMP = 865285528
    channel ch1: starting piece 1 at 2014-12-02 21:56:20
    channel ch1: finished piece 1 at 2014-12-02 21:56:27
    piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02/o1_mf_annnn_TAG20141202T210529_b7vk8408_.bkp tag = TAG20141202T210529 comment = NONE
    channel ch1: complete set of backups, time: 00:00:07
    channel ch1: archived deletion or newspapers
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36706_b7vc98xc_.arc RECID archived log file = 2773 STAMP = 865282473
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36707_b7vc9cz7_.arc RECID archived log file = 2774 STAMP = 865282476
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36708_b7vc9gn1_.arc RECID archived log file = 2775 STAMP = 865282478
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36709_b7vc9l3f_.arc RECID archived log file = 2776 STAMP = 865282482
    RECID = STAMP 2777 = 865282486 name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36710_b7vc9plj_.arc archived log file
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36711_b7vg8qz5_.arc RECID archived log file = 2778 STAMP = 865285528
    A backup over the 2014-12-02 21:56:27


    From backup 2014-12-02 21:56:27
    channel ch1: from compressed data file backup set incremental level 1
    channel ch1: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=/opt/oracle/oradata/test/undotbs01.dbf 00003
    Enter a number of file datafile = 00005 name=/opt/oracle/oradata/test/hp01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/cmtspace01.dbf 00035
    Enter a number of file datafile = name=/opt/oracle/oradata/test/sysaux01.dbf 00002
    Enter a number of file datafile = 00001 name=/opt/oracle/oradata/test/system01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/users01.dbf 00004
    channel ch1: starting piece 1 at 2014-12-02 21:56:28
    channel ch1: finished piece 1 at 2014-12-02 23:48:06
    piece handle tag = / opt/oracle/rman/bk/incr1_df_TEST_1gpp6gcc_1_1 MONDAY_INC_1_DF = comment = NONE
    channel ch1: complete set of backups, time: 01:51:38
    channel ch1: from compressed data file backup set incremental level 1
    channel ch1: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=/opt/oracle/oradata/test/undotbs01.dbf 00003
    Enter a number of file datafile = 00005 name=/opt/oracle/oradata/test/hp01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/cmtspace01.dbf 00035
    Enter a number of file datafile = name=/opt/oracle/oradata/test/sysaux01.dbf 00002
    Enter a number of file datafile = 00001 name=/opt/oracle/oradata/test/system01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/users01.dbf 00004
    channel ch1: starting piece 1 at 2014-12-02 23:48:07
    channel ch1: finished piece 1 at 2014-12-03 01:17:22
    piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02/o1_mf_nnnd1_TAG20141202T215627_b7vqsq8y_.bkp tag = TAG20141202T215627 comment = NONE
    channel ch1: complete set of backups, time: 01:29:15
    A backup over the 2014-12-03 01:17:22

    From backup 2014-12-03 01:17:23
    Current archived log
    channel ch1: compressed boot archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 1 sequence = 36712 RECID = 2779 STAMP = 865288890
    archived journal entry thread = 1 sequence = 36713 RECID = 2780 STAMP = 865288965
    archived journal entry thread = 1 sequence = 36714 RECID = 2781 STAMP = 865288971
    channel ch1: starting piece 1 at 2014-12-03 01:17:24
    channel ch1: finished piece 1 at 2014-12-03 01:17:49
    piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_03/o1_mf_annnn_TAG20141203T011723_b7vx145d_.bkp tag = TAG20141203T011723 comment = NONE
    channel ch1: complete set of backups, time: 00:00:25
    channel ch1: archived deletion or newspapers
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36712_b7vkkts7_.arc RECID archived log file = 2779 STAMP = 865288890
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36713_b7vkn5v0_.arc RECID archived log file = 2780 STAMP = 865288965
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36714_b7vkncv2_.arc RECID archived log file = 2781 STAMP = 865288971

    =============================================================================================================


    When I here is the backup incremental level 0, everything seems good.

    ----------------------------------
    Run {}
    allocate channels ch1 disc type;
    Set order id "Sunday_INC_0";
    backup incremental level 0 compressed backupset
    format ' / opt/oracle/rman/bk/incr0_%d_%U'
    tag "Sunday_INC_0".
    database more entered archivelog delete;
    output channel ch1.
    }
    --------------------------------

    But why my backup of difference in level 1 increntmental would not have good correct rman output path?


    You have specified the keyword 'database' twice in the backup command.  If execution is in the specified format, the second with the default format (to the FRA)

    Hemant K Collette

  • RMAN backup incremental level 1 without level 0-10 gr 2

    Hello

    I'm a bit confused after a few tries.

    The issue: It is mandatory to perform incremental level 0 backup before level 1 using Oracle 10 g 2?

    On Oracle 11.2 is mandatory, but I don't know about Oracle 10.2.0.5.

    11.2 test. If there is no level 0 rman take care on this subject and automatically perform 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 blocks that change between backups in each data file.
    In a typical incremental backup strategy, an incremental backup of level 0 is used as a starting point. A level 0 backup captures all the blocks in the data file.

    So, on Oracle 10.2.0.5 happens not like 11.2:

    Parade level 1 without level 0 backup:
    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 down
    Delete all (except SPFILE) ASM files.
    ASMCMD> cd +DG_ORCL/DB10g
ASMCMD> ls
PARAMETERFILE/
spfiledb10g.ora
    So we will perfom a database restore
    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 that I don't need level 0 backup to restore the level 1.

    Thank you
    Levi Pereira

    Levi,

    Please visit: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm

    If no level 0 backup is available, then the behavior depends on the setting of compatibility mode. If compatibility is > = 10.0.0, copies all blocks changed since the file was created RMAN and stores the results as a level 1 backup. In other words, the CPN at the time the incremental backup is taken is the creation of SCN file. If compatibility<10.0.0, rman="" generates="" a="" level="" 0="" backup="" of="" the="" file="" contents="" at="" the="" time="" of="" the="" backup,="" to="" be="" consistent="" with="" the="" behavior="" in="" previous="">

    Same info is here:

    http://www.Pythian.com/news/287/level-1-incremental-backup-in-Oracle-10G/

    Concerning

    Grosbois

  • Backup incremental level 2,3,4 RMAN.

    Hello guys,.

    Can someone let me know what is the meaning / usage of incremental backup of level 2,3,4.

    Kind regards.

    Wikipedia can have an easy to understand the reason for several additional levels:

    A backup of level 1 decision Monday would only include changes made since Sunday. A backup of level 2 decision Tuesday would only include changes made since Monday. A backup of level 3 Wednesday would only include changes made since Tuesday. If a level 2 backup taken Thursday, it would include all changes made since Monday because Monday was the most recent level n - 1 backup.

    https://en.Wikipedia.org/wiki/Incremental_backup

    What is RMAN?

    The Oracle documentation refers only to additional 0 year 1. What I understand, RMAN never supported incremental backups multilevel at 3 levels (0-4). Apparently, people often had trouble understanding the logic for levels 3 and 4. RMAN provides the clause 'cascading', which also existed in 9i and is usually an easier to understand the backup strategy. RMAN also provides or has provided an option to perform incremental backups cumulative at level 1 or higher. For simplicity, the la documentation documentation since 10 g mentions only level 0 only a 1 an other levels is deprecated.

    BACKUP INCREMENTIELLE from LEVEL 1 (differential by default, changes made since the last level 0 or 1)

    BACKUP INCREMENTIELLE LEVEL 1 CUMULATIVE (changes since the last last level 0)

    Below some info from http://docs.oracle.com/cd/E11882_01/backup.112/e10643/obs_comm.htm#RCMRF910

    RMAN version 10.0.1: levels other than 0 and 1 are deprecated.

    If you make an additional workforce 1 backup, incremental or cumulative, and there is no previous level 0, RMAN automatically performs an incremental backup of level 0. BTW, a full backup is identical to a level 0 incremental backup but excluded a strategy of backup incremental level.

  • Cumulative level 1 backup and redundancy of information

    My understanding of Cumulative level 1 - backups all the block changed since last level 0 backups and also double level 1 incremental copies, if we missed any level 1 differential before running the level 1 cumulative backup.

    Having said that I fell on the underside of documentation in Oracle.

    Suppose a case where REDUNDANCY is 1 . You run a backup of level 0 at noon Monday, a level 1 cumulative backup on Tuesday and Wednesday at noon and a backup of level 0 at noon Thursday. Immediately after each daily backup, you run a DELETE OBSOLETE . Wednesday DELETE command does not remove the level 1 of the Tuesday backup because the backup is not redundant: the level 1 of Tuesday backup could be used to recover the level 0 backup Monday for a duration between Tuesday noon and Wednesday noon. However, the DELETE command Thursday removes the previous level 0 and level 1 backups.

    Can someone explain to me why killing level 1 backup needed clarification? When we have a backup of the sea element that has backup KILLS (e i, which has backup LUN)

    to recover the database so I think that a single backup item is needed Wednesday.

    Please correct me if I'm wrong. Sorry for my bad English, if you find any grammatical error

    Also put me as what will contain the element of KILLING level 1 cumulative backup

    for sample data of level 0 kills more than Monday morning and data MIDI Mar

    Thank you



    Thank you


    2638616 wrote:

    My understanding of Cumulative level 1 - backups all the block changed since last level 0 backups and also double level 1 incremental copies, if we missed any level 1 differential before running the level 1 cumulative backup.

    Having said that I fell on the underside of documentation in Oracle.

    Assume a case in which REDUNDANCY is 1 . You run a backup of level 0 at noon Monday, a level 1 cumulative backup on Tuesday and Wednesday at noon and a backup of level 0 at noon Thursday. Immediately after each daily backup, you run a DELETE OBSOLETE . Wednesday DELETE command does not remove the level 1 of the Tuesday backup because the backup is not redundant: the level 1 of Tuesday backup could be used to recover the level 0 backup Monday for a duration between Tuesday noon and Wednesday noon. However, the DELETE command Thursday removes the previous level 0 and level 1 backups.

    Can someone explain to me why killing level 1 backup needed clarification? When we have a backup of the sea element that has backup KILLS (e i, which has backup LUN)

    to recover the database so I think that a single backup item is needed Wednesday.

    Please correct me if I'm wrong. Sorry for my bad English, if you find any grammatical error

    Also put me as what will contain the element of KILLING level 1 cumulative backup

    for sample data of level 0 kills more than Monday morning and data MIDI Mar

    Thank you

    Thank you

    Also put me as what will contain the element of KILLING level 1 cumulative backup

    for example Monday level 0 data more Tuesday morning as well as MIDI data Mar


    No backup of level 1 will contain nothing of the previous level 0 backup. First level 1 (no matter the cumulative or differential) will contain only the data blocks that have changed since the previous level 0.  Backups.will all new 1 cumulative level contain only data blocks that have changed since the previous level 0.

    And if you think a little about it, which will answer any other questions.

  • duplicate/clone database recovery failed, but backup total available (ORA-19505, ORA-17503)

    Hello

    I'm 11 GR 2. I ran a duplicate of RMAN database ABCD01P with the simple script:

    DUPLICATE THE TARGET DATABASE TO "TESTBKP' OF THE ACTIVE DATABASE.

    It ran fine for about 3 hours and ended in failure, after all my 175 data files

    have been copied to the destination host, when you start to recover. The log shows:

    ...

    content of Script memory:

    {

    until the SNA 607608188039.

    retrieve the archivelog deletion of database clone;

    }

    ...

    destination for the restoration of the data file 00009: +DATAF/testbkp/datafile/ab11_lob.435.847475901

    aux1 channel: reading of the element of backup +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021

    aux2 channel: from additional data file from the restore backup set

    aux2 channel: specifying datafile (s) to restore from backup set

    ...

    and then failed with:

    ORA-19870: error while restoring the backup +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021 piece

    ORA-19505: impossible to identify the file "+ FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021".

    ORA-17503: ksfdopn:2 could not open the file +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021

    I do not understand because this file it says it could not identify or open exists and is present in my FRA...

    (this backup from an incremental backup, updated full and the first one I did on the source DB one hour before

    -INCREMENTAL LEVEL BACKUP 1 TO RETRIEVE THE COPY WITH THE TAG... DATABASE PLUS ARCHIVELOG...-)

    Any idea?

    Thank you very much...

    SEB

    Hi Seb,

    I've seen similar error reported when there is simultaneous backup running operation.

    Make sure to run twice at a time when there is no alternative transaction.

    Thank you

    Renu

  • Need help for the restoration of the level 1 backup

    Hello!

    I am trying to create my database on a new server using hot rman incremental backups.

    I already restored and retrieved my database of level 0 on the new server, but I am not able to restore/recover the level 1 backup of the new server. I transported irom backup level 1 the old server to the new. What I need to get lvl 1 bkp only or also to restore it.

    Can someone help me on this problem by specifying the steps to restore/recover backups incremental level 1?

    Thank you!

    If the recovery has been completed and "tables are not present", this means that the tables were not present at this SNA. Either they were created after the SNA GOLD were dropped from the later the RCS.

    You must have block change tracking for restoration. It is used for backups only (and it of okay if she was present or not in the backup).

    Hemant K Collette

  • What is the need for level 0 and level 1 backup?

    I am a bit confused about the need for level 0 and level 1 backup. Oracle has proposed strategy in 10g creates only level 1 backup continues to not to break and not to create any level of 0 after the first backup of level 0. But I had seen in the document Oracle Database Backup & Recovery basis he suggests to create backup of level 0 on weekly or monthly basis. There?

    Secondly according to my understanding when creating oracle backup of level 1 first creates a level 0 backup that contain also copies of data image files and then apply an incremental copies of the image, once the incremental backup is applied on the copy of the image you don't have to the previous incremental backups. Am I wrong?
    If I'm right, what is the difference between level 0 & backup of level 1? and after the level 0 backup you must also all previous backups.

    PL. help me to clarify my questions in this regard.

    Kind regards

    Vassallo

    What is the most reliable in terms of recovery?

    I do not see the differences in terms of recovery, the two strategies are reliable.

    There is an advantage in terms of recovery time expected, Oracle says:

    /*
    Incorporate gradually update the backup in your backup strategy shortens the time of recovery as provided. The reason is that media recovery right now or at some point in the recent past may begin at the time of the last backup of level 1 applied, rather than at the time of the last full database backup.
    */

    In a regular incremental backup strategy you always go back to a level 0 backup and then to apply everything follows level 1 backups + archivelogs. But - for an incremental backup set to day - it's a little tricky to emerging a window of recovery, normally relies on redundancy 1, i.e. that a backup is retained, you cannot go back, this type of backup is designed for a quick and complete recovery.

    But there is a solution (I don't think there is place in EM), even if you're on 10g, see the 11 g documentation, he explains fuller:

    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28270/rcmbckba.htm#BRADV89532

    Werner

  • How the level 0 and level 1 backups are related?

    Version: 11 g

    I was going through the scripts in the post, two issues related to the RETENTION STRATEGY


    When you have a differential incremental backup strategy and when you run scripts to backup of level 1 and level 0 via cronjobs different from Sunday to Saturday, during recovery, how RMAN will identify all these level 1 backups and backup of level 0 parent as a single unit? In level 0, and its backup scripts later level 1, I do not see a clause that links the level 0 backup and its subsequent backups level 1?

    Hi Steve_74,

    How RMAN will identify all these level 1 backups and backup of level 0 parent as a single unit?

    Information used during a restore comes the controlfile.

    Example of
    Select backup, INCREMENTAL_LEVEL
    v $ backup_set
    /
    Will determine the backup set level 0 necessary depending on your clause of restore

    Select INCREMENTAL_LEVEL, INCREMENTAL_CHANGE #, CHECKPOINT_CHANGE #.
    v $ BACKUP_DATAFILE
    When file # = 1
    /
    Will determine what (s) to apply to the datafile 1 according to your restoration clause.

    Kind regards

    Tycho

    Edited by: tychos on November 1st, 2009 01:51

  • Block Media Recovery and RMAN backup incremental level 1

    Hello

    I read somewhere that block Media Recovery will not work if a database is backed up with 1 incremental rman. Is this true and if so is there a work around?
    I can't find it in the documentation of oralce.

    Concerning
    Me

    Hello

    Yes you are right, for the recovery block media, you must have full rman backup. Incremental backups are not used by block
    media recovery. Only full backups and archived logs are used.

    See this doc on part III

    http://download-UK.Oracle.com/docs/CD/B19306_01/backup.102/b14191/TOC.htm

    concerning

    Jafar

    Published by: jerome on October 22, 2008 19:51

  • RMAN restore level 0, 1 incremental level and ARCHIVELOGs

    I can't understand it and I read through the documentation and the web.

    On linux 64-bit in 11.2.0.3, I do weekly backups of level 0 and increments of 1 level every night. During the day, I also do ARCHIVELOG backups.

    I know I need to restore the LEVEL 0 database files (which I can do it), then later increments of 1 LEVEL of restoration (which I just can't), then apply ARCHIVELOGs (what I do).

    My problem is HOW to apply files of database LEVEL 1 of the above LEVEL 0 incremental backups restored?

    Thanks in advance!

    default channel: deletion of Journal archives

    And I haven't used the command "recover archivelog deletion of database; I used "recover the database.

    This isn't a problem. At the time of recovery, it is common that you see these messages.

    During restore, RMAN restores the archives at the local site, and finally when the recovery is complete, it deletes the temporarily stored archives.

    rewh2oman
         
    Handle: rewh2oman
    Status level: Beginner
    Join date: January 9, 2007
    Messages total: 87
    Total Questions: 6 (4 pending)
    Name russ

    If you feel that your questions have been answered, then please provide appropriate points and consider the son of closing. Please clean the forum!

  • Restore database from a cold backup

    Hi all

    We use Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 on SunOS 5.11.

    We have a database of primary and physical standby.

    We used to catch a cold backup of database pending. Now we want to restore the cold backup and as primary (scénarion of building our database main and backup have been planted and we have cold backup standby?.)

    We have done following the steps.

    1 copy the cold backup on server

    2. Mount the backup database

    3. perform the pint in time recover by issuing the fllowing command

    to recover a database on hold until cancel;

    4. apply some archived files and then CANCEL

    5 issue command to change the mode as "THE PRIMARY", as a result

    ALTER database recover managed standby database finish; and received followig error (alert log file)

    " Sun Aug 18 14:39:42 2013

    Logmerger died, by closing parallel recovery slaves

    Sun Aug 18 14:40:16 2013

    Death of recovery slave PR00

    Sun Aug 18 14:40:24 2013

    Interruption recovery! »

    We successfully restore the database and swithover the primary status after completing the steps:

    1. Cold backup on server
    2. Mount the database on hold
    3. Perform the recovery point in time by issuing the fllowing command
      1. recover database until cancel; pending
      2. Applied some files and then CANCEL
    4. Delete the log files waiting for redo
      1. change the Group of clear database logfile
    5. Recovery of eve of finishing
      1. ALTER database recover managed standby database finish;
    6. Issue following command to change the mode of "PRIMARY."
      1. change the database for validation to the passage at the elementary level with the end of the session;
    7. Open database
      1. ALTER database open;
    8. The redo log files
      1. Alter system switch logfile;
    9. Restart the database

    Earlier, we had missed step # 4.

    Kind regards

    Hassan

  • LEVEL 0 BACKUP FAILURE AFTER CHANGE HARD DRIVE

    Hello

    Yesterday I took the backup of level 0 from the new hdd(H:), mais il a échoué.) Please find more information,

    OS - Windows server 2012 (Live)

    VERSION - 11.2.0.1.0

    SERVER - server production

    Previously I configured 2 TB external Hdd in G: drive and set db_recovery_file_dest 2000 GB and backup location also the same hard drive size. Log Archive also only set according to G: drive location

    Since last three it is smoothly and taken the backup and the status of yesterday as hdd(G:) sur le point de remplir et il n'y est pas d'espace pour contenir le prochain niveau 0.)

    Now, according to those elders advice and I decided to take the only above mentioned archive disk G: log and mount the new hard drive in drive H: and Changed to the H: drive db_recovery_file_dest as below,

    H:\RMAN\AWSPROCESS\BACKUP and I did nothing with the parameter db_recovery_file_dest_size, it is intact, that the way in which it has been defined depending on the hard disk existing (g) 2000 GB (I learned that I changed my backup location, so this new HARD drive will automatically consider

    My goal is that enough backup RMAN based on Hdd (H :) new and I started yesterday and obtained backup failed with only 155 GB of backup in the new hdd(H:), si le niveau 0 prises avec succès, alors il pourrait être autour de 400 Go.))

    How to take my level 0 success based on newly mount Hdd (H :). What I did wrong and what to do more to achieve my successful backup.

    Please guide me.

    If you simply replace the disk, RMAN will always have the previous saved backups. RMAN does not automatically adjust its records because you free up space on the side of the BONE. You must do an overlap RMAN to synchronize your catalog or the RMAN command file and delete the records expired in your RMAN Repository in order to relaim the space on your FRA.

    http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV89615

Maybe you are looking for