ARCHIVE NEWSPAPER DELETTION POLICY

Similar Questions

• Archive log deletion policy explanation

  How can the archived logs are deleted automatically by the database? I don't get it...
  
  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#CHDCFHBG
  
  I quote:
  
  Archived recovery logs can be deleted automatically by the database or RMAN command initiated by the user. Only newspapers in the field of quick recovery can be deleted automatically by the database.
  
  When that will happen? Without RMAN?
  
  Any ideas?

  Hello;

  If you use FRA as destination for you archive logs they will get deleted until the following conditions:

  1. If there is pressure of space in the flash recovery area (Oracle decides)

  2. what policy of removal of rman archive log is configured.

  3. when the recovery window retention policy is configured and when all unwanted archives are saved.

  Here, there is a short note which will help you understand:

  http://www.oraclefaq.NET/2007/10/18/archive-log-automatically-getting-deleted-from-Oracle-10G-database-with-OMF/

  This can also help:

  http://docs.Oracle.com/CD/B19306_01/backup.102/b14192/rpfbdb001.htm

  http://umardba.blogspot.com/2010/03/maintenance-of-archivelogs-on-standby.html

  Best regards

  mseberg

• Archive deletion policy journal

  Hello everyone,

  I configured the custody of data with oracle 11g with 2 databases on hold.

  I use rman in one of the servers (stb1) Eve to make backups.

  Can sb help me how to configure rman to delete archive logs when it is applied to all the sleep AND when they are backed up at least once in the reserve where the backups are performed.

  Thank you

  Hello

  You can run the command to do this below. The test that it can work.

  that you do not use FRA, oracle will not delete archives automatically

  in primary education

  RMAN > CONFIGURE ARCHIVELOG DELETION POLICY APPLIED TO ALL STANDBY;

  Standby mode

  When you do a backup

  RMAN > CONFIGURE ARCHIVELOG DELETION POLICY NONE;

  DELETE archivelog until 'sysdate-2/24' time saved 1 time to the device type sbt;

  Standby mode when you just want to apply:

  RMAN > CONFIGURE ARCHIVELOG DELETION POLICY NONE;

  DELETE archivelog until 'sysdate-2/24;

  If some records are not applied, those who will not be deleted... you can test

  Thank you

