Data Guard - RMAN removing archive log

Similar Questions

• Purge logs archiving on things primary and Standby and for Data Guard RMAN

  
  Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

  Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

  Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

  Q1. The above only removes logs archiving to the primary or primary and Standby?

  Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  I also saw

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

  Q3. That what precedes, and once again it is something that you re primary side?

  I saw the following advice in the manual of Concepts of data protection & Admin

  Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

  Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

  Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  Any idea greatly appreciated,

  Jim

  The above only removes logs archiving to the primary or primary and Standby?

  When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

  including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

  You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

  If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  Its a configuration, it will not erase by itself.

  If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

  1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

  2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

  If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

  Great example:

  http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

  All Oracle is worth a peek here:

  http://emrebaransel.blogspot.com/

  That what precedes, and once again it is something that you re primary side?

  I would never use it. I always had it put it this way:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

  Why would I want my primary ro connect to the RMAN Repository?

  Because if you break down, you want to be able to backup there, too.

  Also if it remains idle for awhile you want.

  Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Always use a database of catalog RMAN with Data Guard.

  If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Same answer as 5, use a catalog database.

  Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Same answer as 5, use a catalog database.

  What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

  Best regards

  mseberg

  Summary

  Always use a database with RMAN catalog.

  Always use CRF with RMAN.

  Always set the deletion «To APPLY ON ALL STANDBY» policy

  DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

  Post edited by: mseberg

• Pull on the RMAN backup archive logs?

  Environment:

  Oracle 11.2.0.3 EE on Solaris

  Physical standby

  I have a gap of journal archive at the moment.  The missing archive logs have been saved on the primary and have not yet been transferred to waiting due to some maintenance work performed on the standby server.

  The database will be able to recognize that the missing archivelog files are in the RMAN backup files, restore them and send them to the update server standby for application?

  If not, will it restore manually, copy them to the standby server and save them for their application?

  Thanks a lot for your help!

  -gary

  Were the archivelogs deleted on the primary once they have been saved? If they have been deleted on the primary, then you can:

  1 manually transfer the backup to forward files

  2 replace the archivelog destination configured on the eve

  3 restart the managed recovery on the standby process, and the computer should be able to detect and apply the missing archivelogs.

  If they have not been deleted on the primary and are always available in the archivelog directory configured, then the process of Data Guard should be able to detect and automatically fix the gap.

  If you have a long interval archivelogs missing and you use + ASM, you can also try to use an incremental backup to roll forward the database pending, this article provides a good step by step: the steps for Rolling forward a standby database using RMAN incremental backup. (Doc ID 836986.1)

  Kind regards
  Oscar

