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?

Similar Messages

  • 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

  • How to create non cumulative Key Figure.

    Friends Let me know steps for creating Non Cumulative Key Figure, can any one tell me where can i get documents for this. points will be rewarded

    Hi,
    check these help links
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/95/1ae03b591a9c7ce10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6312e07211d2acb80000e829fbfe/content.htm
    It's a big topic so it's not possible to write everything here.
    You can search the forums also.
    Thanks

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

  • 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

  • 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

  • Prob while creating Non - Cumulative KF with Inflow & Outflow

    hello all,
    I created 3 Key Figures, with DEPOSIT, WITHDRAWL, BALANCE... with Amount & 0CURRENCY data type... If i measure the DEPOSIT & BALANCE in 0CURRENCY then only i could be able to see the keyfig in Inflow(DEPOSIT) and Outflow(WITHDRAWL) of the Total Key fig.. I hope till here is fine..
    Im loading the file thru Flat file..
    when im activating the Data Source it got activated(whr 0CURRENCY is taken in once FIELDS tab while mapping)...
    The problem started whn im ran IP... its throwing the error msg " The argument " INR" or "USD" cannot be interuppted as a number on assignment field / BIC/WITHDRAWL record 1 value INR.
    Thanks in advance

    Hi,
    what i understood from the message again is ur mapping the filed currency to withdrawal keyfigure.
    chk the columns order in datasource and flat file and assign the proper mapping pls.
    lets say if u have Deposit,withdrwal, balance,currency as your fields in u r datasource then do have the same fields in your Flat file as well so that they are in same order as in datasource.
    pls chk this and try again.

  • 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

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

  • Cumulative Incremental?

    Hopefully you all can resolve a question for me. I was under the impression that a CUMULATIVE backup and an INCREMENTAL backup were two separate things.
    INCREMENTAL LEVEL : Copies only those data blocks that have changed since the last incremental integer backup, where integer is 0 or 1 (see Example 2-16).
    CUMULATIVE : Copies the data blocks used since the most recent level 0 backup (see Example 2-16).
    So I go to "Example 2-16"...
    http://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta007.htm
    Example 2-16 Performing a Cumulative Incremental Backup
    This example backs up all blocks changed in the database since the most recent level 0 incremental backup. If no level 0 backup exists when you run a level 1 backup, then RMAN makes a level 0 backup automatically. Any inaccessible files are skipped.
    BACKUP
      INCREMENTAL LEVEL 1 CUMULATIVE
      SKIP INACCESSIBLE
      DATABASE;I am confused. I thought that cumulative/incremental were exclusive backup types. How can they both be referenced in the same code block?
    Thanks

    Hi,
    please donot be confuse In the same document it written
    Incremental Backups:
    An INCREMENTAL backup at level 0 backs up all data blocks in datafiles being backed up. An incremental backup at level 0 is identical in content to a FULL backup,
    but unlike a full backup the level 0 backup is a part of the incremental backup strategy.
    A level 1 backup copies only changed blocks. A level 1 incremental backup is either differential or CUMULATIVE.
    *If cumulative, RMAN backs up all blocks changed since the most recent level 0 backup.*
    *If differential, RMAN backs up blocks updated since the most recent level 0 or level 1 incremental backup.*
    HTH :)

  • 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

  • Trouble with Non Cumulative Key Figures

    Hi all of you,
    I am working on Non Cumlative Key Figures, (NCKF). I have the data like this
    Sales rep S100 visited SHOP S1 on 1st Jan and 10th Aug, and transacted worth         100 and 500
    SHOP S2 on 1st Mar and 1st July and transacted worth 200 and 300
    SHOP S3 on 3rd Sept. and transacted worth 400
    Sales rep S200 visited SHOP S1 on 1st Jan and 1st Aug and transacted worth 100 and 300,
    visited SHOP S2 on 1st April and transacted worth 200     
    I created Non Cumulative Key Figure in the following manners:
    In modeling in InfoObjects I double clicked on my key figure BILLAMT and selected the Aggregation tab. I selected Counter (all values) for Exception aggregat. By default Agg. Referen. Char was 0calday. I then activated the info object and went to BEx. Here I took other IOs like Salesrep, Shop NUM and Dt. Of trans in rows and Bill amt in columns and executed the report. I am not getting the output how it should come for NON cumulative key figures.
    But when I right click the key figure Bill Amount in BEx in change query mode and select properties. I go to the option Calculate result as and selected the option as “Count all values”. And in another option Calculate Single Value as I selected the option “Count all values”. I said OK, saved the query and executed it. Now the output is similar to how it comes for a Non Cumulative Key Figure query but I am unable to understand the output.
    Now my doubt is where do we set the properties for Non Cumulative Key Figures? Is it in the Administrator Workbench under Modelling under InfoObjects?
    OR
    Is it in BEx change query mode by right clicking on the key figure and selecting properties?
    Please explain.
    Thank you
    TR.

    As for the setting for Non Cumulative key figures...the default setting is done in the Key Figure properties, where u can define the Exception Aggregation. This property is used as such in the query, but if suppose u are getting the normal aggregation in the query , what you could do is "Create The Key Figure as Global Calculated Key Figure in Bex" and go to properties...click on the Button for aggregation ..select the aggregation and define with respt to 0CALDAY ..here.
    Hope this helps.

  • Non cumulative with non-cumulative change

    Hi Experts,
    I have a Question !, As i know that i can create Non-Cumulative Figure By Means Of two ways:-
    1. Non cumulative with non-cumulative change and
    2. Non Cumulative with Inflow and Outflow.
    the second one is very clear but i am not very clear about 1st option i.e What Non-Cumulative Value changes is? and how it calculates the non-cumulative Value.
    If u have an Idea please share your knowledge...
    Ragards
    Prakash

    The 1st option is for key figures like headcount or similar, which you would like to store as a total figure in a cube instead of a DSO in a scenario where you are using a multiprovider on this together with other non-cumulative cubes.
    The SAP help below explains this quite well
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
    Best,
    Ralf

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

  • Is level 0 backup = whole backup ?

    The level 0 backup is a start point that contains all blocks.
    if so, is it same as whole database backup?
    if so, why it called incremental level 0 backup?
    a bit confused.

    Its a terminology that makes it confusing. Its indeed the whole backup but in the incremental backup, it serves as the base as well. In oracle. there are terms like this. For example, oracle uses in the B/R manuals , two terms for the backup, whole database backup and full database backup, when actually there is just one command, Backup Database. But the terminology says, if you include your archive logs, spfile with the data files and control files, its whole backup otherwise, its just full backup. This is the similar kind of thing, so don't be confused.
    Rest of the details are in that link which is already given to you. Have a good read of it.
    HTH
    Aman....