• Newspaper archive automatically deleted

  Hello
  
  My archive logs is deleted automatically from the ASM. I keep my archive logs in FRA. My alert log shows the destruction like this:
  

  Deleted Oracle managed file +DATA1/orcl/archivelog/...

  To recovery window retention policy is set to 24 days. The + DATA1 ASM drive has plenty of free space. ARCHIVELOG deletion policy is set to None, and I'm not running removal of archive of rman too...
  Y at - it another option, I have to check?

  See Bug # 4911954
  (Note to support #4911954.8)

  Compare the contents of V$ FLASH_RECOVERY_AREA_USAGE and V$ RECOVERY_FILE_DEST

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• ARCHIVELOG deletion policy vs v$ flash_Recovery_Area_usage - delicate...

  Hi all

  Reading of

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10643/rcmsynta016.htm#RCMRF121

  DELETE ARCHIVELOG ALLconsiders that the deletion of archived newspaper policy

  
  

  Reading on archivelog deletion policy

  Only newspapers in the field of quick recovery can be deleted automatically by the database.
  When the deletion policy is set on NONE , RMAN considers archived redo log files as eligible for deletion if they meet both of the following
  

  
  -The archive redo logs, whether in or outside of it, fast recovery area have been transferred to remote required destinations specified byLOG_ARCHIVE_DEST_n

  
  

  -Log redo archived in the area of fast recovery, files have been saved at least once to the disk or SBT or newspapers are obsolete according to the backup retention policy.

  The esteem newspapers backup retention policy obsolete If newspapers are needed by a guaranteed restore not point and that newspapers are not required by Flashback Database

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

  LOG_ARCHIVE_DEST_1 Q1) is configured to use 'db_recovery_file_dest' and archivelogs are kept here-> I have meet the #1 condition?

  Q2) I have a retention policy recovery backup window 1 day and I haven't done ANY backup at all yet. I don't have a flashback database, or doesn't I created a ganrantee restore point - I meet the #2 condition?

  
  Q3) I am able to issue "delete archivelog all ', what does that say I satisfy the condition #1 and #2 and the archivelogs are eligible for deletion?

  Q4) if above is a Yes, and with newspapers in fast recovery area may be removed automatically-> why is he in V$ FLASH_RECOVERY_AREA_USAGE, 'PERCENT_SPACE_RECLAIMABLE' always show 0 for the log archiving?

  I thought that the space which are recyclable are files that are eligible for deletion
  ?

  Kind regards

  Noob

  So, this giving some more thought and reading the documentation again. I conclude the following:

  The confusion might be in the context of "eligible for deletion" and management of automatic space of files inside the fast recovery area.

  If the Archivelog deletion policy is set to 'none', then delete archivelog all the will remove all archivelogs, without worrying. Otherwise, the archivelogs policy are not deleted.

  According to the documentation:

  
  

  DELETE ARCHIVELOG ALL considers only the deletion of archived newspaper policy and does not take into account the configured retention policy.

  Everything under "eligible for deletion" applies to the space management FRA, who considers the RMAN retention policy and, as far as I understand it, also believes the Archivelog deletion policy when it is not set to 'none '.

  Archive redo log deletion policy is set to NONE by default. In this case, RMAN considers archived redo log files in the recovery area as eligible for deletion if they fulfill the following two conditions:

  • The archived redo logs, whether in the flash recovery area or outside of it, have been transferred to the required remote destinations specified by LOG_ARCHIVE_DEST_ n .
  • Archived recovery logs have been saved at least once to the disk or SBT or newspapers are obsolete according to the backup retention policy.

  Regarding your recoverable space issue... If you have access to MOS, I suggest to see Doc ID 315098.1.

  What I take from this document, is that archivelogs are included in the column SPACE RECUPERABLE if the free space of FRA becomes less then 15% and the archivelogs are not required by the current backups. Or, archivelogs were saved and not deleted.