• Data Guard problem (sequence of log says 1,2,3..)

  Hello
  
  I have a database (Prim) of production and ensure a physics database (Stand).
  
  Production down, I started standby (Stand) by the command 'alter database enable the database pending '.
  
  Now Eve will have production
  
  More I wanted to do (prim) database of production prior to standby controlfile and taking backup in sleep mode (stand)
  
  Restore on prim and mounted to the database.
  
  list of newspapers of record now shows log archiving as sequence 1,2,3,4...
  and the recovery does not occur.

  If you have flashbacks on, then Yes, you can restore [url http://nikolayivankin.wordpress.com/2012/02/14/dgmgrl-reinstating-ex-primary-to-standby-by-flashback-database-feature/] ex-primaires as before

  Otherwise, you only have to recreate the config.

• Delete pending archive logs

  Hello
  
  My oracle database is 11.2.0.2 RDBMS RAC on RHEL 5. 6
  
  We have recently established physics of the standby database. How to remove archive logs waiting for physical standby mode?

  Hello;

  There is a little different to do this. I would consider these notes:

  How to ensure that RMAN is NOT delete archived logs that have not yet shipped to standby [394261.1 ID]

  RMAN removes records of logs on the primary database not applied pending physical [ID 1324759.1]

  Configure RMAN to purge the archivelogs after application on hold [728053.1 ID]

  You can use an RMAN script to do this:

  echo "Starting RMAN..."
  $ORACLE_HOME/bin/rman target / catalog user/password@rcatalog << EOF
  
  delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
  
  exit
  EOF
  

  Best regards

  mseberg

• Removal of RMAN, Data Guard, and Archives journal

  Our DG Environment running Oracle 11 g R2
  We have a 3 node DG Environment with
  A primary being
  B and C being Active Data Guard Standby
  Backups are taken out of B and go directly to tape.
  Standby Redo Logs and fast recovery area are used
  
  
  
  Holding the recommendation of "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
  RMAN primary control ('A')
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING
  
  RMAN standby ("B") where the backup is performed
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY
  
  RMAN set the other Standby ("C")
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING
  
  How can we know what newspaper Archives are eligible to be removed from 'A' and 'C '?
  When remove it takes place?
  How can say us when archiving logs are deleted from the 'A' and 'C '?

  Dear user10260925,

  The documentation that you read is reliable but not enough.

  The Oracle can handle the archivelog directory and know that you are eligible for deletion. Stuff you posted here was derived from the books online and is supported and can be used when the Oracle knows and manages the archivelogs. This is simply called the flash recovery area. Please read the FRA at this very moment.

  Under the personal component normal circumstances in the industry use a few scripts to achieve on backup archivelog deletion.

  Here's a useful example to you;

  # Remove old archivelogs
  ######################################
  00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
  ######################################
  
  vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
  export ORACLE_SID=optstby
  export ORACLE_HOME=/oracle/product/10.2.0/db_1
  cd /db/optima/archive/OPTPROD/archivelog
  
  /oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
  grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
  chmod 755 delete_applied_redo_logs_1.sh
  sh delete_applied_redo_logs_1.sh
  rm delete_applied_redo_logs_1.sh
  rm delete_applied_redo_logs.lst
  

  vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
  vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
  set echo off
  set heading off
  spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
  select 'rm -f ' || name from v$archived_log where applied = 'YES';
  spool off
  exit
  vals3:/db/optima/archive/OPTPROD/archivelog#
  

  Hope that helps.

  Ogan

• 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

• Archiving logs apply frequency in Data Guard

  Dear all,
  
  How can we verify/set up the frequency archive newspapers should be applied to the Data Guard?
  
  Version: 10 g 2; OS: Windows 2003 R2 (64-bit).

  How we can configure the frequency of archive logs must be applied to the DG?

  Erase the question once more what you're expecing, as I understand, it's...

  It depends on the Redo genearation / Archive primary & network latency between primary databases & Eve.
  There is a configuration, you can change in the primary to put options such as delay , net_timeout and so on.

  consult this manual too.
  http://download.Oracle.com/docs/CD/B28359_01/server.111/b28294/log_arch_dest_param.htm

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

• Archive log list does not sequence of current journal is awaiting data base

  Hi all

  So I tried waiting for database physical installation in my local vm.

  I apparently completed the Setup, but I am facing a problem which I cannot understand.

  OS:-Linux 6.4

  Oracle version: 12.1.0.2.0

  primary data: ORA12C

  backup database: ORASTD

  Primary database: -.

  SYS@ORA12C > list of archive logs;

  Database log mode Archive Mode

  Active AutoArchive

  Archives/u01/app/oracle/fast_recovery_area of destination

  More old sequence of journal online 14

  Log sequence archive 16

  Current log sequence 16

  SYS@ORA12C > select name, database_role, controlfile_type from v$ database;

  NAME DATABASE_ROLE CONTROL

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

  ORA12C CURRENT PRIMARY

  SYS@ORA12C > select the sequence #, first_time, next_time, applied from v$ archived_log;

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  4 15 APRIL 15 APRIL 16 15 NO.

  4 15 APRIL 15 APRIL 16, 15 YES

  5 16 APRIL 15 APRIL 16 15 NO.

  5 16 APRIL 15 APRIL 16, 15 YES

  6 16 APRIL 15 APRIL 16 15 NO.

  6 16 APRIL 15 APRIL 16, 15 YES

  7 16 APRIL 15 APRIL 16 15 NO.

  7 16 APRIL 15 APRIL 16, 15 YES

  8 16 APRIL 15 APRIL 16 15 NO.

  8 16 APRIL 15 APRIL 16, 15 YES

  9 16 APRIL 15 APRIL 16 15 NO.

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  9-16 APRIL 15 APRIL 16, 15 YES

  10 16 APRIL 15 APRIL 16 15 NO.

  10-16 APRIL 15 APRIL 16, 15 YES

  11 16 APRIL 15 APRIL 16 15 NO.

  12 16 APRIL 15 APRIL 16 15 NO.

  13 16 APRIL 15 APRIL 16 15 NO.

  11-16 APRIL 15 APRIL 16, 15 YES

  12-16 APRIL 15 APRIL 16, 15 YES

  13-16 APRIL 15 APRIL 16, 15 YES

  14 16 APRIL 15 APRIL 16 15 NO.

  15 16 APRIL 15 APRIL 16 15 NO.

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  15 16 APRIL 15 APRIL 16 15 NO.

  14-16 APRIL 15 APRIL 16, 15 YES

  Waiting for the database: -.

  Select the sequence #, first_time, next_time, applied from v$ archived_log;

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  4 15 APRIL 15 APRIL 16, 15 YES

  5 16 APRIL 15 APRIL 16, 15 YES

  6 16 APRIL 15 APRIL 16, 15 YES

  7 16 APRIL 15 APRIL 16, 15 YES

  8 16 APRIL 15 APRIL 16, 15 YES

  9-16 APRIL 15 APRIL 16, 15 YES

  10-16 APRIL 15 APRIL 16, 15 YES

  11-16 APRIL 15 APRIL 16, 15 YES

  12-16 APRIL 15 APRIL 16, 15 YES

  13-16 APRIL 15 APRIL 16, 15 YES

  15 16 APRIL 15 16 APRIL 15 IN-MEMORY

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  14-16 APRIL 15 APRIL 16, 15 YES

  SQL > select name, database_role, controlfile_type from v$ database;

  NAME DATABASE_ROLE CONTROL

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

  PHYSICAL STANDBY ORA12C STANDBY

  SQL > archive logs list;

  Database log mode Archive Mode

  Active AutoArchive

  Archives/u01/app/oracle/fast_recovery_area of destination

  More old sequence of journal online 0

  Log sequence to archive 0

  Current log sequence 0

  Now, here's my question is why the sequence of current newspapers shows 0. I tested the datas

  database primary eve happens again. I'm totally out of index.

  I tried to find it on google but nothing could help me until now.

  Any kind of help would be very appreciated.

  Thank you

  Soumya

  Hello

  I am also testing in Data Guard 12.1 configurations.

  Oracle support response is "it seems therefore that this information be removed.

  So is the best way to check on the database pending:

  SQL > select thread #, max(sequence#) ' last day before Seq received. "

  v $ archived_log val, v$ database vdb

  where val.resetlogs_change # = vdb.resetlogs_change #.

  Group thread # order by 1;

  SQL > select thread #, max(sequence#) ' last day before Seq applied.

  v $ archived_log val, v$ database vdb

  where val.resetlogs_change # = vdb.resetlogs_change #.

  and val.applied in ('YES', "IN-MEMORY")

  Group thread # order by 1;

  concerning

• Archive Data Guard and Flashback

  Hello
  
  I have a DB 11.2.0.1 with a database of pending.
  If I put a few tables to be in the flashback data archive, (support for FDA tables) will be copied to a db as well sleep?
  
  concerning

  Hello;

  I hesitate to answer because you don't seem to close your old questions or give points to those who help. But I also believe in giving the benefit of the doubt.

  If the FIU is configured on your watch then the answer is Yes.

  While this is not a requirement to use I would always use FRA with Data Guard.

  db_recovery_file_dest = ' / u01/app/oracle/flash_recovery_area.

  The following are some sample parameter values that might be used to configure a physical standby database to archive its standby redo log to the fast recovery area:
  
  LOG_ARCHIVE_DEST_2 = 'LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILE,STANDBY_ROLE)' LOG_ARCHIVE_DEST_STATE_2=ENABLE
  

  Source

  DataGuard of Concepts and Administration 11g Release 2 (11.2) E10700-02

  With RMAN efficiently in an environment of Dataguard. [848716.1 ID]

  Best regards

  mseberg

  Published by: mseberg on December 1, 2012 13:53

• How to move from Data Guard time really apply (restore) to archive the journal

  Hello
  
  Standby database configured with broker and application really remake in time; However, I want to change it to archive the journal apply mode without losing the broker configuration. Is this possible? If it is not possible to use the broker to make archive log apply, I can remove the broker and use Data Guard to set up the day before to use the archive log apply?
  
  Concerning

  Hello;

  Broker automatically allows real-time applies to databases on hold if the standby database has standby redo logs configured.

  Stop repeat applies

  DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-OFF';
  

  Repeat restart applies broker

  DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-ON';
  

  In order to get rid of standby redo logs would be a way. I would like to leave myself alone. Real time assistance to prevent the loss of data.

  Best regards

  mseberg

• remove disk archiving logs

  How can I delete the backup copies defined archives logs, all my archives are written in asm and from there they are saved on the disk in the form of backup sets. archive backup sets are not get deleted from the drive. How can I change the config to have them removed?
  
  Here is the show all the config of rman.
  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVE 2 TIMES TO THE DISK.

  Hello

  data compressed backupset backup more archivelog entry remove

  Concerning
  Hitgon

• With RMAN for backup, but not with the archive logs

  We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.
  
  Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.
  
  My question is around logs archiving and RMAN.
  Our current situation is:
  -We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
  -We set the archive_lag_target so archiving logs is produced every 30 minutes.
  -a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
  -daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.
  
  I'm interested in feedback as to if our strategy around archiving logs is correct or not.
  
  Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
  We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.
  
  Curious to know what others are doing.

  Hello

  Welcome to OTN!

  Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

  On the disk space, you can delete the archives once they were saved by RMAN.

  RMAN > delete any backup archivelog entry;

  This supports the archivelogs and then remove the archives from the disk.

  If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

  RMAN > configure archivelog political of deletion to applied pending;

• RMAN-06059: expected archived log not found

  DB version: 11.1.0.7
  Operating system: Solaris 10
  
  Our cron job RMAN has met the following error.
  -First save attempt (complete bkp more archive log) done by connecting to the catalog

  Starting backup at 14-MAR-12
  current log archived
  released channel: ch00
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of backup plus archivelog command at 03/14/2012 08:09:58
  RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
  ORA-19625: error identifying file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-17503: ksfdopn:2 Failed to open file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-15173: entry 'pqwsp_26530_1_764525298.arc' does not exist in directory 'pqwsp_arch'

  Because I didn't share RMAN catalog schema password, I used the control as a catalog file and run the CROSSCHECK command.
  
  -Use the control as a catalog file

  $ rman target /
  
  Recovery Manager: Release 11.1.0.7.0 - Production on Wed Mar 14 09:45:59 2012
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  connected to target database: PQWSP (DBID=1638594930)
  
  RMAN> crosscheck archivelog all;
  
  using target database control file instead of recovery catalog
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=429 instance=pqwsp1 device type=DISK
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26563_1_764525298.arc RECID=19019 STAMP=777888587
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26564_1_764525298.arc RECID=19022 STAMP=777890270
  validation succeeded for archived log
  .
  .
  .
  .
  .
  
  Crosschecked 14 objects

  Cannot find objects expired in the output above. I had * "validation succeeded" * message to arch all newspapers.
  
  So I ran a

  BACKUP ARCHIVELOG ALL DELETE ALL INPUT;

  and this backup was successful.
  
  No idea why the first attempt failed when there were not all logs archived expired? If I run the command of OVERLAP by connecting to the catalog, I could find out of date newspapers?

  No idea why the first attempt failed when there were not all logs archived expired?
  this case is not releated archivelog expired, however it seems the requested archivelog 26530 isn't available on destinationas, that it can be removed manually or another taking backup operation the backup and deleted if the execution of the whole.

  crosscheck updated detail that its not available for backup... Check the output of you overlap cmd to 26530 archivelog.

  Thank you
  Tylay Singh