Rman retention window doubt

Hello, i have RMAN backup in the way of backupsets on two node 11gR2 RAC on linux standard edition.
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name MGW are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_mgw2.f'; # default
RMAN>And now i dont understand why RMAN is not deleting backupsets that are older then 24 hours , although i have set
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS.
I have in my rman script that is executing every day @ 23:00 this:
backup as COMPRESSED BACKUPSET database FORMAT '/home/oracle/rman/%U' plus archivelog delete input;
delete noprompt obsolete;And now i see in my rman backup folder that there is backupset from yesterdey 23:00 ,and also from the day before yesterday 23:00.
[oracle@data02 rman]$ ls -l
total 51889864
-rw-r----- 1 oracle asmadmin 26454474752 Jul 14 00:19 0bmhcc1s_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 14 00:19 0cmhcg84_1_1
-rw-r----- 1 oracle asmadmin 26626334720 Jul 15 00:18 0fmhf0ep_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 15 00:18 0gmhf4ih_1_1
-rw-r--r-- 1 oracle oinstall           0 Jul 14 16:52 aa_1_1I thoght that if i have run my rman script today @ 23:00 , than that will do backup but also delete backup from the day before because i have set
retention to 1 day .
Can you please say why i am wrong in this ?

The RMAN retention policy doesn't just keep the amount of days specified. It calculates the interval from the end of the current time and extends back in time for the number of days specifed.
So for example if you set the backup retention policy to 1 day today. Then RMAN will keep the backups for 15th July, 16th July.
Then on the 17th July, the 15th July backup will be obsolete.
I.e.
Current date   Status                                 Recovery Point
15th July        available                               15-1 = 14th July
16th July        available                               16-1 = 15th July
17th July        backup of 15th July obsolete  17-1 = 16th July
So your backup for today wouldn't be marked as obsolete until the 17th July.
5 Configuring the RMAN Environment
However, if you have a fixed-date database then you should be setting the retention policy to redundancy instead of recovery window.
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