• Archive newspaper vs. Full Backup Concept

  Hello
  
  I just need some clarification on how backups and Archives Records work. Lets say from 13:00 I have archive records 1,2,3,4,5 and then I perform a full backup at 18:00.
  
  I take then generate logs archiving at 18:00 to get newspapers 6,7,8,9,10. Then, I stop at 23:00.
  
  If my interpretation is correct, the archive logs should allow me to restore oracle to a point in time anywhere between 13:00 and 23:00. But if I have only the full backup, then I can only restore to a single point, which is from 18:00. My understanding is correct?
  
  Archive logs only applied to data files during backup or only during a restore? There is no archive newspaper applied on the fly.
  
  Thanks in advance.

  thelok wrote:
  Thanks for the great explanation! If I can do a restore time to any time point since the data changed files have been written (or when I have the last set of data files backed up more archive logs). What you say, I can force the data files to write about recovery logs (by a control point with 'alter set archive current log' or 'backup database more archivelog'), and then I can delete all archive logs have an SCN less than the SNA control point on the data files. Is this true? It would be for the purpose of preservation of disk space.

  Hello

  See this example. I hope this explains your doubt.

  # My current date is 06-11-2011 17:15
  # I not have backup of this database
  # My retention policy is to have 1 backup 
  
  # I start listing  archive logs.
  RMAN> list archivelog all;
  
  using target database control file instead of recovery catalog
  
  List of Archived Log Copies
  Key     Thrd Seq     S Low Time            Name
  ------- ---- ------- - ------------------- ----
  29      1    8       A 29-10-2011 12:01:58 +HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837
  30      1    9       A 31-10-2011 23:00:30 +HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025
  31      1    10      A 03-11-2011 23:00:23 +HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105
  32      1    11      A 04-11-2011 23:28:23 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065
  33      1    12      A 05-11-2011 23:28:49 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349
  
  ## See I have archive logs from time "29-10-2011 12:01:58" until "05-11-2011 23:28:49" but I dont have any backup of database.
  
  # So I perfom backup of database including archive logs.
  
  RMAN> backup database plus archivelog delete input;
  
  Starting backup at 06-11-2011 17:15:21
  
  ## Note above RMAN forcing archive current log, this archivelog generated will be usable only for previous backup.
  ## Is not my case... I don't have backup of database.
  
  current log archived
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid=159 devtype=DISK
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=8 recid=29 stamp=766018840
  input archive log thread=1 sequence=9 recid=30 stamp=766278027
  input archive log thread=1 sequence=10 recid=31 stamp=766366111
  input archive log thread=1 sequence=11 recid=32 stamp=766516067
  input archive log thread=1 sequence=12 recid=33 stamp=766516350
  input archive log thread=1 sequence=13 recid=34 stamp=766516521
  channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:23
  channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:15:38
  piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 tag=TAG20111106T171521 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=+HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837 recid=29 stamp=766018840
  archive log filename=+HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025 recid=30 stamp=766278027
  archive log filename=+HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105 recid=31 stamp=766366111
  archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065 recid=32 stamp=766516067
  archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349 recid=33 stamp=766516350
  archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_13.414.766516521 recid=34 stamp=766516521
  Finished backup at 06-11-2011 17:15:38
  
  ## RMAN finish backup of Archivelog and Start Backup of Database
  ## My backup start at "06-11-2011 17:15:38"
  
  Starting backup at 06-11-2011 17:15:38
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting full datafile backupset
  channel ORA_DISK_1: specifying datafile(s) in backupset
  input datafile fno=00001 name=+HR/dbhr/datafile/system.386.765556627
  input datafile fno=00003 name=+HR/dbhr/datafile/sysaux.396.765556627
  input datafile fno=00002 name=+HR/dbhr/datafile/undotbs1.393.765556627
  input datafile fno=00004 name=+HR/dbhr/datafile/users.397.765557979
  input datafile fno=00005 name=+BFILES/dbhr/datafile/bfiles.257.765542997
  channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:39
  channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:03
  piece handle=+FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539 tag=TAG20111106T171539 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:24
  Finished backup at 06-11-2011 17:16:03
  
  ## And finish at "06-11-2011 17:16:03", so I can recovery my database from this time.
  ## I will need archivelogs (transactions) which was generated during backup of database.
  ## Note during backup some blocks are copied others not. The SCN is inconsistent state.
  ## To make it consistent I need apply archivelog which have all transactions recorded.
  
  ## Starting another backup of archived log generated during backup.
  Starting backup at 06-11-2011 17:16:04 
  
  ## So automatically RMAN force another "checkpoint" after backup finished,
  ## forcing archive current log, because this archivelog have all transactions to bring database in a consistent state.
  
  current log archived
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=14 recid=35 stamp=766516564
  channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:16:05
  channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:06
  piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565 tag=TAG20111106T171604 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_14.414.766516565 recid=35 stamp=766516564
  Finished backup at 06-11-2011 17:16:06
  
  ## Note: I can recover my database from time "06-11-2011 17:16:03" (finished backup full)
  ##  until "06-11-2011 17:16:04" (last archivelog generated) that is my recover window in this scenary.
  
  ## Listing Backup I have:
  ## Archive Logs in backupset before backup full start - *BP Key: 40*
  ## Backup Full database in backupset - *BP Key: 41*
  ##  Archive Logs in backupset after backup full stop - *BP Key: 42*
  
  RMAN> list backup;
  
  List of Backup Sets
  ===================
  
  BS Key  Size       Device Type Elapsed Time Completion Time
  ------- ---------- ----------- ------------ -------------------
  40      196.73M    DISK        00:00:15     06-11-2011 17:15:37
          *BP Key: 40*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171521
          Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
  
    List of Archived Logs in backup set 40
    Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
    ---- ------- ---------- ------------------- ---------- ---------
    1    8       766216     29-10-2011 12:01:58 855033     31-10-2011 23:00:30
    1    9       855033     31-10-2011 23:00:30 896458     03-11-2011 23:00:23
    1    10      896458     03-11-2011 23:00:23 937172     04-11-2011 23:28:23
    1    11      937172     04-11-2011 23:28:23 976938     05-11-2011 23:28:49
    1    12      976938     05-11-2011 23:28:49 1023057    06-11-2011 17:12:28
    1    13      1023057    06-11-2011 17:12:28 1023411    06-11-2011 17:15:21
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ -------------------
  41      Full    565.66M    DISK        00:00:18     06-11-2011 17:15:57
          *BP Key: 41*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171539
          Piece Name: +FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539
    List of Datafiles in backup set 41
    File LV Type Ckp SCN    Ckp Time            Name
    ---- -- ---- ---------- ------------------- ----
    1       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/system.386.765556627
    2       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/undotbs1.393.765556627
    3       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/sysaux.396.765556627
    4       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/users.397.765557979
    5       Full 1023422    06-11-2011 17:15:39 +BFILES/dbhr/datafile/bfiles.257.765542997
  
  BS Key  Size       Device Type Elapsed Time Completion Time
  ------- ---------- ----------- ------------ -------------------
  42      3.00K      DISK        00:00:02     06-11-2011 17:16:06
          *BP Key: 42*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171604
          Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565
  
    List of Archived Logs in backup set 42
    Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
    ---- ------- ---------- ------------------- ---------- ---------
    1    14      1023411    06-11-2011 17:15:21 1023433    06-11-2011 17:16:04
  
  ## Here make sense what I trying explain
  ## As I don't have backup of database before of my Last backup, all archivelogs generated before of my backup full is useless.
  
  ## Deleting what are obsolete in my env, RMAN choose backupset 40 (i.e all archived logs generated before my backup full)
  
  RMAN> delete obsolete;
  
  RMAN retention policy will be applied to the command
  RMAN retention policy is set to redundancy 1
  using channel ORA_DISK_1
  Deleting the following obsolete backups and copies:
  Type                 Key    Completion Time    Filename/Handle
  -------------------- ------ ------------------ --------------------
  *Backup Set           40*     06-11-2011 17:15:37
    Backup Piece       40     06-11-2011 17:15:37 +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
  
  Do you really want to delete the above objects (enter YES or NO)? yes
  deleted backup piece
  backup piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 recid=40 stamp=766516523
  Deleted 1 objects
  

  In the example above, I could before running Backup "archivelog all delete" because they are not necessary, but as an example, I followed this unnecessarily. (archivelog backup and deletion after)

  Kind regards
  Levi Pereira

  Published by: Levi Pereira on November 7, 2011 01:02

