last available retention policy backup RMAN

Similar Questions

• CONFIGURE REDUNDANCY 0 RETENTION POLICY

  Our 11 g R2 database, here's our RMAN script
  Currently, our retention policy is 1, so 1 backup is kept as well as the current backup.
  I just want to have 1 it is, RMAN backup should I take backup and delete the former bacup.
  Will it work if I change to 0 retention policy?
  

  RUN
  { 
    ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
    ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
    ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
    DELETE NOPROMPT OBSOLETE;
    BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
    SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
    BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
  
  }
  
  RMAN> show all
  2> ;
  
  using target database control file instead of recovery catalog
  CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
  CONFIGURE BACKUP OPTIMIZATION OFF; # default

  Published by: user10243788 on April 24, 2012 01:14

  Not possible, see this

  RMAN > CONFIGURE REDUNDANCY 0 RETENTION POLICY;

  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command configures to 24/04/2012 14:44:33
  RMAN-06532: County of redundancy must be greater than zero

  I just want 1 backup,

  If you run your cmd 'DELETE NOPROMPT OBSOLETE;' after your backup command then it will delete previous backup and keep only 1 backup.

  Thank you
  Christian Christmas Pal Singh

• Backups RMAN does not match its retention policy

  Hello

  I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

  For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

  DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

  I have clear and defined retention to 14 days over policy but doesn't seem to work.

  I would be grateful suggestion (s) about the strange.

  Thank you very much.

  Best regards

  John-MK wrote:

  Hello

  I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

  For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

  DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

  I have clear and defined retention to 14 days over policy but doesn't seem to work.

  I would be grateful suggestion (s) about the strange.

  Thank you very much.

  Best regards

  We would need to know what kind of backups and where they were taken.  Imagine this scenario:

  7-day retention strategy.

  Level 0 incremental backup taken on Sunday

  Backup incremental level 1 taken Monday at Sam.

  Let's say that October 1 is a Sunday, so we take an Inc.-0 backup on October 1 and again on Oct. 8.

  Now let's say that we are at 10 Oct.  Our 7-day retention policy dicatates that we can recover any day of return to 3 Oct.

  The only way we can find to 3 Oct is to start with this backup Inc.-0 Oct. 1.

  Recovery all starts with last Inc.-0 backup before the point in time to be recovered.  In a normal life, regularly cycling calendar of backups, actually will end you with backups 1 day far twice also older than your retention period.

  A more extreme example.  Same period of retention of 7 days, but after a single backup Inc. - 0, you don't take any backups of 3 months.  That only a backup is always necessary to apply your window of recovery and therefore is not obsolete, despite the fact it is 3 months old and your recovery window is 7 days.

  Also, you mention "expiration".  Regarding backups oracle, 'expired' isn't the same as "obsolete".

  "Obsolète" means "is more necessary to apply the principle of recovery."

  "Expired" is a little more complex.

  When a backup is performed, or an archivelog is written, an account of which is written in the repository.  When you do a 'crossover' rman, these repository records are compared to reality - to see if the archivelog or saved backup file actually exists.  Maybe someone used an OS command to delete them.  Any file found "go walkabout" have their directory of files marked as "expired".  An rman "expiration to delete" then delete the records in the repository.

