Archive log deletion policy explanation

Similar Questions

• ARCHIVE NEWSPAPER DELETTION POLICY

  Hi all...
  I configured saparate location for archve log...
  my retention policy is set to 1 redundancy...
  last backup I took was on Saturday...
  Since last week, there was a lot of archived newspapers generated...
  so today I have dedcided to remove all not required archive log...
  so I run the command...
  report obsolete...
  and then delete obsolete...
  WHN I run the command delete obsolete it has deleted all the obsolete backup... pieces but for fun he removed several newspapers archived in the location of log_archive_dest_1...
  I wonder why he deleted archived journal because I did not to any command to remove the archived newspaper...

  user13762949 wrote:
  I use 11.1.0.6.0...
  the command that I published was...

  RMAN > obsolete report
  RMAN > remove obsolete
  so I stray m that order they should have removed the obsolete backup of FRA and no archived log destination...
  fact RMAN automatically recognizes the log... If obsolete archive so much so I was show teas command last week but never happened like this...

  no idea what could have happened

  Yes-RMAN knows your destination of the newspaper archive and it automatically deletes obsolete backups more is not necessary-for-recovery of the archivelogs when you issue remove obsolete command.

  concerning

• Archive log deletion with no backup of the archive logs

  I suffer from enormous size archive of the newspaper. In my previous post, I asked for help. I almost 480 GB archive log every day in our database of 11 2 under redhat linux 5.8 GR. Now, if you please help me in another case.
  
  If I take backup of archive logs and run delete archivelog everything until ' sysdate-1' with each backup database of day how it affects. " In my opinion there should be no problem in that I have the last incremental backup and recovery 1 days archive log in archivelog destination. If I do not archive log backups to how it will be different. Help, please.

  >

  Hello

  Sir, I know how to remove. But in my opinion delete up to sysdate-1 and taking no backup of the Archives of newspapers will
  no effect. Is in my opinion is right or wrong, that is the question.

  What I read in your original post, is that you take a daily incremental backup - Yes? I'm assuming that you also take
  a full backup on a regular basis (Sunday?).

  I was working on the assumption that the foregoing is available? I worked on a project where installation has been similar. We
  tested regularly backups - I hope that you do the same thing?

  What we used to do was FTP (script Unix - cron job - if you Google you will find Python or Perl to do the same thing - that is)
  what I wanted to, but was cancelled - very 1980, anyway) the archived redo logs on to a specific computer that holds only these files.
  After FTP "d - they have been removed from the server, freeing up space.

  Now, you say you have TB 0.5 per day - while more than a week, you will need a machine with ~ 3 TB of disk - if you can get a kind
  the scenario as this place and running, then you will have both your incremental backup and your archived redo logs for the last
  24 hours and the full backup with recovery archived records dating back to this full backup. You can also always archive on tape if
  suits. So, you will have redundant coverage - 'belt and braces' as the Americans say.

  But, to answer your question directly, "take no backup of archive logs have no effect" - that is true - it
  will not affect the operation of the database server, but if I were you, I would hang on to enough archived redo log to return to the
  last backup. That's just my humble OPINION.

  HTH,

  Paul...

  Published by: Paulie July 21, 2012 19:28

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

• Archive log deletion

  Hello

  Can we delete all the archivelog, if we take a full backup RMAN or cold backup. I'm using Oracle 11 g 2.

  If you take an RMAN backup with the OPEN database, you must back up both archivelogs (even if "there is no user transaction").

  If your RMAN backup started at 10:00 and ended at 11:30, the minimum archivelogs that you must back up are those of the first after 10:00 in the first after 11:30 - this range is necessary to capture all the changes that have occurred in the database during execution of the backup.

  However, if you backup all archivelogs generated, you have the possibility to be able to restore and recover the database to any point in time.

  Hemant K Collette

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

• Data Guard - RMAN removing archive log

  Hello

  I ' v DataGuard with physical standby.

  I do a backup only on the primaries. Both sites have ther separate backup systems.

  I ' v FRA and configured archivelog deletion with RMAN configuration:

  on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?

  1 should I reconfigure RMAN?

  change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  2. make full backup

  Hello

  1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

  section: "all archived Redo Log deletion policy."

  Document provides the best algorithm to analysis of work

  You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to allow a policy of removal of archived newspaper. This configuration specifies that archived newspapers are eligible for deletion only when the specified number of archived log backups exist on the specified device type.

  
  

  If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

  The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

  2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

  It will be useful.

  -Thank you

  Pavan Kumar N

• 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

• 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

• Retention policy for archive logs.

  Retention policy is set to "REDUNDANCY 2".

  We do the complete disk backup without archive logs at 12:00.

  After that, we make full backup with newspapers to archive tape at 18:00.

  RMAN will consider newspapers to check-in after 12:00 as obsolete as it is backed up to tape?

  Thank you.

  REDUNDANCY applies only to the data files and control files. For archiving logs, there are POLICY of DELETE ARCHIVELOG. But "remove obsolete" won't use POLICY of DELETE ARCHIVELOG, so archiving logs should be removed separately if they meet this policy.

• 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

• 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-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';
  

• delete files from archive log with rman

  Hi guys,.

  I try to delete the log file archive on my backup site, but I get the following message. There are a lot of archive logs is present on the storage but rman may show that. No idea what I'm doing wrong here.

  RMAN > list archivelog all;

  specification does not match any newspaper archived in the repository

  RMAN >

  Kind regards

  Sorry about that. Its 11g 2 R (11.2.0.1) and OS Version is 2008 R2 64 bit. Sleep is in auto recovery mode. (hope this helps).

• Current archive log has been deleted, how to recover using the previous archive log?

  Hello
  
  My current log sequence #819 and it has been deleted and no other choice to get it back and I have previous newspapers archived with sequences #814 à 818.
  
  When I start my database is to show that the use ' MUST USE RESETLOGS or NORESETLOGS option of database open, then I used the command
  
  SQL > ALTER DATABASE OPEN RESETLOGS;
  ALTER DATABASE OPEN RESETLOGS
  *
  ERROR on line 1:
  ORA-01113: file 1 needs media recovery
  ORA-01110: data file 1: ' E:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01. DBF'
  
  SQL > alter database recover;
  ALTER database recover
  *
  ERROR on line 1:
  ORA-00283: cool cancelled due to errors
  ORA-01610: recovery using BACKUP CONTROLFILE option must be
  SQL > alter database recovery using backup controlfile;
  change the database recovery using backup controlfile
  *
  ERROR on line 1:
  ORA-00279: change 8433746 September at 15/01/2013 19:51:59 needed to screw 1
  ORA-00289: suggestion:
  E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_01_16\O1_MF_1_819_
  
  % U_. ARC
  ORA-00280: change 8433746 thread 1 is in sequence #819
  
  now, I don't have the log archiving with 819 sequence, I recover from 818. Please tell me how to do?

  Hello

  1. select * from v$log and see which log file is current. Query v$logfile to check physical file location belonging to current log group.
  2. Take bacup of your curent control file using copy/paste of your OS
  3. Issue following command in mount state
  recover database until cancel using backup controlfile
  4. When it finishes applying available archived logs, still it will ask for the location of archived logs which have not been applied, here provide path of current redo log file you got in first step. Here your recovery will finish after applying current redo log
  5.alter database open resetlogs.
  

  Salman