Maybe you are looking for

  • MacBook Doesn't run from battery

    My MacBook is no longer running from battery, it seems like is fully charged or have not problem charging itself, but if I disconnect the charger it shuts off automatically and also if I try to turn on from Battery it tries to start but immediately s

  • Nokia e6 check-in app/feature

    thanks to evrybody in the house, have being using my nokia e6 for over a year now, earlier dis year i have an hardware issue, so i took it for refix at nokia care centre in lagos nigeria, after d refix, they did wot they call upgrade for me. sinced t

  • Second Admin User - keychain login?

    Recently added second Admin User (Spouse). When logged in to the second Admin User, being required to enter Keychain login password from first Admin User. This is for Safari and for other apps. If the second User is logged in at an administrative lev

  • Failover - How to achieve a transparent failover using SQLPlus

    AIX 5.3 Oracle Clusterware 10.2.0.4.0 Oracle Enterprise Edition 10.2.0.4.0 This is the behavior I see from an Oracle Client session which is to be expected if I read RAC: Frequently Asked Questions [ID 220970.1] see below (1) SQLPlus session connecte

  • ADF_FACES-60098:The Faces lifecycle exceptions receives untreated RENDER_

    Anyone know why I get this error when doing a tree table, unfold out when the third node, the first two without any problems. to run my application module views the relationship of the nodes is fine but the error comes when I pass the ADF component a