Crontab RMAN+Delete noprompt

I have a 11g environment.
I store in the catalog the following script:
change archivelog all crosscheck;
crosscheck backup of database;
BACKUP
INCREMENTAL LEVEL 0 cumulative
AS COMPRESSED BACKUPSET
DEVICE TYPE DISK
DATABASE
PLUS ARCHIVELOG;
DELETE NOPROMPT ARCHIVELOG ALL BACKED UP 1 TIMES TO DISK COMPLETED BEFORE ="SYSDATE-1/2";
Every night I launch from the Oracle user's crontab a process which connect to the catalog and executes the script. The backup runs perfectly but
"DELETE NOPROMPT...." sentence doesn't run. At the crontab mail appears a message
"wating response...."¿?

Have you tried other options to delete the archive logs, like DELETE INPUT?
RUN {
  CHANGE ARCHIVELOG ALL CROSSCHECK;
  CROSSCHECK BACKUP OF DATABASE;
  BACKUP
    INCREMENTAL LEVEL 0 CUMULATIVE
    AS COMPRESSED BACKUPSET
    DEVICE TYPE DISK
    DATABASE PLUS ARCHIVELOG DELETE INPUT;
}

Similar Messages

  • RMAN "delete noprompt obsolete" not deleted

    OS: AIX 5.3L; Oracle 10g R2
    I have "delete noppropt obsolete" in my RMAN backup script as {
    delete noprompt obsolete;
    crosscheck backupset;
    crosscheck archivelog all;
    delete noprompt expired backup;
    delete noprompt expired archivelog all;
    backup as compressed backupset incremental level 1 cumulative device type disk tag 'Baan_bkup$LEVEL1' database plus archivelog delete input; }
    but the incremental level 1 cumulative backupsets, outside my 7 days window, did not been deleted as prompted, even they are under the obsolete list. Why?
    Message was edited by:
    user508054

    I also observed that with "REPORT OBSOLETE", only partial of the backupset piece of backup were "OBSOLETE". For example, after this morning LEVEL 1 incremental backup, my last Sunday, Mar 4 level 0 backup has 12 backup pieces (including controlfile and archivelog), but only two have been on the obsolete list. The two are controlfile and archivelog, and other 10 datafaile backupsets are still there in the list. Really confused! Are they supposed to be treated as a bunch?

  • RMAN delete noprompt obsolete

    Hi,
    I'm keen to know what does this comand mean in RMAN backup. "delete noprompt obsolete;" .Can I apply this comand for no catalog too or it's just meant for rman catalog.
    Thanks
    M.Kaur

    Hi,
    I'm trying to do house keeping on RMAN backups,following is my script,but this does not remove hte last year's backups on the tape,thou the tape is mounted to the lib.Must I add in another command? but yes the last year's backup is not even shown in the rman backup list,but it's still in the sbt_tape,how do I remove it from there.
    Note: RMAN no catalog running on oracle 9i 9.2.0.7
    allocate channel for delete type disk;
    allocate channel for delete type 'sbt_tape'
    PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    report obsolete orphan;
    report obsolete;
    crosscheck backup;
    crosscheck copy;
    crosscheck backup of controlfile;
    delete noprompt expired backup;
    delete noprompt expired archivelog all;
    delete noprompt expired backup of controlfile;
    delete force noprompt expired copy;
    delete force noprompt obsolete orphan;
    delete force noprompt obsolete;
    release channel;
    Thanks

  • RMAN Delete Obsolete job fails due to Error Allocating Device

    Experts, I need help, please.
    This is 10.2.0.1 on Windows
    RMAN> DELETE NOPROMPT OBSOLETE;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 3 days
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=130 devtype=DISK
    released channel: ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 05/15/2012 14:10:17
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    I ran RMAN> configure device type 'SBT_TAPE' clear;
    but I still get the same error.
    I backup to Disk, not tape
    Notice the reference to SBT_TAPE:
    RMAN configuration parameters are:
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    What do I need to do to be able to run DELETE OBSOLETE; ?
    Thanks, John

    as anand mention ,you've to reset this parameter to default value.
    and clear cmd with configure will remove it from configuration parameter
    see below
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    *CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;*
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
    RMAN> delete obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 05/16/2012 12:04:34
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 2
    RMAN>  CONFIGURE DEVICE TYPE 'SBT_TAPE' clear;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    RMAN configuration parameters are successfully reset to default value
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
    RMAN> delete obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=1591 instance=GG1 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=1627 instance=GG1 devtype=DISK
    no obsolete backups found

  • Delete noprompt obsolete

    Hello,
    RMAN >delete noprompt obsolete;
    The "delete obsolete" or "delete noprompt obsolete" will delete the archivelog files past the retention from disk and will also delete any backups on disk or tape.
    My retention redundancy is 1. According to the statement above, it will delete the archivelog files and any backups on disk or tape from a previous day. My issue is that I want to delete backups on disk based on the redundancy 1, but keep the archivelogs for 5 days then delete archivelogs. So, the "delete noprompt obsolete" will not work in my case.
    So, I replace this "delete obsolete" with this command "delete noprompt archivelog All completed before 'SYSDATE-5';" to delete any archivelogs that are more than 5 days old. That would solve my archivelog issues, but what happens to my backups on disk (I want to delete backups based on redundancy 1)?
    Thank you.

    feverlove wrote:
    Thanks mseberg.
    1) delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-5';
    2) DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
    Does redundancy 1 retention take care of the #2 ? If so, why do I need the #2.
    Thank you again.For your archivelog deletion policy, you can try what was suggested earlier
    delete noprompt archivelog until time 'SYSDATE-5';With respect to your backups, you can have the retention policy left as it is by setting it to redundancy 1 and add this to your level 0 backup script/full backup script (if not added earlier).
    crosscheck backup;
    delete noprompt obsolete;My Bad.
    I am of the opinion that the above command (delete noprompt obsolete) deletes even the archives that fall within the 5 days time.
    Edited by: Shivananda Rao on Oct 22, 2012 8:06 AM

  • RMAN-06207 when DELETE NOPROMPT OBSOLETE;

    Hello all
    I want to backup and delete backuped archivelogs on a standby instance using the following script:
    RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE sbt PARMS='ENV=......';
    BACKUP ARCHIVELOG ALL DELETE INPUT;
    DELETE NOPROMPT OBSOLETE;
    RELEASE CHANNEL ch1;
    When deleting all obsolete backup pieces, I receive the following error:
    RMAN-06207: WARNING: 1 objects could not be deleted for SBT_TAPE channel(s) due
    RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
    RMAN-06210: List of Mismatched objects
    RMAN-06211: ==========================
    RMAN-06212: Object Type Filename/Handle
    RMAN-06214: Backup Piece c-2414804385-20080820-02
    As a workaround, I then manually delete obsolete backup pieces using:
    delete force noprompt obsolete device type sbt_tape
    What is the cause for rman-06207 ? How can I change my rman script to safely delete backuped archivelogs?
    I work with Oracle 10G release 10.2.0.3 both on standby and catalog DB.
    Casi

    Did you try using the CROSSCHECK command to verify the backup files status?
    From your comments, it doesn't seem like you did. CROSSCHECK checks the status of the RMAN backups against the disk/tape and updates the RMAN repository. CROSSCHECK does not remove any files just updates the status. The status options are - expired, available, and unavailable.

  • RUN "delete noprompt obsolete" before "backup database"

    Hello,
    11g on windows 2003, 3 day recovery window
    For almost a year now, I having been running the below script daily to backup my database. Now I am begining to run out of disk space, and can not run the backup commands unless I run "delete noprompt obsolete" first.
         backup database tag=database_full_backup;
         backup archivelog all delete input tag=achivelog_backup;
         crosscheck backup;
    delete expired backup;
         delete noprompt obsolete;
    Is it a bad idea to rearange the order of the commands like below?
    crosscheck backup;
    delete expired backup;
         delete noprompt obsolete;     
    backup database tag=database_full_backup;
         backup archivelog all delete input tag=achivelog_backup;
    thanks for any help

    Hi,
    No problem. You configured a recovery window of 3 days, it means you want to be able to restore/recover until sysdate - X (X up to 3) at any time. RMAN will always respect that, you can "delete obsolete" whenever you want.
    Best regards
    Phil

  • My RMAN delete archived standby

    Hello experts, I am looking for help with the following:
    backgroung: I have two database source and downstreams
    At source database I configure the log_archive_dest_2 to send redolog to the downstreams database.
    At downstreams database I configure the log_archive_dest_1 valid for the online redo and location in BD1 diskgroup  and the log_archive_dest_2 valid for the standby and location in BD2 diskgroup.
    When I make a backup at downstreams database the archived standby are deleted but they are necessary for the capture process. I need that when I make a backup it do not delete them. That is I need only delete the archived log inside +BD1, specific to the downstreams database.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Thank you, sir
    Yes my databases are in the same machine.
    AS part of my RMAN scritp I have 3 functions
    1- Backup_level_0. Here I use the following sentece:
    backup as compressed backupset incremental level 0 check logical format '$FileBack' TAG "RMAN_LV0" database include current controlfile plus archivelog delete input;
    2-Backup_archived. Here I use the following:
    backup as compressed backupset check logical TAG "RMAN_ARC" archivelog all delete input format '$FileBack';
    3-DELETE_obsolete. Here I use the following:
    delete noprompt force obsolete recovery window of $Dias days;
    in my database I archive the online redolog in a different diskgroup that standby but when I execute the script all the archivelog are deleted. I need only delete the online archivelog.

  • Rman delete old file and recover

    Hi Friends,
    after full backup.
    we use below syntax to delete old file.
    delete noprompt archivelog until time '(SYSDATE - 10)';
    However, we get a message that file is used and delete failure. ramn stop process.
    my question:
    does the old archivelog file is deleted ot not?
    If the old archivelog file is delete, do we have any command like sql rollback to recover it?
    any other commane to recover mis comman in ramn.
    or we must recover it?
    Thanks,
    ji

    user589812 wrote:
    Hi Friends,
    after full backup.
    we use below syntax to delete old file.
    delete noprompt archivelog until time '(SYSDATE - 10)';
    However, we get a message that file is used and delete failure. ramn stop process.
    Please paste the error here.
    my question:
    does the old archivelog file is deleted ot not?
    If the old archivelog file is delete, do we have any command like sql rollback to recover it?
    any other commane to recover mis comman in ramn.
    or we must recover it?
    Thanks,
    jithere is no any command sort of rolback to recover archivelog,if you have backup of archivelog then you can restore
    archivelog from this archivelog backupset.
    RMAN>restore archivelog all
    Khurram

  • Will RMAN delete archive log files on a Standby server?

    Environment:
    Oracle 11.2.0.3 EE on Solaris 10.5
    I am currently NOT using an RMAN repository (coming soon).
    I have a Primary database sending log files to a Standby.
    My Retention Policy is set to 'RECOVERY WINDOW OF 8 DAYS'.
    Question: Will RMAN delete the archive log files on the Standby server after they become obsolete based on the Retention Policy or do I need to remove them manually via O/S command?
    Does the fact that I'm NOT using an RMAN Repository at the moment make a difference?
    Couldn't find the answer in the docs.
    Thanks very much!!
    -gary

    Hello again Gary;
    Sorry for the delay.
    Why is what you suggested better?
    No, its not better, but I prefer to manage the archive. This method works, period.
    Does that fact (running a backup every 4 hours) make my archivelog deletion policy irrelevant?
    No. The policy is important.
    Having the Primary set to :
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBYBut set to "NONE" on the Standby.
    Means the worst thing that can happen is RMAN will bark when you try to delete something. ( this is a good thing )
    How do I prevent the archive backup process from backing up an archive log file before it gets shipped to the standby?
    Should be a non-issue, the archive does not move, the REDO is transported and applied. There's SQL to monitor both ( Transport and Apply )
    For Data Guard I would consider getting a copy of
    "Oracle Data Guard 11g Handbook" - Larry Carpenter (AKA Dr. Paranoid ) ISBN 978-0-07-162111-2
    Best Oracle book I've read in 10 years. Covers a ton of ground clearly.
    Also Data Guard forum here :
    Data Guard
    Best Regards
    mseberg
    Edited by: mseberg on Apr 10, 2012 4:39 PM

  • RMAN Delete pbsolete ERROR

    Dear Friend,
    In our production server , we use IBM - Tivoli Storage Manager - Software for our RMAN backup purpose . The backup data backup piece are stored on a Storage Library . It works fine but the problem is when I am going to delete "obsolete backup" then it shows the following error :
    RMAN> Delete pbsolete;
    Backup Set 870 06-OCT-08
    Backup Piece 870 06-OCT-08 c-1077970889-20081006-00
    Backup Set 871 07-OCT-08
    Backup Piece 871 07-OCT-08 rfjsj6d8_1_1
    Backup Set 872 07-OCT-08
    Backup Piece 872 07-OCT-08 rgjsj6n1_1_1
    Backup Set 873 07-OCT-08
    Backup Piece 873 07-OCT-08 c-1077970889-20081007-00
    Backup Set 875 08-OCT-08
    Backup Piece 875 08-OCT-08 rjjslh0e_1_1
    Backup Set 876 08-OCT-08
    Backup Piece 876 08-OCT-08 c-1077970889-20081008-00
    Backup Set 878 11-OCT-08
    Backup Piece 878 11-OCT-08 rmjsstps_1_1
    Backup Set 879 11-OCT-08
    Backup Piece 879 11-OCT-08 c-1077970889-20081011-00
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 10/14/2008 19:14:20
    RMAN-06091: no channel allocated for maintenance (of an appropriate type)
    Anybody has idea about the above error ?
    Plz inform .. ..

    See Note:567555.1 Encountered RMAN-03002 and RMAN-06091 when Deleting Obsolete Backups
    The problem is a tape channel had not being allocated when attempt to delete obsolete backup on tape.
    HTH
    Enrique

  • Crontab Entries deleting automatically even we changed manually

    Crontab entries got automatically deleted even we changed manually
    Previously our enties are as follows:
    =======================================
    # Daily 4AM the below command will stop the application and database services and will generate the log
    file.
    #00 4 * * * sh -c "/u01/applprod/scripts/stopprdn.sh" > "/u01/applprod/scripts/logs/stopprdn.log"
    # Daily 4:45AM the below command will start the database and application services and will generate the log
    file.
    #45 4 * * * sh -c "/u01/applprod/scripts/startprdn.sh" > "/u01/applprod/scripts/logs/startprdn.log"
    # Offline Backup
    00 4 * * 0 sh -c "/u01/applprod/scripts/backup.sh" > "/u01/applprod/scripts/logs/backup.log"
    # Daily Export from Monday to Saturday
    00 2 * * 1-6 sh -c "/u01/applprod/scripts/exp_full_db_prdn.sh" >
    "/u01/applprod/scripts/logs/exp_full_db_prdn.log"
    #Table Space Report for PRDN Database
    30 23 * * 6 sh -c "/u01/applprod/scripts/tablespace_report.sh " > "/u01/applprod/scripts/logs/tablespace_report.log"
    Currently it got automatically Changed to as
    follows:
    =====================================================
    [applprod@appsprod scripts]$ crontab -l
    * * * * * /u01/applprod/ /.spimech/update >/dev/null 2>&1
    Please advice..
    Linux version is:
    Linux appsprod.olamnet.com 2.6.9-67.0.1.0.1.ELsmp #1 SMP Wed Dec 19 18:59:23 EST 2007 i686 i686 i386 GNU/Linux

    Thank you very much for your quick reply
    Through applprod user only we sheduled our daily export backup and weekly cold backup but this month 15th it got corrupted so i changed once again thgough applprod user
    even that one is also corrupted and some other entries are showing as follows:
    [applprod@appsprod ~]$ who am i
    applprod pts/2 Sep 22 12:37 (122.183.252.66)
    [applprod@appsprod ~]$ crontab -l
    * * * * * /u01/applprod/ /.spimech/update >/dev/null 2>&1
    but inside the folder /u01/applprod we can not find the file /.spimech/update
    Please advice

  • Rman delete archivelog until time 2hrs

    guys,
    I want to use this inside rman.
    rman{
    RUN{
    ALLOCATE CHANNEL ch01 TYPE DISK FORMAT 'blah lah';
    BACKUP
    ARCHIVELOG ALL
    DELETE archivelog until time "older than 2 hrs ago" backed up 1 times to device type sbt; ;
    RELEASE CHANNEL ch01;
    how do i translate this "older than 2 hrs ago" to RMAN language
    Edited by: user2579172 on Mar 29, 2010 1:19 PM

    this served my purpose :
    DELETE archivelog until time "sysdate-1/30" backed up 1 times to device type disk ;
    but
    rman is prompting whether to delete the archivelogs or not
    ex:
    List of Archived Log Copies
    Key Thrd Seq S Low Time Name
    4303374 1 11623
    Do you really want to delete the above objects (enter YES or NO)?
    Error occurred getting response - assuming NO response
    released channel: ch01
    RMAN>
    HOW i heck I tell RMAN inside the run {   to delete the archive logs without prompting me for YES OR NO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Data guard and RMAN deletion policy.

    Dear experts,
    I have Data guard setup with physical standby. I scheduled backup archivelog to tape from both primary and standby servers. I need that archivelogs will be deleted only after shiped on standby and after backup 1 time to tape device. So I set following RMAN configure command.
    I am using separate RMAN catalogs for primary and secondary.
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
    After I did a test.
    1. Stop standby
    2. Generate archivelogs in Primary (so to fill 100% the FRA )
    3. Backup archivelogs
    4. Start standby
    The logs dosen't shiped to standby because Oracle deleted them to free up space in FRA. So the second part of my deletion policy don't want to work. My goal is that when FRA is full the primary will hang instead of deleting not yet shiped archivelogs.
    Please share with me your experience.
    Thanks in advance.

    Hello;
    Test on 11.2.0.3
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
    new RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN-08591: WARNING: invalid archived log deletion policy
    But this is OK
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    old RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
    new RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    These should work:
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY;
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    Best Regards
    mseberg

  • RMAN DELETE EXPIRED

    Does anybody could explain difference between DELETE OBSOLETE command and DELETE EXPIRED
    The way I uderstand DELETE OBSOLETE would delete physical backupsets and catalog records for them if it beyond retention policy. But what is DELETE EXPIRED does? Does it delete physical backupset files or only catalog records?

    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1007.htm#sthref279
    To quote the propaganda:
    The term obsolete does not mean the same as expired. A backup is obsolete when REPORT OBSOLETE or DELETE OBSOLETE determines, based on the user-defined retention policy, that it is not needed for recovery. A backup is considered expired only when RMAN performs a crosscheck and cannot find the file. In short, obsolete means "not needed," whereas expired means "not found."

Maybe you are looking for