CONFIGURE ARCHIVELOG DELETION POLICY

Similar Questions

• 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

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

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

• How to configure the deletion on 10g policy?

  Oracle 10.1, I would invoke the command like:
  

  CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;

  but it does not work on 10g, 11g only.
  is there such a command for 10g? I can not find...

  ARCHIVELOG DELETION POLICY applies to the ArchiveLogs.

  It does not apply to backups.

  Backups and ArchiveLogs are different types of objects.

  Hemant K Collette

• 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

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

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

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

• TCP/IP configuration with group policy?

  Hi guys!

  I intend to install the DHCP server on my domain controller (windows 2003) concerning the dynamic assignment of IP addresses, where all the computers on the network are using static IP now. I don't want to change the existing TCP/IP configurations of computers and other network of dynamic static devices in addressing all the machines in the network as it is tedious and not professional. Do I need some special or additional configurations to DHCP or any group policy useful to change dynamically TCP/IP configurations.

  any help to the my query will be highly appreciated.

  Best regards and thanks in advance

  Server problems are better managed on Technet.  http://social.technet.Microsoft.com/forums/en-us/categories/

  responses to consumer issues.

  Good luck

• ASM diskgroup space do not free themselves after RMAN archivelog delete

  Version Infra grid: 11.2.0.4

  DB version: 11.2.0.4

  OS: Oracle Linux 6.4

  Storage: Enterprise-class storage (EMC VMAX)

  We are in the Bank we have a database of CARS of Production 2 nodes very critical.

  Newspaper archives are stored in ARCH_DG diskgroup. Because of the unexpectedly heavy workload, our diskgroup ARCH_DG became full and we got the usual error

  ORA-00257: archiver error. Connect internal only, until this just released.

  To wear the DB back to business quickly, I tried to delete the old archive logs more than 1 day of the diskgroup first using the following command

  RMAN > delete noprompt archivelog until ' SYSDATE-1';

  So, I started to see the following message

  
  

  RECID = STAMP 19807 = 849396325 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10066.331.849396309 archived log file

  Delete archived log

  RECID = STAMP 19809 = 849396940 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10067.274.849396925 archived log file

  Delete archived log

  name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10068.341.849397529 RECID archived log file = 19810 STAMP = 849397543

  Delete archived log

  name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10069.298.849398167 RECID archived log file = 19812 STAMP = 849398182

  Delete archived log

  RECID = STAMP 19813 = 849398806 name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10070.317.849398783 archived log file

  Delete archived log

  name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10071.342.849399327 RECID archived log file = 19814 STAMP = 849399337

  Although I could see messages "deleted archived newspaper" as stated above there are 2 inconsistencies (odd behavior)

  1 inconsistency. Not a single byte released upwards of archive diskgroup. Each log archiving is 4 GB in size. I got "journal archived deleted" message at least 25 archived log files. For example, 100 GB should have been released.

  The diskgroup to archive has remained at 99.9% as shown below and the DB was inaccessible.

  SQL > select name,.

  Round(total_mb/1024,2) Total_GB.

  Round(free_mb/1024,2) Free_GB.

  free_mb/total_mb * 100 "% free"

  ABS ((free_mb/total_mb*100)-100) '% complete '.

  v $ asm_diskgroup;  2 3 4 5 6

  NAME TOTAL_GB FREE_GB % free full
  ------------------------------ ---------- ---------- ---------- ------------
  ARCH_DG 1000.78 99.9223633.077636719
  DATA_DG 10000.02 1188.19 11.8818616 88.1181384
  OCR_VOTE_DG 12 11.09 92.4623525 7.53764754
  < snipped >

  
  

  Inconsistency2. The number of available archived newspapers remained unchanged. He was always showing 301

  SQL > select count (*) from v$ archived_log where status = 'A ';

  COUNT (*)

  ----------

  301

  RMAN later > remove obsolete; command removed 17 archived newspapers.

  This means that 17 x 4 = 68 GB should have been released.

  But Diskgroup of free space and the County of v$ archived_log.status = 'A' is unchanged, as mentioned above.

  , Of ASMCMD, I deleted manually a full archive directory connects using rm-rf command.

  Even after running rm - rf on a whole directory full of archived newspaper space was not released and we always receive ""ORA-00257: archiver error '. "

  So, we had to shoot down the cluster using "stop crsctl crs. After the cluster has been raised using 'crsctl start crs' on both nodes,

  space has been freed up, and the DB became accessible.

  I wonder why the ASM diskgroup space was not release despite the removal of the archive logs. Are the 1 & 2 above mentioned inconsistencies caused by something handle to open the file ?

  Hello

  Please run command you at the level of the ASM, below

  SQL > alter diskgroup check all the repair;

  -At the end of the same thing, run below command and enable it to perform

  SQL > alter diskgroup rebalance power 4.

  -To validate the space

  $ asmcmd Pei lsdg

  Kind regards
  Loriette

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