• Data Guard archive political deletion log

  Hi all

  I configured the data guard with 2 bases Eve in oracle 11g.

  I want to use rman to delete archives on all servers.

  I have configured no FRA, no recovery catalog.

  My question is:

  If I delete waiting til sequence # 1627 and on primary sequence til = # = 1620 or vice versa this would cause problems for Data Guard.

  I say delete until the different sequences # on primary and standby cause problems for synchronization?

  Thank you

  So if I understand delete archivelog to sysdate - or delete archivelog all completed before sysdate n is not the archivelog deletion policy you put on RMAN?

  She depends on it. The note was made at the base of the MOS document how ensure that RMAN is NOT delete archived logs that have not yet shipped to standby mode (Doc ID 394261.1)

  Delete archivelog to sysdate - depends on all of the deletion policy. If the deletion policy is set on "applied pending all", then it does not delete the archives, if they are not applied on the day before. If the deletion policy is set to none, then it does not check if the archive is applied on the eve and deletes them directly.

  Last Archive generated on primary:

  SYS@oraprim > select max(sequence#) from v$ archived_log;

  MAX(SEQUENCE#)

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

  114

  Last check-in applied in mode ensures:

  SYS@orastb > select max(sequence#) from v$ archived_log in case of application = 'YES ';

  MAX(SEQUENCE#)

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

  109

  Delete policy set to NONE on primary:

  RMAN > show archivelog deletion policy;

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

  RMAN settings for database with db_unique_name ORAPRIM are:

  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;

  RMAN > delete archivelog until 'sysdate;

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 60 type of device = DISK

  List copies of newspapers archived to database with db_unique_name ORAPRIM

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

  Thrd Seq S key low time

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

  110-1-214 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727

  216-1-111 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731

  217-1-112 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731

  113. OF 1 219 A 13 JANUARY 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733

  222 1 114 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737

  You sure you want to delete the items above (enter YES or NO)? NO.

  It is the removal of primary archives that have not yet been applied on the eve.

  Delete policy 'APPLIES ON STANDBY ALL' value on the primary:

  RMAN > show archivelog deletion policy;

  RMAN settings for database with db_unique_name ORAPRIM are:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  RMAN > delete archivelog until 'sysdate;

  output channel: ORA_DISK_1

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 60 type of device = DISK

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727 thread = 1 sequence = 110

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731 thread = 1 sequence = 111

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731 thread = 1 sequence = 112

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733 thread = 1 sequence = 113

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737 thread = 1 sequence = 114

  It checks if the archive has been applied on the day before. As the 110 to 114 sequence is not applied in the waiting, the archives are not deleted on the primary.

  Hope that gives you a clear picture of how it works.

  -Jonathan Rolland

• What ArchiveLog deletion policy will activate

  Hi all

  I know when archive political deletion log turn on?

  
  

  Configure the policy to delete archivelog saved 2 times to the disk.

  Do above mean that delete archivelog backed up twice?

  
  

  Thanks for your help.
  

  The deletion policy specifies what archivelogs are eligible for deletion. In your example, the archivelogs, who were backed up 2 times on the disk (and not band).

  Deletion occurs when files in the FRA use all available space (depending on configuration), and the database recover space in order to store the new files - for example the new archivelogs.

• archive log deletion pending

  Hi all
  
  I'm working on oracle database enterprise edition 10.2.0.4.I have created a database.the physical standby of the primary database name is prim and the standby database name Eve.He has 100 files of newspapers to archive are generating each size is 300 MB per day. I applied archive log political removal of watch on the primary database. So all the newspaper shifted and applied pending archive are deleted from primary. But my concern is the archive logs staggered into sleep mode. The archivelogs in the standby server must be deleted.how that it can be removed. Help, please

  use RMAN to this effect, as you do in primaries.

  It will make a backup if you need and delete the archivelogs.

• RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  I get RMAN-08120: WARNING: journal archived not deleted, not yet applied watch on primaries
  but when I run under query, I get the same result of primary and backup
  
  SQL > select max(sequence#) from v$ archived_log;
  
  MAX(SEQUENCE#)
  --------------
  44051
  
  SQL >
  
  
  Eve is a log switch behind only!

  Hello;

  If RMAN tries to remove an archive which is not yet applied in standby log, you see the RMAN-08120

  It's a good thing. As long as you don't have any archives for days on standby, you probably don't have a problem.

  What are your RMAN settings for the database of the day before?

  MetaLink Note: 361182.1 can help too. Or Note 1079953.1

  Your main, make sure that:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
  

  Please consider closing some of your old issues to clean up the forum.

  Best regards

  mseberg

• RMAN archivelog deletion policy

  Hello
  
  I use 10 g on RHEL 4.8 64 bit 2.
  
  If I use the RMAN > "" backup database archivelog all delete all entries '; " It removes archiving of all locations logs after backup
  
  If this command obeys the retention-log archiving strategy or let say if I have something like below.
  
  CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES ON SBT.
  
  
  Thank you
  Vijay

  Fabienne wrote:
  If I say backup - archivelog all delete all entries: RMAN removes all archivelogs of all destinations of the archive after backup and retention policy applies to newspapers that have been backed up on TAPE or on DISK?

  remove all entries, will remove all SOURCES of backups after performing the backup.

  CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES ON SBT.

  In your case, RMAN backs up archivelogs for band and then remove all sources of archivelog backups.

  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14192/bkup003.htm

• I would like to delete policy, top stories, stories recommended, a trend of stories for you page on new app

  I would delete policy, top stories, stories recommended, new trends for you page on the news application? Please get what he was better before we can remove it

  Hello, fredym1!

  Thank you for joining the communities Support from Apple! Looks like you're wanting to customize the news application in the section for you. That's a big question! Read this article with the steps to use news on your iPad, iPhone or iPod touch. More precisely:

  Customize for you

  Add themes and channels that interest you in the section Explore to your Favorites. This allows new decide what kind of stories you show for you.

  To display the list of channels and topics you follow, tap on Favorites.  If you subscribe to a channel, there is a separate section in the Favorites for your subscriptions. You can also sort the bookmarks by name, visited recently, or most visited. Just tap Favorites at the top of the screen, then choose how you want to sort them.

  You want quick access to headlines? Learn how to Add the new app to your Widgets on your iOS device.

  

  Add a subject or a channel

  1. Tap Explore the bottom of the screen.
  2. Browse the categories, channels and topics that interest you.
  3. When you find a channel or a topic you want to add, click on .

  Looking for a specific topic or channel? Click the Search tab and enter what you are looking for. You can also add a topic or a channel, you are looking for to your Favorites. Just type in next to the search results.

  Remove a theme or a channel

  1. Go to your Favorites.
  2. Tap on edit.
  3. Type in the upper right corner of the string or the topic you want to delete.

  You can also cut a channel to avoid stories appear in your feed you.

  See you soon!

• RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  Hi Oracle Community,

  I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

  During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

  Concerning

  J

  Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

  RMAN> backup database plus archivelog;
  RMAN> delete noprompt archivelog all completed before 'sysdate-1';
  

• RMAN delete policy has not worked and not delete outdated backup

  Hi all

  I am facing a problem this obsolete backup is not delete unwanted backup.

  I used to take level 0 once weekly and cumulative incremental in 3 times a day.

  I have 2 TB hard drive, every week, I used the backup from command remove obsolete based file can delete based on my redundancy strategy 1.

  The previous week it works fine and deleted obsolete backup based on the deletion policy. but this week when I try to use the delete obsolete command, it is not removed and the hard drive is always full and I couldn't take later backup.

  It's live server, I need to take the free space on the hard drive. Please help me.

  You will find details of error that I met in the log file.

  output channel: C1

  output channel: C2

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of backup so archivelog command at 05/05/2015 10:57:14

  ORA-19502: write error on file 'G:\RMAN\AWSPROCESS\BACKUP\AWSPROCESS\BACKUPSET\2015_05_05\O1_MF_NNND1_TAG20150505T090032_BNJGC9RR_. BKP", the number of block 7227648 (block size = 8192)

  ORA-27070: async read/write failed

  OSD-04016: error queuing an asynchronous i/o request.

  S/O-error: (OS 112) there is not enough space on the disk.

  Your backup on May 02 is not a valid backup, then you can try something like:

  RMAN > delete database backup completed after 'sysdate-6 ";

• CONFIGURE ARCHIVELOG DELETION POLICY

  Hi all

  In this context:

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVE 2 TIMES TO THE DISK.

  I tell rman to consider the already saved archivelogs twice to be obsolete.

  I can then delete using:

  backup database more archivelog entry remove

  or manually as in

  cross-checking of backup;

  remove obsolete;

  My question is this: why would you wait until newspapers are saved twice? Why save twice on the drive?

  In my case, I saved them outside of the FRA and the FRA. I understand the process to remove them, I'm just not sure about the meaning of the "n TIMES" retention policy

  Thank you.

  11.2.0.2

  DA

  Hey Dan,

  Save your archivelogs twice is purely an exercise in belts and suspenders.

  So unless you have two backups RMAN will not remove the archivelog, you will get a warning of something like 'need to create another backup expiration deletion.

  Purely belts and suspenders and nothing more, in the case where a copy of one of the archivelogs is corrupt or something.