• Problems with the retention policy that removes a Cumulative incremental backup

  Hello

  I have following two scripts:

  1 RMAN script runs the weekend and made a full backup of level 0.

  2 RMAN script works on a daily basis and a level 1 Cumulative backup.

  at the end of each script I delete noprompt obsolete redundancy 1; (I don't need a single copy of local disk)

  My problem is that it seems that remove obsolete handles only level 0 (full) backups.

  for example, my goal is:

  Saturday = > level 0 + delete obsolete (level 0 + all the incremental)

  Sunday = > obsolete level 1 cumulative + delete

  Monday = > level 1 cumulative + Delete obsolete (backup Sunday)

  etc...

  What happens in reality is rather that remove obsolete Monday, completely ignores Sunday 1 cumulative level.

  and he keeps all the up to the next level 0 backup

  its actually covered in the Oracle Documentation:

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV8400

  but it's just not make sense.

  in order to have redundancy of 1 copy I only need to level 0 + unique Level 1 cumulative backup.

  I don't have level 0 + all level 1 cumulative backups between full backups.

  
  

  so my question is there a way to make the retention policy to keep only the last level 1 cumulative?
  

  It's true window of 1 day recovery ignores several backups of cumulativ made the same day as being obsolete. Regular retention strategies rman probably cannot provide what you want. You can manually identify the backupset and delete them or change of cumulativ backups to incremental backups.

  That would save the space of several cumulative backups and and would work even for several backups on the same day. Of course with the disadvantage that you need all of the incremental backups and your recovery time may be longer

• Question on the implementation of the RMAN retention policy

  Version: 11 g
  OPERATING SYSTEM: AIX 5.3
  
  
  I intend to implement a differential incremental backup of my database. My strategy is
  

  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  Tuesday-->     Level 1 backup
  Wednesday-->     Level 1 backup
  Thursday-->     Level 1 backup
  Friday-->     Level 1 backup
  Saturday-->      Level 1 backup
  
  Again, the new weekly backup cycle starts
  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  .
  .

  First script to perform the backup of level 0 - this script will be run by a cron job every Sunday morning 02:00
  ==================================================================

  run{
  crosscheck backup;
  crosscheck archivelog all;
  crosscheck copy;
  crosscheck backup of database;
  crosscheck backup of controlfile;
  delete noprompt obsolete device type disk;
  }
  
  
  run {
  allocate channel ch1 device type disk;
  backup incremental level 0 format '/u07/rman_backup/FULL_%d_%u' database tag "weekly_full";
  backup format '/u07/rman_backup/RMAN_CTL%s:%t:%p.bkp' current controlfile;
  --release channel ch1;
  allocate channel ch1 device type disk;
  backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' DELETE INPUT TAG "archivelogs");
  release channel ch1;
  }

  The second script for differential incremental backup at level 1 for the next 6 days. This script will run every day
  at 02:00 from Monday to Saturday by a cron job. I have 6 scripts like below, the only difference being the tag "Monday-level 1", "Tuesday-level1"... etc.
  =======================================================

  run{
  crosscheck backup;
  crosscheck archivelog all;
  crosscheck copy;
  crosscheck backup of database;
  crosscheck backup of controlfile;
  delete noprompt obsolete device type disk;
  }
  
  
  run {
  allocate channel ch1 device type disk;
  backup incremental level 1 format '/u07/rman_backup/RMAN_DBF_%s:%t:%p.bkp' database tag "Monday-level1";
  backup format '/u07/rman_backup/RMAN_CTL<%s:%t:%p>.bkp' current controlfile;
  --release channel ch1;
  allocate channel ch1 device type disk;
  backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' delete input tag "archivelogs");
  release channel ch1;
  }

  Question1.
  I want to as backups to become obsolete and deleted as below

  At the end of every week's backup cycle.ie Just after taking a new Sunday's level 0 backup, 
  i need all the old level 1 and level 0 backups from the previous week to get deleted.

  The setting persist following should do the trick. Right?

  CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

  Question2.
  Since

  CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

  is defined. When the new backup cycle begins next Sunday, RMAN should delete the backup of level 0 of last Sunday. Ideally, RMAN should remove all its ' (child) of level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and deleted. RMAN removes level 1 level 0 backup child deleted backups Sunday (when the new backup cycle begins)?
  
  Question3:
  Suggestions that you guys have about the scripts above?
  
  Published by: resistanceIsFruitful on October 30, 2009 06:04

  You have answered your question yourself in your question, when you understand

  Ideally RMAN should remove all its ' other (children) level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and removed_

  Yes indeed RMAN done, did you check it yourself?

  Khurram

• RMAN retention policy

  Hello everyone, I think to create a retention policy, but the problem is if I want to have the backup that ran daily from detention for 15 days and each backup run a monthly backup for a year which is the best option to set up the recovery window retention policy, because if I set with 365 days I'm going to keep daily backups for the whole year, suggest or advise

  Hello

  set the retention policy for 15 days (daily policy):

  RMAN > CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 60 DAYS;

  And add keep until 'sysdate + 365' monthly backup.

  RMAN > backup format incremental level 0 '% d.n0.%T.set_%s_%t' TAG data = 'BK_DATA_monthly_20150501' keep until 'SYSDATE + 365' opens a session;

  If you can make backup maintenance with delete obsolete;

  RMAN > remove force noprompt obsolete;

  
  

  It works with oracle 9i, 10g and 11g

• RMAN: Deletion retention policy policy VS Archivelog

  I am a newbie to RMAN, so I did a lot of reading and experimentation, and I'm stuck on a problem.

  TASK: I want to keep two days of archived newspapers and a days worth of backups.

  SOLUTION: set 1 retention policy, set the deletion policy to archive 2

  (CONFIGURE ARCHIVELOG DELETION of SAVED POLICY 2 TIMES TO THE DISK.)

  and it's my simple backup script

  run

  {

  database backup "nightly_backup" tag more archivelog;

  delete noprompt obsolete;

  }

  PROBLEM: it does not work. Oracle documentation clearly (as clearly as possible the documentation) that "remove obsolete" uses the retention policy to clear logs archived. and deletion policy deletion archivelog to use "delete archivelog all;

  My tests verifies this.

  ISSUE. How remove the database obsolete backupsets ONLY by using the delete command?

  -Mark

  Just for clarity - if other people who have this issue will find this thread-I found the answer.

  Two policies are in effect only when you use the quick recovery for all your backup needs area. The database will automatically manage files according to policies. But as soon as you run manually ' rman > delete noprompt obsolete ' Oracle will only follow the retention policy.

  So as soon as FRA got up to about 78 percent full, he began to delete files, you can see in the alert.log

  Deleted Oracle managed file +FRA/sndbox/backupset/2014_07_23/annnf0_nightly_backup_0.435.853650191

  Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_1_seq_204.439.853668327

  Deleted Oracle managed file +FRA/sndbox/autobackup/2014_07_23/s_853650247.441.853650249

  Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_2_seq_189.434.853668653

  Another consequence of this fun is that Oracle will not automatically manage files outside of the FRA. So, if you save FRA on the disk, Oracle removes only files of FRA. If you must manually remove FRA backups, but which will also remove the FRA files according to the retention policies.

• Recovery window retention policy removes the archive logs before backup?

  Hi all

  Oracle 11G on Windows 2008 R2

  This afternoon, I've changed my retention policy RMAN "RETENTION POLICY 3 REDUNDANCY"on RECOVERY WINDOW OF 3 DAYS RETENTION POLICY

  However, I checked tonight and after that my daily backup, all the archive before backup logs had been removed! So that means I don't think I can restore to any point in time, before my daily backup. All newspapers .arc were there after the backup. Then I tried another test and began the daily backup again. During the backup process, archive logs were deleted again! Now, I don't have any archives of newspapers...

  Is this good behavior OF RETENTION POLICY RECOVERY WINDOW? I thought that she would keep all the files needed for to restore me to any point in time for the previous 3 days. When I used a REDUNDANCY, with my daily backups, he kept 3 days of backups + archiving logs so that I could restore point-in-time at any point. How can I use WINDOW RECOVERY so that I can actually restore to any point in time for the 3 days?

  I wanted to change WINDOW of recovery, since I read that using the REDUNDANCY, it keeps only X copy a backup (so if I ran the backup 3 times a day, I would have only these 3).

  Thanks in advance.

  After a database RESTORE, Oracle tries to RECOVER a DATABASE.  He tries to 'find' the archivelogs for this phase in the location expected archivelog.  If they are NOT present in the location expected archivelog, it attempts to restore backups before applying them.

  Since your BACKUP... DELETE ENTRY deletes the archivelogs after that that they are saved, Oracle will have to use backups to recover the archivelogs.

  Hemant K Collette

• backup with the retention policy to recovery of N days window

  Hello

  I did command to create an incremental backup of database with the configuration:

  run

  {

  Configure retention policy to recovery of 14 days window;

  backup incremental level 1 cumulative

  tag daily_incr_14_days

  database

  more archivelog delete all input;

  }

  All parameters are set to their default values, and backups of data goes to FRA. I've got catalog recovery connected and all the views RC_ at my disposal.

  (1) is it possible to know which window of recovery has been used for any command in the rman backup or query view RC_ or local database (control file information)?

  (2) if I use other settings of window of recovery with command configures which would overlap or report rman commands do?

  BR

  Sandrine.

  TenakaKhan wrote:

  Mahir,

  Thanks for the reply - in other words, this window of recovery should be used mainly for maintenance purposes (overlap, remove obsolete, report need backup etc.) and he was not associated with the actual with backup items as retention period "keep until the" safeguard clause... command database (this information are saved with the backup as I could verify according to rc_backup_set of the recovery catalog)?

  Yes.

  Maintaining backups RMAN and repository & nbsp; Reviews

  keepOption

  backup retention policy

  A policy defined by the user to determine how long the backups and archived logs must be kept for the media recovery. You can define a retention policy in terms of redundancy backup or a recovery window.

  RMAN keeps backups of data files that are required to meet the current retention policy, and all logs archived redo necessary to a complete recovery of data files.

  Recovery window

  A recovery window is a type of RMAN backup retention policy, in which the ADMINISTRATOR specifies a period of time and RMAN ensures the retention of backups and Archives redo logs required for recovery to point-in-time at any time during the recovery window.

  The interval always ends at the present time and is extended in time for the number of days specified by the user. For example, if the retention policy is set for a window of recovery of seven days and the current time is 11:00 Tuesday

  RMAN maintains the necessary backups to recover point-in-time at 11:00 the previous Tuesday.

  Concerning

  Mr. Mahir Quluzade

• Query on the RMAN retention policy

  
  Hi, I have my retention set to 2 redundancy policy

  I took 3 backups so far (2 sets of backup, 1 copy of the Image)

  When I check the obsolete report I get the following

  RMAN retention policy apply to the order

  RMAN retention policy is set to 2 redundancy

  Report of obsolete backups and copies

  Making key time filename/handle type

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

  Backup 1 05-SEP-13 set

  Exhibit 1 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp 13-SEP-05

  Backup 2 05-SEPT-13 set

  Exhibit 2 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp 13-SEP-05

  Backup 3 05-SEPT-13 set

  Save the song 3 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp 13-SEP-05

  Backup 4 05-SEPT-13 set

  Save the 4-13-SEVEN piece. 05 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp

  Backup 5 27-SEPT-13 set

  Save the song 5-/home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp 13-SEP-27

  Backup the value 7 13-SEP-27

  Save the song 7 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp 27-SEP-13

  Archive newspaper 305 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc

  Archive newspaper 306 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc

  Archive journal 307 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc

  Archive newspaper 308 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc

  Backup 1,2,3,4 set elements are essentially equivalent to my older backup - so under a redundancy of the 2, I can see why it is obsolete

  5 and 7 were simply command file/SPFILE AutoSave backups and the 2 most recent backups of them have since been taken (backupset parts 9 and 10)

  Q. what happens if I wanted to restore the database to the 27/09? What control and SPFILE he would use (assuming that OBSOLETE files had been removed from the FRA)?

  If I have to restore the backup set removed in the FRA, Cross Check and restore the database using RMAN to 27/09?

  Q. Why are some today (10/10/13) archival newspapers marked OBSOLETE?

  Q. If I wanted to be able to restore the database for 2 days, is perhaps a policy of conservation of a day 2 Recovery window might be better than my current redundancy = 2 policy (associated with a daily backup)?

  any advice appreciated,

  Jim

  Yes, the BackupPieces names.

  A BACKUP of the LIST would show the content of BackupSets and BackupPieces.

  Hemant K Collette

• The Archive Log backup retention policy

  How can I define retention policy for backups of the log of the Archives?

  The question and the answer that you have marked as "Right answer" is misleading.

  For removal of journal policy archived, see below.

  Configuration of RMAN environment

  For the real question displayed "How can I define retention policy for backups of the log of the archives?", see link below. ""

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318

  Also, have you started the thread to clear your doubts or test other users of the forum?

  Thank you!!

• The front last backup RMAN delete file even if redundancy on 3 days

  Dear Oracle gurus
  
  My environment
  Node 2 11g R2 Cluster with ASM
  Database 11.2.0.3.0
  
  I got to know that file below is delete by RMAN even if redundancy on 3 days
  * 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 * is removed
  
  can you please provide a reason or recommendations to correct the backup configuration
  
  =========Before Backup========================================
  917M rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
  Rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 669M
  Rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 101M
  64M rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
  116M rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
  Rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 85M
  1003M rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
  689M rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
  87M rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
  Rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013 73M
  110M rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
  Rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013 103M
  115M rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
  88M rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
  1011M rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
  701M rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
  226M rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
  215M rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
  * 230M rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
  * 568M rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
  * 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
  ===========================================================================
  
  ===================After Backup========================================================
  -rw - r - 1 oracle oinstall 1049755648 12 May 20:05 rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
  -rw - r - 1 oracle oinstall 720715776 12 May 20:05 rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
  -rw - r - 1 oracle oinstall 91013120 13 May 20:05 rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
  -rw - r - 1 oracle oinstall 75726848 13 May 20:05 rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
  -rw - r - 1 oracle oinstall 114327552 14 May 20:05 rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
  -rw - r - 1 oracle oinstall 107782144 14 May 20:05 rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
  -rw - r - 1 oracle oinstall 120307712 15 May 20:05 rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
  -rw - r - 1 oracle oinstall 91226112 15 May 20:05 rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
  -rw - r - 1 oracle oinstall 1058840576 16 May 20:05 rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
  -rw - r - 1 oracle oinstall 733757440 16 May 20:05 rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
  -rw - r - 1 oracle oinstall 236716032 17 May 20:05 rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
  -rw - r - 1 oracle oinstall 224174080 17 May 20:05 rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
  -rw - r - 1 oracle oinstall 594411520 18 May 20:06 rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
  -rw - r - 1 oracle oinstall 240123904 18 May 20:06 rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
  -rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
  -rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
  -rw - r - 1 oracle oinstall 254590976 19 May 20:06 rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
  -rw - r - 1 oracle oinstall 709885952 19 May 20:07 rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
  -rw - r - 1 oracle oinstall 19234816 19 May 20:07 rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
  ==================================================================================
  
  
  Configuration of RMAN
  bash-$3.2 rman target /.
  
  Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 14:34:26 2013
  
  Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
  
  connected to target database: ORCL (DBID = 3171721304)
  
  RMAN > show all.
  
  using the control file of the target instead of recovery catalog database
  RMAN settings for database with db_unique_name ORCLDR are:
  CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
  CONFIGURE BACKUP OPTIMIZATION
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcldr2.f'; # by default
  
  RMAN > exit
  =========================================================================================
  RMAN Full Backup Script
  RMAN level 0
  #! / bin/bash
  . /Home/Oracle/.bash_profile
  logloc = 'date' + rman_backup_lvl0_orcldr_ %m %y hour %M %S %d ".log
  Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
  run
  {
  allocate channels ch1 type disk maxpiecesize = 1024 M;
  allocate channel ch2 type disk maxpiecesize = 1024M;
  database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
  include current controlfile more archivelog delete all entries
  tag 'datafile_full ';
  }
  delete noprompt obsolete;
  EXIT;
  EXPRESSIONS OF FOLKLORE
  =========================================================================================
  
  Backup logs
  -bash-3, $ 2 cat rman_backup_lvl0_ORCLdr_190513200501.log
  
  Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 20:05:01 2013
  
  Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
  
  connected to target database: ORCL (DBID = 3171721304)
  
  RMAN >
  RMAN > 2 > 3 > 4 > 5 > 6 > 7 > 8 >
  using the control file of the target instead of recovery catalog database
  allocated channel: ch1
  channel ch1: SID = instance 1753 = ORCLdr2 = DISK device type
  
  allocated channel: ch2
  channel ch2: SID = 5 = device type ORCLdr2 = DISK instance
  
  
  From backup may 19, 13
  Current archived log
  archived journal of wire 1 to jump with sequence 84; already saved
  skip the journal archived thread 2 with sequence 79; already saved
  channel ch1: Startup archived log backup set
  channel ch1: specifying the newspapers archived in the backup set
  archived journal entry thread = 2 sequence = 81 RECID = 388 STAMP = 815810424
  archived journal entry thread = 1 sequence = 85 RECID = 385 STAMP = 815793508
  archived journal entry thread = 1 sequence = 86 RECID = 389 STAMP = 815810426
  archived journal entry thread = 1 sequence = 87 RECID = 391 STAMP = 815828071
  channel ch1: from room 1 to May 19, 13
  channel ch2: Startup archived log backup set
  channel ch2: specifying the newspapers archived in the backup set
  archived journal thread = sequence 2 = 82 entry RECID = 396 STAMP = 815861105
  archived journal entry thread = 1 sequence = 88 RECID = 393 = 815846442 STAMP
  archived journal entry thread = 1 sequence = 89 RECID = 397 STAMP = 815861108
  channel ch2: from room 1 to May 19, 13
  channel ch1: finished piece 1 to May 19, 13
  piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
  channel ch1: from part 2 to May 19, 13
  channel ch2: finished piece 1 to May 19, 13
  piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
  channel ch2: from part 2 to May 19, 13
  channel ch1: finished part 2 to May 19, 13
  piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
  channel ch1: from 3 to 19 May 13 piece
  channel ch2: finished part 2 to May 19, 13
  piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
  channel ch2: complete set of backups, time: 00:01:10
  channel ch2: archived deletion or newspapers
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_82_814540431.arc RECID archived log file = 396 STAMP = 815861105
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_88_814540431.arc RECID archived log file = 393 = 815846442 STAMP
  RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
  Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_89_814540431.arc thread = 1 sequence = 89
  channel ch2: archived deletion or newspapers
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_84_814540431.arc RECID archived log file = 383 STAMP = 815774802
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_79_814540431.arc RECID archived log file = 378 STAMP = 815774705
  channel ch1: finished part 3 to 19 May 13
  piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_3_1 tag = DATAFILE_FULL comment = NONE
  channel ch1: complete set of backups, time: 00:01:25
  channel ch1: archived deletion or newspapers
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_81_814540431.arc RECID archived log file = 388 STAMP = 815810424
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_85_814540431.arc RECID archived log file = 385 STAMP = 815793508
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_86_814540431.arc RECID archived log file = 389 STAMP = 815810426
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_87_814540431.arc RECID archived log file = 391 STAMP = 815828071
  Backup finished on 19 May 13
  
  From backup may 19, 13
  channel ch1: start the incremental level 0 datafile backup set
  channel ch1: specification-datafile in the backup set (s)
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_5.dbf 00009
  Enter a number of file datafile = 00001 name=+ORASYS/ORCLdr/datafile/system.257.814500985
  Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/undotbs1.259.814500991 00003
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app2.dbf 00006
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app.dbf 00008
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users01.dbf 00011
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users03.dbf 00013
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users05.dbf 00015
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users07.dbf 00017
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_5.dbf 00019
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_7.dbf 00021
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_9.dbf 00023
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_11.dbf 00025
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdrmaxdat.dbf 00027
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradcdr.dbf 00029
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_8.dbf 00031
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_10.dbf 00033
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_5.dbf 00037
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_7.dbf 00039
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_9.dbf 00041
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_11.dbf 00043
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdrmaxdat.dbf 00045
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradinterimcdr.dbf 00047
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/reports.dbf 00048
  channel ch1: from room 1 to May 19, 13
  channel ch2: start the incremental level 0 datafile backup set
  channel ch2: specification-datafile in the backup set (s)
  Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/sysaux.256.814500977 00002
  Enter a number of file datafile = 00005 name=+ORASYS/ORCLdr/datafile/undotbs2.258.814500987
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/namestatistics.dbf 00035
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/gidstatistics.dbf 00036
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/stat01.dbf 00007
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_6.dbf 00010
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users02.dbf 00012
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users04.dbf 00014
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users06.dbf 00016
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users08.dbf 00018
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_6.dbf 00020
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_8.dbf 00022
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_10.dbf 00024
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_12.dbf 00026
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/unameradcdr.dbf 00028
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_7.dbf 00030
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_9.dbf 00032
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statisticsmaxdate.dbf 00034
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radintdr2013_6.dbf 00038
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radiusintcdr2013_8.dbf 00040
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radinterimcdr2013_10.dbf 00042
  Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/tb2013_12.dbf 00044
  Enter a file datafile 00046 name=+ORADATA1/ORCLdr/datafile/tberimcdr.dbf = number
  Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/users.260.814500995 00004
  channel ch2: from room 1 to May 19, 13
  channel ch1: finished piece 1 to May 19, 13
  total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
  channel ch1: from part 2 to May 19, 13
  channel ch2: finished piece 1 to May 19, 13
  total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
  channel ch2: from part 2 to May 19, 13
  channel ch1: finished part 2 to May 19, 13
  total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
  channel ch1: complete set of backups, time: 00:00:22
  channel ch1: start the incremental level 0 datafile backup set
  channel ch1: specification-datafile in the backup set (s)
  channel ch2: finished part 2 to May 19, 13
  total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
  channel ch2: complete set of backups, time: 00:00:22
  including the current control in the backup set file
  channel ch1: from room 1 to May 19, 13
  channel ch1: finished piece 1 to May 19, 13
  total, handle = / backup/RMAN_Backup/rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
  channel ch1: complete set of backups, time: 00:00:01
  Backup finished on 19 May 13
  
  From backup may 19, 13
  Current archived log
  channel ch1: Startup archived log backup set
  channel ch1: specifying the newspapers archived in the backup set
  archived journal entry thread = 2 sequence = 83 RECID = 399 STAMP = 815861227
  channel ch1: from room 1 to May 19, 13
  channel ch2: Startup archived log backup set
  channel ch2: specifying the newspapers archived in the backup set
  archived journal entry thread = 1 sequence = 90 RECID = 401 STAMP = 815861227
  channel ch2: from room 1 to May 19, 13
  channel ch1: finished piece 1 to May 19, 13
  piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/47oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
  channel ch1: complete set of backups, time: 00:00:01
  channel ch1: archived deletion or newspapers
  name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_83_814540431.arc RECID archived log file = 399 STAMP = 815861227
  channel ch2: finished piece 1 to May 19, 13
  piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/48oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
  channel ch2: complete set of backups, time: 00:00:01
  channel ch2: archived deletion or newspapers
  RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
  Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_90_814540431.arc thread = 1 sequence = 90
  Backup finished on 19 May 13
  
  From control file and SPFILE Autobackup 19 May 13
  room handle=/u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130519-00 comment = NONE
  File control finished and Autobackup SPFILE to 19 May 13
  output channel: ch1
  output channel: ch2
  
  RMAN >
  RMAN >
  RMAN retention policy apply to the order
  RMAN retention policy is set to 3 redundancy
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = instance 1753 = ORCLdr2 = DISK device type
  Remove the following obsolete backups and copies:
  Making key time filename/handle type
  -------------------- ------ ------------------ --------------------
  8 4 may control file copy 13 /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f
  Game save 40 9 May 13
  Save the piece 40 9 May 13/backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
  Save game 39 may 9, 13
  Save the song 39 9 May 13/backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
  Backs up the entire 42 9 May 13
  Backup total 42 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1mo97nkl_1_1
  Backs up the entire 43 9 May 13
  Backup total 43 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1no97nkl_1_1
  Save game 46 may 10, 13
  Backup total 46 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1po9abvp_1_1
  Game backup 45 may 10, 13
  Backup total 45 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1qo9abvp_1_1
  Save game 47 10 May 13
  Save room 47 10 May 13/backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
  Backs up the entire 48 may 10, 13
  Save the piece 48 10 May 13/backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
  Backs up the entire 50 10 May 13
  Backup total 50 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1uo9ac0l_1_1
  Backs up the entire 51 may 10, 13
  Backup total 51 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1vo9ac0l_1_1
  Backs up the entire 54 may 11, 13
  Backup total 54 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/21o9d0bi_1_1
  Save game 53 may 11, 13
  Backup total 53 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/22o9d0bi_1_1
  Save game 55 may 11, 13
  Save the piece 55 may 11, 13/backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
  Backs up the entire 56 may 11, 13
  Save the song 56 11 May 13/backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
  Backs up the entire 58 may 11, 13
  Backup total 58 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/26o9d0cj_1_1
  Save game 59 may 11, 13
  Backup total 59 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/27o9d0cj_1_1
  Backs up the entire 62 12 May 13
  Backup total 62 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/29o9fknp_1_1
  Save game 61 12 May 13
  Backup total 61 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/2ao9fknp_1_1
  Save game 77 14 May 13
  Backup total 77 14 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00
  Game backup 101 16 May 13
  Backup total 101 16 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130516-00
  Backs up the entire 114 18 May 13
  Save the song 117 may 18, 13/backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
  remove the item from backup
  backup piece handle = / backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = 40 STAMP = 814997122
  remove the item from backup
  backup piece handle = / backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = STAMP 39 = 814997122
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1mo97nkl_1_1 element of backup RECID = STAMP 42 = 814997141
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1no97nkl_1_1 element of backup RECID = STAMP 43 = 814997141
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1po9abvp_1_1 element of backup RECID = STAMP 46 = 815083513
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1qo9abvp_1_1 element of backup RECID = STAMP 45 = 815083514
  remove the item from backup
  backup piece handle = / backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = STAMP 47 = 815083522
  remove the item from backup
  backup piece handle = / backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = 48 STAMP = 815083522
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1uo9ac0l_1_1 element of backup RECID = STAMP 50 = 815083541
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1vo9ac0l_1_1 element of backup RECID = STAMP 51 = 815083541
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/21o9d0bi_1_1 backup RECID piece = 54 STAMP = 815169906
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/22o9d0bi_1_1 element of backup RECID = STAMP 53 = 815169906
  remove the item from backup
  backup piece handle = / backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 55 = 815169915
  remove the item from backup
  backup piece handle = / backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 56 = 815169917
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/26o9d0cj_1_1 element of backup RECID = STAMP 58 = 815169939
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/27o9d0cj_1_1 element of backup RECID = 59 STAMP = 815169939
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/29o9fknp_1_1 element of backup RECID = 62 STAMP = 815256313
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/2ao9fknp_1_1 backup RECID piece = 61 = 815256313 STAMP
  remove the item from backup
  handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/c-3171721304-20130516-00 element of backup RECID = 101 STAMP = 815601943
  remove the item from backup
  backup piece handle = / backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 RECID = 117 STAMP = 815774800
  20 objects deleted
  
  RMAN-06207: WARNING: 2 items could not be removed for DISC due channels
  RMAN-06208: status do not match. Use the OVERLAP command to set status
  RMAN-06210: list of relevant objects
  RMAN-06211: =.
  RMAN-06212: filename/Type object Handle
  RMAN-06213: --------------- ---------------------------------------------------
  RMAN-06214: copy of the data /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f file
  RMAN-06214: /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00 piece of backup
  
  
  RMAN >
  RMAN >
  
  Complete recovery manager.
  -bash - $3.2
  
  Concerning
  Hitgon
  
  Published by: hitgon on May 20, 2013 02:09
  
  Published by: hitgon on May 20, 2013 02:15

  It contained a real data file? Or was it a backup controlfile? A backup controlfile may be outdated if another backup controlfile does not capture the same information it contains.

  Hemant K Collette

• RMAN-05021 configuration pending retention policy

  Hi all.
  
  Running Oracle on Linux (x 64) 11.2.0.2; single node instance.
  
  We have the following configuration:
  
  bvlive (PRIMARY)
  bvstby2 (STANDBY)
  
  We currently have a 21-day retention policy, and backup on the waiting space begins to be a problem.
  
  At first, I thought I could reconfigure this on the day before - but RMAN will not allow this:
  
  STANDBY TIME:

  RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 days;
  
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of configure command at 10/15/2012 10:09:50
  RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file

  Which makes sense when I think about it. I saw this thread retention policy is not configured , but get different results:
  
  PRIMARY:

  RMAN> configure retention policy to recovery window of 14 days;
  
  old RMAN configuration parameters:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
  new RMAN configuration parameters:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
  new RMAN configuration parameters are successfully stored
  
  RMAN> show all;
  
  RMAN configuration parameters for database with db_unique_name BVLIVE are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;

  STANDBY TIME:

  RMAN> SHOW ALL;
  
  RMAN configuration parameters for database with db_unique_name BVSTBY2 are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;

  Which also makes sense; so I am not the original poster solved his problem. I saw a few discussions about this which involve:
  
  1. standby stop
  2. on the primary retention policy configuration
  3. take a backup controlfile elementary school
  4 copy transversely to the waiting
  5 restart the day before using backup controlfile
  
  But then, this seems to be for the CAR, which we do not.
  
  It dawned on me that I can use the option KEEP until when you take backups, but encountered; ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST attrbuts Dungeon (i.e. I can't use DUNGEON and store the backups in the FRA).
  
  Can someone please advise on the best way to go down the retention period in the waiting, ideally without having to rebuild the day before from scratch?
  
  Thank you
  Ray
  
  Published by: ray_h on October 15, 2012 03:33

  Take a look at this http://asanga-pradeep.blogspot.com/2011/07/changing-backup-policy-on-standby-db.html

  It could be that useful...

• Help remove backups rman (delete the repository)

  Hi all.

  I will soon be administering a few databases Oracle (11g Rel2). Currently these DBs area in log mode archive with a backup rman in place policy.

  
  

  I don't like this policy and you want to use my own, incremental backups from updadateable, so this is the plan I have in mind.

  
  

  (1) disable mode archive.

  
  

  (2) a clean shutdown and take a backup to cold.

  
  

  (3) since after you disable archiving, backups RMAN ALL will be unusable, I want to remove them (including newspapers archive and backup sets).

  
  

  (4) after the correct deletion, set up some persistent RMAN settings, such as retention policy, controlfile autobackup and optimization.

  
  

  (5) turn on archiving

  
  

  (6) to set up the new policy based backups backup incremental updateable with duplex location for archiving logs.

  
  

  Help is requested on the best way to clean all the backups (3).

  
  

  I can manually delete the backups and do overlap, but according to the Oracle Documentation "Delete backup" will be delete all backups for data recorded in the RMAN Repository.

  
  

  So which is the best way easier and faster? Will delete backup include the archive logs?

  
  

  Thanks in advance. Luis!

  
  

  myluism wrote:

  Can I still use them?

  I would say it is "the wrong answer to evil. When you disable log mode archive, you can only back up the database when it is stopped and only to restore and recover the database until the last stop.

  Looking at your plan, I wonder what you are trying to accomplish first log mode archive disabling and then enabling archive mode log again. Why do you think that this is necessary and what you're trying to accomplish.

  You need not disable and enable log mode archive in order to eliminate the obsolete achivelogs.

  If you are not satisfied with the retention policy, simply change it. All backups that are outside your retention policy will be considered as obsolete and you can remove them using RMAN delete obsolete, which will remove all files as well as the appropriate data backup from the RMAN Repository.

  For example you can archivelog delete all the entries backup and then delete the backupset or remove them at the OS level, do overlap and then use delete noprompt expired archivelog all.

  The retention policy applies to backup and archivelogs. However, you can have a separate archivelog deletion policy that applies to archivelogs.

• Retention policy

  We had a database of Oracle 9i, configured with a Hot Standby. For the moment, we have the following rman script, configured to run every night at 22:00:
  Run {}
  backup database;
  delete noprompt archivelog all completed before ' SYSDATE-7 ";
  delete noprompt backupset completed before "Trunc (sysdate);
  }
  By separate thread, I realized that "backup database" should be replaced by 'backup database more archivelog' however I am also considering the component to delete.
  My idea is that I still want to have a value of weeks of recovery archived newspapers available on the machine, just in case the emergency breaks down and in addition at least a full backup of database available online at any time.
  My understanding is that the script above should be secure, as if the backup database should fail, the next steps would not run. However in reviewing it I'm afraid we have a case where the backup ends just before midnight, causing the backup finished just to be deleted.
  I know that I can change the "TRUNC(SYSDATE-2/24)", but I wonder if there is a cleaner to do this way?
  What I think I want is a retention policy of 1 OBSOLETE on database backups, but a WINDOW OF 7 DAYS on the archived redo logs. However, I understand that the same retention policy should apply to these two newspapers of recovery and that the two options are mutually exclusive.
  Any thoughts on the issue of whether what I'm trying to achieve is logical, and if so how I can best achieve this?

  PatHK wrote:
  OK, thanks, but as I am running Oracle 9i for now, you are able to comment first find out if it makes sense for me to keep a value a week of archived redo logs and the most recent full backup and also whether the script below every night at 22:00 is the best way to do this?

  Run {}
  backup database archivelog;
  delete noprompt archivelog all completed before ' SYSDATE-7 ";
  delete noprompt backupset completed before "TRUNC(SYSDATE-2/24)";
  }

  It depends on your backup strategy. You can automatically delete all archive redo log files that were created 7 days ago
  But if you

  -Save all the archived redo log files using any backup of database
  -Have Standby database which keeps even long archived redo log file when it is created

  so why keep a value of 7 days to restore archived log files? What is the meaning behind this policy?

  The following script will delete backupsets that were created two days ago