• Configure ARCHIVELOG Mode

  Hi all
  
  I'm using the Oracle 11 g with Windows 32-bit platform.
  
  My database was in noarchive mode.
  

  SQL> SELECT LOG_MODE FROM V$DATABASE;
  
  LOG_MODE
  ------------
  NOARCHIVELOG
  
  
  SQL> shutdown immediate
  Database closed.
  Database dismounted.
  ORACLE instance shut down.
  
  SQL> startup mount
  ORACLE instance started.
  
  Total System Global Area  535662592 bytes
  Fixed Size                  1334380 bytes
  Variable Size             306185108 bytes
  Database Buffers          222298112 bytes
  Redo Buffers                5844992 bytes
  Database mounted.
  
  SQL> alter database archivelog;
  
  
  Database altered.
  
  SQL> alter database open;
  
  Database altered.
  
  SQL> archive log list;
  
  Database log mode            Archive Mode
  Automatic archival             Enabled
  Archive destination            USE_DB_RECOVERY_FILE_DEST
  Oldest online log sequence     40
  Next log sequence to archive   42
  Current log sequence           42
  
  SQL> show parameter log_archive_start
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ---------
  log_archive_start                    boolean     FALSE
  
  SQL>

  I'm doing a switch a check to my way USE_DB_RECOVERY_FILE_DEST logs are generated.
  That's all it requires to configure databsae in ARCHIVELOG Mode.
  A question is why is log_archive_start FALSE setting. I think it should be TRUE.
  

  SQL> Alter system archive log start;
  
  System altered.
  
  SQL> show parameter log_archive_start
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ---------
  log_archive_start                    boolean     FALSE
  
  SQL>

  Thank you
  SAZ

  You don't need this setting. This setting was amortized to the oracle 10g database.

  Concerning
  Asif Kabir

• RMAN ARCHIVELOG DELETE THE ENTRY SITE

  With RMAN to back up the database with 2 destinations journal archive. If log_archive_dest_1 = / usr/archive/LOCATION and test log_archive_dest_2
  LOCATION = / u03/archive/test and the two dest_states are enabled (log_archive_min_succeed_dest = 1), directory which is affected by the ENTRY DELETE command to remove the ARCHIVELOGS? According to the Oracle Documentation:
  
  You can specify clauses ENTRY REMOVE or REMOVE all THE ENTRIES for the BACKUP ARCHIVELOG command remove newspapers archived after that only they are saved, eliminating separate to remove manually step the archived redo logs. REMOVE ENTRIES, RMAN only deletes the specific copy of the log of archived redo chosen for the backup set.
  
  Is there a way to make Oracle choose the directory? The reason is that I want to keep 3 days newspapers on the drive, but the smaller location = / usr/archive/test only supports one day of logs. I also have the logs to another server to backup and save 1 week, but prefer to leave 3 days on the server database, but in the largest/u03/archive/test directory. If all the newspapers in the smallest directory files can be deleted after the backup if possible.
  
  Thank you
  
  Curt Swartzlander
  Northwest Arkansas Community College

  Do not "delete entry", but delete the archivelogs directly (of course after the backup command). Use the option 'as string_pattern' in the command "delete archivelog' to specify the location:

  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/rcmsynta008.htm#i78730

  Werner