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

Similar Messages

  • Block media recovery

    All,
    I'm in the process of self-learning all kind of data recovery strategy on my desktop.
    How to simulate the error of datafile block corruption ? To test the block media recovery through rman.
    Please advice.
    Thanks

    Though in Windows, an open db doesnot allow a file to be openedYou should try with the most powerfull Win* tool: notepad...
    You'll be surprised.
    Regards,
    Yoann.

  • 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

  • RMAN 0 level backup failed while releasing channels at end.

    In RMAN 0 level backup, when it's about to finish, reports an error as releasing channels. It backed up about 98% datafiles.
    Is this backup is usable. As we can not affort to take backup again as it's a big terabyte databse.
    Please suggest.
    Thanks in advance.
    Aj.

    Do you have release stmts in the script
    From 9i onwards oracle Release the channels automatically upon backing up, so you can remove the release channel lines if you have and try it

  • 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

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

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

  • RMAN - Schema level backup ??

    We have a production system in which one schema is getting bigger day by day(40GB).
    We want this schema in our development instnaces once in a week atleast.As export for this is taking time we want to go for rman setup for faster process.
    1)Will rman backup speed up the process ?
    2)Is there any way we can take the rman backup for a schema and not for the whole database.
    3)If yes what are the steps for this setup and steps to use this in the develpment database?
    Production is on hp-ux and dev on windows.

    1)Will rman backup speed up the process ?It depends. If they will be backuped only 40Gb, will be relatively fast.
    2)Is there any way we can take the rman backup for a schema and not for the whole database.Schema No, but if the schema objects is in a single tablespace one, can be make the tablespace backup
    3)If yes what are the steps for this setup and steps to use this in the develpment database?Follow the steps to backup the tablespace.

  • BACKUP AND RECOVERY USING RMAN

    제품 : ORACLE SERVER
    작성날짜 : 2003-08-04
    BACKUP AND RECOVERY USING RMAN
    ==============================
    1. Backup Method
    1.1 backing up in noarchivelog mode
    SVRMGR> shutdown;
    SVRMGR> startup mount
    rman을 가동시킨 후 다음을 수행
    run {
    # backup the database to disk
    allocate channel dev1 type disk;
    backup (database format '/oracle/backups/bp_%s_%p'); }
    1.2 Backing up databases and tablespaces in archivelog mode >
    - database 단위 backup script
    run {
    allocate channel dev1 type 'sbt_tape';
    backup skip offline (database format '/oracle/backups/%d_%u');
    release channel dev1;
    - tablespace 단위 backup script
    run {
    allocate channel dev1 type disk;
    backup
    (tablespace system,tbs_1,tbs_2,tbs_3,tbs_4,tbs_5
    format '/oracle/backups/bp_%s_%p');
    - datafile 단위 backup script
    run { 
    allocate channel dev1 type disk;
    backup
    (datafile '?/dbs/t_dbs1.f'
    format '/oracle/backups/%d_%u');
    - control file backup script
    control file은 system datafile의 첫번째 화일을 백업받을 때 백업되며 다음과
    같은 방법으로도 백업받을 수 있다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (tablespace tbs_5 include current controlfile
    format '%d_%u');
    - archived logs backup script
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog from time 'Nov 13 1996 20:57:13'
    until time 'Nov 13 1996 21:06:05'
    all
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog low logseq 288 high logseq 301 thread 1
    all delete input
    format '%d_%u');
    - copying datafiles
    run {
    allocate channel dev1 type disk;
    copy datafile '?/dbs/tbs_01.f/dbs/tbs_01.f' to '?/copy/temp3.f';
    - incremental backups
    새로운 데이타화일이 추가되거나 테이블스페이스가 추가된다면 level 0의 backup을
    반드시 수행한다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 0
    (database
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 1
    (database
    format '&d_%u');
    2. Recovery Method
    - tablespace recovery
    run { 
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    sql "alter tablespace tbs_1 offline immediate" ;
    set newname for datafile 'disk7/oracle/tbs11.f'
    to 'disk9/oracle/tbs11.f' ;
    restore (tablespace tbs_1) ;
    switch datafile all ;
    recover tablespace tbs_1 ;
    sql "alter tablespace tbs_1 online" ;
    release channel dev1;
    release channel dev2;
    - point-in-time recovery
    TBS_1 테이블스페이스는 두 개의 데이타 화일 소유. TEMP1은 백업이 없으나 user
    data는 없는 temporary segemnt만 가지고 있음.
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    SVRMGR> shutdown abort;
    SVRMGR> startup nomount;
    run { 
    # recover database until 3pm after restoring tbs_1 to a new location
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    set until time 'Nov 15 1996 15:00:00'
    set newname for datafile '/vobs/oracle/dbs/tbs_11.f'
    to '?/dbs/temp1.f' ;
    set newname for datafile '?/dbs/tbs_12.f'
    to '?/dbs/temp2.f' ;
    restore controlfile to '/vobs/oracle/dbs/cf1.f' ;
    replicate controlfile from '/vobs/oracle/dbs/cf1.f';
    sql "alter database mount" ;
    restore database skip tablespace temp1;
    switch datafile all;
    recover database skip tablespace temp1;
    sql "alter database open resetlogs";
    sql "drop tablespace temp1";
    sql "create tablespace temp1 datafile '/vobs/oracle/dbs/temp1.f' size 10M";
    release channel dev1;
    release channel dev2;
    - 전체 데이타베이스를 복구하려 할때
    current redologfile이 존재할때 다음과 같은 작업으로 전체 데이타베이스를 복구할
    수 있다.
    replace script restore_recover_db_cf {
    execute script restore_cf;
    sql 'alter database mount';
    execute script restore_db;
    execute script recover_db;
    sql 'alter database open resetlogs';
    replace script alloc_1_disk {
    allocate channel d1 type disk;
    setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
    replace script rel_1_disk {
    release channel d1;
    replace script restore_cf {
    execute script alloc_1_disk;
    restore
    controlfile to '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    replicate
    controlfile from '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    execute script rel_1_disk;
    replace script restore_db {
    execute script alloc_1_disk;
    restore
    (database);
    execute script rel_1_disk;
    replace script recover_db {
    execute script alloc_1_disk;
    recover
    database;
    execute script rel_1_disk;
    Reference Documents
    <Note:104796.1>

    Hi Alok,
    why there is a need for standby here? you mean to say standby db?
    what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

  • 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

  • Rescue and recovery doesn't see my backup

    I installed windows 7 a few days ago, I had vista, but I'm having some problems. the first
    one is system migration assistant. I asked it to transfer my music folder and my passwords
    from the password manager, which it both didn't. it ust didn't transfer them. luckily, I made
    a backup before starting this business, but I can't see it when I open rescue and recovery!
    the backup is on an external USB hard drive. when I open Rescue and Recovery, advanced
    mode, set prefferred backup location to USB, start recovery and then list the backups, nothing is shown.
    one more thing, if I was able to see the backup, getting back my music wouldn't be that much
    of a trouble, but I think getting back my passwords will be more difficult. what's the easiest way
    of getting back my passwords if I am able to see the backup?
    when I open the RRbackups folder on the drive, there is a folder \RRbackups\Documents and Settings\Daniel Bakker\AppData\Roaming\Lenovo\Client Security Solution,
    which contains a .pwm file, a file from which I suppose it holds the password data. so I thought, let's use the import function from the
    password manager. but then of course it asks for the password which the file is encrypted with.
    the password isn't my windows password, but is there any way to find out with which password it is encrypted?

    I've seen some versions of R&R refuse to show backups when their total space taken was at or near the limit set in R&R. In advanced mode, set the limit as high as possible and see if they appear.
    This is if you are working from the installed R&R. If you're running from a rcovery CD, never mind...
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • ORA-01123: cannot start online backup; media recovery not enabled

    the Oracle doc says:
    Action: Enable media recovery and retry this operation.
    how helpful it is!
    Could someone advise me on what is exactly the command
    for "enable media recovery"?
    Thanks.
    - Zack Hu

    but when I modified the init.ora file and re-start the
    db, I still have "NO archive mode", when I tried to
    set it to archive mode I got an error:
    SQL> startup pfile='D:\oracle\admin\WinMWDCS\pfile\initWinMWDCS.ora';
    ORACLE instance started.
    Total System Global Area 135863156 bytes
    Fixed Size 453492 bytes
    Variable Size 109051904 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 1191936 bytes
    Database mounted.
    Database opened.
    SQL> archive log list;
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination d:\oracle\oradata\WinMWDCS\archive
    Oldest online log sequence 73
    Current log sequence 75
    SQL> alter database archivelog;
    alter database archivelog
    ERROR at line 1:
    ORA-01126: database must be mounted EXCLUSIVE and not open for this operation

  • 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

  • Problem in performing multiple Point-In-Time Database Recovery using RMAN

    Hello Experts,
    I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
    Environment:
    Oracle 11g, ASM,
    Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
    Snapshot DiskGroups :
    Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
    Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
    Steps performed for point in time recovery:
    1. Restore control file from snapshot 2.
         RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
    2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
    3. Catalog data files from snapshot 1.
    4. Catalog archive logs from snapshot 2.
    5. Perform point in time recovery till given time.
         STARTUP MOUNT;
         RUN {
              SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
              SET UNTIL TIME "06-mar-2013 09:30:00";
              RESTORE DATABASE;
              RECOVER DATABASE;
              ALTER DATABASE OPEN RESETLOGS;
    Results:
    Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
    Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
    Starting recover at 28-FEB-13
    using channel ORA_DISK_1
    starting media recovery
    media recovery failed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 03/06/2013 11:10:57
    ORA-00283: recovery session canceled due to errors
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
    start until time 'MAR 06 2013 09:45:00'
    ORA-00283: recovery session canceled due to errors
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
    ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
    ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
    Doubts:
    1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
    3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
    However for this to work, I always need to keep the AutoBackup feature enabled.
    How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
    4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
    Please help me out in this issue.
    Thanks.

    992748 wrote:
    Hello experts,
    I'm little newbie to RMAN recovery. Please help me in these doubts:
    1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
    2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
    3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
    Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
    Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
    But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks.

  • NOLOGGING with CTAS and RMAN's Incremental backup

    DB Version: 10.2.0.4
    OS : AIX
    We use RMAN for our backup scheduled via cron.
    Retention Policy : REDUNDANCY 1
    Type             : Incremental On 31st of every month, in most of our schemas, we recreate lots of tables using CTAS.
    Because of the size , CREATE TABLE statements take a long time. Since we run on Standard edition, we can't use PARALLELISM.
    NOLOGGING is the only option to improve the performance. But we are worried about the redo not being generated for these tables and the potential loss of data in case of a crash.
    Currently we take a LEVEL0 backup every wednesday and Sunday nights and LEVEL1 backup on the rest of the days.
    I know that everything will be backed up on LEVEL0. But, what if 31st falls on a day where only LEVEL1 backup occurs. We'll only be safe until the next LEVEL0 comes along.
    Any workarounds for this?

    When you write "we need" you make an assumption not supported by the facts.
    The fact is that you need to refresh the data ... you do not need to recreate the table.
    This is just one better solution:
    http://www.morganslibrary.org/reference/materialized_views.html
    there are others too. But not knowing your version number, and you still have not really stated the business case, I can not advise which would be the best. But it is safe to say there is no way on earth I would do what you are doing based on what you've posted. For example why at the end of each day can't you copy that day's rows to a predefined table spreading the load out over all 30 days and then, at month's end truncate the current table and rename it then rename the already loaded staging table. The swap could be done in a few seconds with essentially no overhead.

Maybe you are looking for