Similar Messages

  • RMAN -Retention policy doubt

    Hi,
    I have doubt on RMAN retention policy.
    we are taking daily cumulative backup and weekly Full database backup.
    And our retention policy is "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS"
    My assumption is that RECOVERY window of 3 days will hold the backups of 3 days and delete the previous backups,since we are taking cumulative backups,and using them database can be recovered.
    we used below commands to take cumulative backup.
    backup incremental level 1 cumulative as COMPRESSED BACKUPSET tag '%TAG' database include current controlfile;
    backup as COMPRESSED BACKUPSET tag '%TAG' archivelog all not backed up;
    Regards,
    mannu

    Thanks for reply.
    A recovery window is a period of time that begins with the current time and extends backward in time to the point of recoverability. The point of recoverability is the earliest time for a hypothetical point-in-time recovery, that is, the earliest point to which you can recover following a media failure. For example, if you implement a recovery window of one week, then this window of time must extend back exactly seven days from the present so that you can restore a backup and recover it to this point. You implement this retention policy as follows:
    In our case:
    Jan 24---Level 0 Full backup
    Jan 25-Cumulative backup
    Jan 26-Cumulative backup
    Jan 27--->Cumulative backup
    Jan-28 ----->cumulative backup
    What would be my point of recoverability? How my recovery window period of 3 days work here.
    Regards,
    Mannu

  • RMAN Retention Policy - redundancy vs recovery window

    Hi All,
    I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
    I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
    Thanks in advance.

    Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
    Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
    Two things you need to consider:
    1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
    2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
    We use "Recovery Window"

  • RMAN Recovery Window 7 days setting - shows no obsolete backups

    Hi All. Quick question about RMAN retention policy....
    I have the current backup strategy:
    Full backup (0) -> Sunday
    Incremental backup (1) -> Monday - Saturday
    Archive log backups -> every hour
    This is a new database I just started taking backups on last month. (1st full backup was run October 4th)
    I currently have not deleted any of them.
    The old RMAN RETENTION POLICY was set to REDUNDANCY = 1
    REPORT OBSOLETE lists all of them up to the last full which ran this past Sunday (Nov 1st)
    I just switched the RMAN RETENTION POLICY to RECOVERY WINDOW of 7 DAYS
    REPORT OBSOLETE lists no backups obsolete...
    Shouldn't I see all the backups prior to a week ago or does it only take affect for backups run under the new policy?
    Any help/replies are apprecitaed.
    Thanks

    Ran crosscheck with no problems:
    Crosschecked 200 objects
    But still same results for:
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    no obsolete backups found
    Am I missing something here? Or like I mentioned is this expected behaviour because all of my other backups were run with REDUNDANCY = 1 retention policy?
    Thanks

  • Query on RMAN Retention Policy

    Hi, I have my Retention policy set to Redundancy 2
    I have taken 3 backups so far ( 2 Backup Sets, 1 Image Copy )
    When I check report obsolete I get the following
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           1      05-SEP-13
      Backup Piece       1      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp
    Backup Set           2      05-SEP-13
      Backup Piece       2      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp
    Backup Set           3      05-SEP-13
      Backup Piece       3      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp
    Backup Set           4      05-SEP-13
      Backup Piece       4      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp
    Backup Set           5      27-SEP-13
      Backup Piece       5      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp
    Backup Set           7      27-SEP-13
      Backup Piece       7      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp
    Archive Log          305    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc
    Archive Log          306    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc
    Archive Log          307    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc
    Archive Log          308    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc
    Backup Set pieces 1,2,3,4 basically equate to my oldest backup - hence under redundancy of 2, I can see why that is obsolete
    5 and 7 were simply Control File/SPFILE backups from Auto Backup and the 2 newer backups of these have been taken since ( i.e. backupset pieces 9 and 10 )
    Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
    Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
    Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
    Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
    any advice appreciated,
    Jim

    Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
    Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
    - Yes you can get the database to the date which ever you want , using recover database until time.
    Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
    - can you please provide the output of below command
    RMAN> show all;
    Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
    - You can restore the database back  to two days or 5 days based on your requirement. You nee to recover the database using  until time option.
    Thanks,
    http://gssdba.wordpress.com

  • RMAN retention policy

    Hi,
    on 10g R2 on AIX6.1 , I have the followings :
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;My backup script :
    RMAN> run
          allocate channel t1 type disk;
          backup as compressed backupset format '$dir/df_%d_%T_%s_%p' database;
          sql 'alter system switch logfile';
          backup as compressed backupset format '$dir/al_%d_%T_%s_%p' archivelog all delete input;
          backup as compressed backupset format '$dir/ctl_%d_%T_%s_%p' current controlfile;
    crosscheck backup;
    delete noprompt obsolete;
    delete noprompt expired backup of database;But I have the backup files of 3th of March yet :
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1 recid=171 stamp=744800219And the only file it deletes is :
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 14 days
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           13404  18-MAR-11
      Backup Piece       13408  18-MAR-11          /appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1
    deleted backup piece
    backup piece handle=/appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1 recid=331 stamp=746072971
    Deleted 1 objectsShould not RMAN delete the backup files of before 15 of March ? Why it does not ?
    Thank for explanation ? Or more.

    Thank to all.
    We backup it every night (FULL at WE and incremental in week).
    list backup of database;
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    7145    Full    571.86M    DISK        00:01:55     03-MAR-11
            BP Key: 7151   Status: AVAILABLE  Compressed: YES  Tag: TAG20110303T085658
            Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1
      List of Datafiles in backup set 7145
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 75445711   03-MAR-11 /data01/bases/MYDB/system01.dbf
      2       Full 75445711   03-MAR-11 /data01/bases/MYDB/psundots01.dbf
      4       Full 75445711   03-MAR-11 /data01/bases/MYDB/psdefault.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    19112   Full    772.42M    DISK        00:03:05     01-APR-11
            BP Key: 19118   Status: AVAILABLE  Compressed: YES  Tag: TAG20110401T121403
            Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110401_60_1
      List of Datafiles in backup set 19112
      File LV Type Ckp SCN    Ckp Time  Name
      8       Full 152751106  01-APR-11 /data01/bases/MYDB/ptprc.dbf
      10      Full 152751106  01-APR-11 /index01/bases/MYDB/pttbl.dbf
      15      Full 152751106  01-APR-11 /data01/bases/MYDB/pttlrg.dbf
      19      Full 152751106  01-APR-11 /data01/bases/MYDB/ptprjwk.dbf
      20      Full 152751106  01-APR-11 /data01/bases/MYDB/ptaudit.dbf
      24      Full 152751106  01-APR-11 /data01/bases/MYDB/amlarge.dbf
      26      Full 152751106  01-APR-11 /data01/bases/MYDB/apapp.dbf
      27      Full 152751106  01-APR-11 /data01/bases/MYDB/aparch.dbf
      34      Full 152751106  01-APR-11 /data01/bases/MYDB/aucapp.dbf
      35      Full 152751106  01-APR-11 /data01/bases/MYDB/auclrge.dbf
      37      Full 152751106  01-APR-11 /data01/bases/MYDB/bdapp.dbf
      38      Full 152751106  01-APR-11 /data01/bases/MYDB/bdlarge.dbf
      40      Full 152751106  01-APR-11 /data01/bases/MYDB/bilarge.dbf
      42      Full 152751106  01-APR-11 /data01/bases/MYDB/caapp.dbf
      50      Full 152751106  01-APR-11 /data01/bases/MYDB/cuaudit.dbf
      54      Full 152751106  01-APR-11 /data01/bases/MYDB/cularge.dbf
      58      Full 152751106  01-APR-11 /data01/bases/MYDB/dpwork.dbf
      60      Full 152751106  01-APR-11 /data01/bases/MYDB/eobfapp.dbf
      64      Full 152751106  01-APR-11 /data01/bases/MYDB/eocmwrk.dbf
      71      Full 152751106  01-APR-11 /data01/bases/MYDB/eoecwrk.dbf
      74      Full 152751106  01-APR-11 /data01/bases/MYDB/eoepapp.dbf
      75      Full 152751106  01-APR-11 /data01/bases/MYDB/eoeplrg.dbf
      77      Full 152751106  01-APR-11 /data01/bases/MYDB/eoewapp.dbf
      81      Full 152751106  01-APR-11 /data01/bases/MYDB/eoiulrg.dbf
      84      Full 152751106  01-APR-11 /data01/bases/MYDB/eoltapp.dbf
      85      Full 152751106  01-APR-11 /data01/bases/MYDB/eoppapp.dbf
      88      Full 152751106  01-APR-11 /data01/bases/MYDB/eotplrg.dbf
      93      Full 152751106  01-APR-11 /data01/bases/MYDB/faapp.dbf
      95      Full 152751106  01-APR-11 /data01/bases/MYDB/fawork.dbf
      101     Full 152751106  01-APR-11 /data01/bases/MYDB/fgwork.dbf
      107     Full 152751106  01-APR-11 /data01/bases/MYDB/fowork.dbf
      109     Full 152751106  01-APR-11 /data01/bases/MYDB/fsapp1.dbf
      112     Full 152751106  01-APR-11 /data01/bases/MYDB/glapp.dbf
      122     Full 152751106  01-APR-11 /data01/bases/MYDB/inlarge.dbf

  • RMAN Retention policy 5 days but v$backup_set shows unexpected return

    ORACLE 10.2
    RMAN NOCATALOG
    Windows Server 2003
    Hi All,
    Just trying to get to grips with RMAN.
    I have the Retention policy set to 5 with Auto Backup Control File.
    I use a scheduled task to take a full backup every night due to small size of database.
    With a 'delete noprompt obsolete' after the backup to remove old backups.
    When I query the v$backup_set I get a return from a backupset from over 10 days ago? (this does not exist in my backup location) other than that the return is as expected.
    Can any one tell me why this is displaying and how to remove the invalid returns.
    Best Regards and Happy Xmas
    Neil
    Message was edited by: removed para due to believe it was incorrect statement
    So i beieve this is stored in the control file which has a default retention of 7 days (CONTROL_FILE_RECORD_KEEP_TIME)
    Neil Hunter

    Hi,
    Slimmed down RMAN report shows me the following, Sorry struggling with layout...
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    26 Full 6.80M DISK 00:00:00 14-DEC-07
    28 Full 6.80M DISK 00:00:00 15-DEC-07
    30 Full 6.86M DISK 00:00:00 16-DEC-07
    32 Full 6.86M DISK 00:00:01 17-DEC-07
    34 Full 6.86M DISK 00:00:01 18-DEC-07
    I have dates when selecting from v$backup_set from the 7,12,13 Dec? as well as the above..... extract as below
    COUNT B CON INCREMENTAL_LEVEL PIECES START_TIM COMPLETIO ELAPSED_SECONDS BLOCK_SIZE INP KEE KEEP_UNTI KEEP_OPTIO
    1 640712259 640712258 2 D NO 1 07-DEC-07 07-DEC-07 1 8192 NO NO
    2 640712260 640712259 3 D YES 1 07-DEC-07 07-DEC-07 1 16384 NO NO
    3 640712625 640712625 4 D NO 1 07-DEC-07 07-DEC-07 0 8192 NO NO
    4 640712626 640712626 5 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
    5 640712648 640712648 6 D NO 1 07-DEC-07 07-DEC-07 0 8192 NO NO
    6 640712649 640712649 7 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
    7 640713224 640713223 8 D NO 1 07-DEC-07 07-DEC-07 1 8192 NO NO
    8 640713225 640713225 9 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
    9 640713657 640713282 10 D NO 1 07-DEC-07 07-DEC-07 375 8192 NO NO
    10 640713668 640713667 11 D YES 1 07-DEC-07 07-DEC-07 1 16384 NO NO
    This could have been when I was setting up RMAN and testing taking a backup? how do I delete or will they expire....
    Reference you previous emails the KEEP fields are blank......
    Regards
    Neil
    Message was edited by:
    Neil Hunter
    Message was edited by:
    Neil Hunter

  • Why it automatically recover current redo log in RMAN command window?

    Firstly, I restore controlfile and datafiles from a backupset.
    Then when I recover database in RMAN command window like below:
    RMAN> recover database;
    Starting recover at 15-AUG-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    archive log thread 1 sequence 9 is already on disk as file /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc
    archive log thread 1 sequence 10 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc
    archive log thread 1 sequence 11 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc
    archive log thread 1 sequence 12 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc
    archive log thread 1 sequence 13 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc
    archive log thread 1 sequence 14 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc
    archive log thread 1 sequence 15 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc
    archive log thread 1 sequence 16 is already on disk as file /u01/app/oracle/oradata/lonion/redo03.log
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc thread=1 sequence=9
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc thread=1 sequence=10
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc thread=1 sequence=11
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc thread=1 sequence=12
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc thread=1 sequence=13
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc thread=1 sequence=14
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc thread=1 sequence=15
    archive log filename=/u01/app/oracle/oradata/lonion/redo03.log thread=1 sequence=16
    media recovery complete, elapsed time: 00:00:04
    Finished recover at 15-AUG-13
    RMAN>
    But, when I recover database in SQL*Plus command window like below:
    [oracle@lonion ~]$ uniread sqlplus /nolog
    [uniread] Loaded history (2178 lines)
    SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 15 19:25:38 2013
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    SQL> conn /as sysdba
    Connected.
    SQL>
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database using backup controlfile;
    ORA-00279: change 2147842454 generated at 08/15/2013 18:34:28 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_%u_.a
    rc
    ORA-00280: change 2147842454 for thread 1 is in sequence #9
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 2147842651 generated at 08/15/2013 18:40:25 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_%u_.
    arc
    ORA-00280: change 2147842651 for thread 1 is in sequence #10
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd
    0slz_.arc' no longer needed for this recovery
    ORA-00279: change 2147842653 generated at 08/15/2013 18:40:26 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_%u_.
    arc
    ORA-00280: change 2147842653 for thread 1 is in sequence #11
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90s
    d0tsb_.arc' no longer needed for this recovery
    ORA-00279: change 2147842656 generated at 08/15/2013 18:40:32 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_%u_.
    arc
    ORA-00280: change 2147842656 for thread 1 is in sequence #12
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90s
    d110b_.arc' no longer needed for this recovery
    ORA-00279: change 2147842684 generated at 08/15/2013 18:41:21 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_%u_.
    arc
    ORA-00280: change 2147842684 for thread 1 is in sequence #13
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90s
    d2ksr_.arc' no longer needed for this recovery
    ORA-00279: change 2147842686 generated at 08/15/2013 18:41:23 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_%u_.
    arc
    ORA-00280: change 2147842686 for thread 1 is in sequence #14
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90s
    d2mc6_.arc' no longer needed for this recovery
    ORA-00279: change 2147842689 generated at 08/15/2013 18:41:27 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_%u_.
    arc
    ORA-00280: change 2147842689 for thread 1 is in sequence #15
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90s
    d2qrm_.arc' no longer needed for this recovery
    ORA-00279: change 2147842691 generated at 08/15/2013 18:41:28 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_%u_.
    arc
    ORA-00280: change 2147842691 for thread 1 is in sequence #16
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90s
    g0or9_.arc' no longer needed for this recovery
    ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
    arc
    ORA-00280: change 2147842986 for thread 1 is in sequence #17
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_90s
    g0os5_.arc' no longer needed for this recovery
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    SQL> recover database using backup controlfile;
    ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
    arc
    ORA-00280: change 2147842986 for thread 1 is in sequence #17
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u01/app/oracle/oradata/lonion/redo01.log        ---- Yon see, proceeding this process, it can't automatically apply the current redo log.
    Log applied.
    Media recovery complete.
    SQL>
    Question Coming:
    Now, my question is that 「Why it automatically recover current redo log in RMAN command window but not in SQL*Plus」?
    BTW: Please pay attention to the red font.

    It also seems not work.
    SQL> recover automatic database using backup controlfile;
    ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
    arc
    ORA-00280: change 2148632889 for thread 1 is in sequence #48
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc' no longer needed for this recovery
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file
    or directory
    Additional information: 3
    SQL>
    It must specify the redo log.
    SQL> recover database using backup controlfile;
    ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
    arc
    ORA-00280: change 2148632889 for thread 1 is in sequence #48
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u01/app/oracle/oradata/lonion/redo02.log
    Log applied.
    Media recovery complete.
    SQL>

  • Rman Retention policy to recovery window

    Hi,
    I have few basic doubts in RMAN backup policy
    1 . Is that possible to set Retention policy to recovery window in minutes??
    2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
    Regards,
    007

    1) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
    2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
    Werner

  • 11gR2 DB - RMAN retains backupsets outside the specified retention window

    11.2.0.1.0 Enterprise Edition Database in Archivelog mode:
    Here's the results of SHOW ALL:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_hcoe.f'; # default
    I run this RMAN job nightly:
    $rman_script="run {allocate channel oem_disk_backup device type disk; recover copy of database with tag 'ORA_OEM_LEVEL_0'; backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA_OEM_LEVEL_0' database;}
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    delete noprompt expired backup;
    delete noprompt expired copy;
    Here's what my FRA looks like as of 2/20/2013:
    /u05/app/oracle/recovery_area/HCOE/archivelog - 7 subdirectories dated 2013-02-14 through 2013-02-20, all empty
    /u05/app/oracle/recovery_area/HCOE/autobackup - 7 subdirectories dated 2013-02-14 through 2013-02-20. The delete noprompt obsolete seems to be deleting these according to the recovery window setting of 4 days. The 2/14 subdirectory is empty, and the 2/15 directory has only 1 file in it. The rest have 2 files.
    /u05/app/oracle/recovery_area/HCOE/backupset - 15 directories from 2013-02-06 through 2013-02-20. These are not being deleted, nor are they considered obsolete. The directories only go back until 02/06, because I manually deleted the directories and their contents before that, and did a CROSSCHECK ALL afterwards when the FRA ran out of space and the active redo could not be archived. This is what I'm confused about. Why are they not being deleted, and what do I need to do to get them to become obsolete?
    /u05/app/oracle/recovery_area/HCOE/datafile - The location of the dbf image copies which are up to date as of 3:30am 2/20/2013
    Thanks in advance.
    Phil

    Phil;
    I believe this is why :
    backup incremental level 1
    Incremental backups are worthless unless you have the parent ( level 0 backup ). Because of this the window will always be larger than the 4 you have set.
    Example
    http://www.visi.com/~mseberg/rman/obsolete_backups.html
    Why are they not being deleted, and what do I need to do to get them to become obsolete?
    Do a level 0 more often.
    Best Regards
    mseberg
    Edited by: mseberg on Feb 20, 2013 8:28 AM

  • RMAN retention policy - backup spfile and then redundancy = 5 removes it.

    I have a database that is Oracle Standard Edition and it is version 9.2.0.6.
    The spfile has not changed since November, 2005. A list backup does not show an spfile backup with a tag of "hot_database_spfile_backup_full". I took a close look at the RMAN script log and was shocked to discover that the spfile backup from the current day is being deleted. Is that because of the redundancy = 5? I'm trying to figure out why a backup piece from the current day is being deleted?
    Examples follow.
    The script deletes obsolete with redundancy = 5, however, I believe the intent was to keep 25 days because one of the configure clauses is set to a recovery window of 25 days. I realize that the redundancy overrides the configure retention policy command. I can fix the script and remove the redundancy = 5.
    In the RMAN run statement, I first resync the catalog, backup the spfile, a full backup of the database including current controlfile plus archive log (delete input), resync catalog, switch logfile, and backup any additional archive logs. The backup looks fine.
    Then, I allocate a channel for maintenance type sbt. The script then has a "delete noprompt expired backup;" a "delete noprompt obsolete redundancy = 5;" and finally, a crosscheck;
    example of backup piece that is later deleted:
    Starting backup at 07/18/2006 20:00:14
    channel t1: starting full datafile backupset
    channel t1: specifying datafile(s) in backupset
    including current SPFILE in backupset
    channel t1: starting piece 1 at 07/18/2006 20:00:14
    channel t1: finished piece 1 at 07/18/2006 20:00:15
    piece handle=P*****_2338_1_596145614_FULL comment=API Version 2.0,MMS Version 5.2.0.0
    channel t1: backup set complete, elapsed time: 00:00:01
    Finished backup at 07/18/2006 20:00:15
    deletion:
    Deleting the following obsolete backups and copies:
    Type Key Completion Time Filename/Handle
    <other lines deleted>
    Backup Set 27453 07/18/2006 20:00:14
    Backup Piece 27454 07/18/2006 20:00:14
    P*****_2338_1_596145614_FULL
    deleted backup piece
    backup piece handle=P*****_2338_1_596145614_FULL recid=2039 stamp=596145614
    Deleted 12 objects
    Why is a backup piece created on 7/18 being deleted in the maintenance step?
    Thanks in advance!

    In the next step in the script, the controlfile and spfile are backed up:
    backup
    full
    skip inaccessible
    tag hot_database_backup_full
    format '%d_%s_%p_%t_FULL'
    (Database
    include current controlfile)
    Plus Archivelog delete input;
    Even though my backup script is redundant by backing up the spfile twice, when I list the backup of the spfile, I would have expected to find 5 backups with a tag of hot_database_spfile_backup_full and 5 with a tag of hot_database_backup_full. That is not the case. I only find spfiles with a tag of hot_database_backup_full. i am still perplexed by RMAN.
    I will modify my script - remove the backup of the spfile, and crosscheck before the delete commands. I will also remove the redundancy = 5. The intent is to keep 25 days of backups.
    Thanks for your comments

  • RMAN Recovery window and Redundancy

    Hi,
    I am using Oracle 11g (11.2.0.1) in windows 2003 server. In RMAN is it possible to set both the below mentioned configuration in effect or anyone of the configuration can only be used?
    RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    Regards,
    007

    No it is not possible.
    007 wrote:
    hi oradb,
    Thanks for your reply. i want both the RMAN configuration policy to be applied. Is the possible???
    regards,
    007hi oradb,
    Thanks for your reply. i want both the RMAN configuration policy to be applied. Is the possible???
    regards,
    007

  • RMAN RETENTION POLICY configuration.

    Currently I am doing RMAN backup once a day and save the copy to tapes through TSM. If I want to keep 15 copies of the db (NOT 15 same copies. It will be one copy from every day backup, so each copy will be different). How should I configure the RETENTION POLICY? Shall I do
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 15 DAYS;
    Or shall I do
    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    Also do I need to configure anything on the TSM side?
    Thanks.

    To keep the last 15 full backups use redundancy 15.
    You don't need to do anything on TSM if:
    - you use RMAN to backup directly to tape device and
    - you use RMAN DELETE OBSOLETE statements to purge old backups.
    See http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV8400

  • RMAN Retention Policy Dilemma

    The RECOVERY WINDOW and REDUNDANCY options of the RETENTION POLICY parameter are mutually exclusive. I have to set one or the other. However, if I set REDUNDANCY = 3 and then RECOVERY WINDOW = 21 DAYS, I've been told that the recovery window of 21 days will be enforced and RMAN will keep only 3 backup copies within this window period? Is this correct?
    Can you specify a maximum number of backups to keep within a window period of N amount of days?

    You can not set them both. It is one or the other.
    If you set recovery window = 21 days, then it will keep as many backups as necessary to restore back to 21 days.
    If you set redundany=3, then it will only keep the most recent 3 backups.

  • RMAN Retention Policies

    We are looking for two retention policies for our backups. 30 days retention for all backups on TAPE and 7 days retention on all backups on DISK. If we set retention policy to 30, disk couldn't accommodate all backups on disk at the same time, we need backups on tape for at least 30 days.
    Any ideas?

    You would have some block of code in your script to delete obsolete backups... replace that with two commands (one global and one for disk). You would still have retention policy for 30 days
    RMAN TARGET /
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
    ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE SBT;
    DELETE FORCE NOPROMPT OBSOLETE;
    DELETE FORCE NOPROMPT OBSOLETE RECOVERY WINDOW OF 7 DAYS DEVICE TYPE DISK;

Maybe you are looking for

  • Printing/saving to PDF...  pdf file size is enormous...

    I am trying to convert a psd file that is a 36"X80" banner to a pdf file.  In the past, I have printed to PDF and all has been fine.  Today the Print to PDF fails...  it doesn't give me an error it just pretends like it prints to pdf with the status

  • Perform as pdf form with the ability to insert pictures

    How to perform as pdf form. with the ability to insert pictures?

  • Resizing images in a div to fit browser width

    i have a page with rollovers in a DIV: http://toddheymandirector.com/REEL/index_newlook.html i want the the images, "nike the getaway", etc, to resize to fit the browser window width. i tried putting them in a div and adding row {     max-width: 100%

  • How to use ignore=check_min_mem Command

    Hi Guru's, I was  trying to install Hana on VMware in laptop. But I am having 8GB ram. I heard that ignore=check_min_mem command can be used to skip the check. Can anyone tell me how  to use this command My installation path is  - ./setup.sh /tmp/han

  • Customizing Spry Menu - Drop items different from tabs at the top

    How can I remove the background image from the dropped down items on a Horizontal Spry Menu while keeping the image for the tabs at the top? It seems every time I change something for the top tabs, the change is carried to the drop down menus as well