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.

Similar Messages

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

  • 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

  • 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

  • When is delete all obsolete backups triggered in Oracle 11g DB

    I have a query as to when delete all obsolete backups triggered in Oracle 11g DB. We changed the RMAN retention policy to 10 days from 14 days in our setup. Is it triggered manually by delete all obsolete from Availablity->Manage Current Backups in OEM or is it triggered automatically every time RMAN backup is done?
    I hope, my question is clear.
    Please revert with the reply to my query.
    Regards

    975148 wrote:
    I have a query as to when delete all obsolete backups triggered in Oracle 11g DB. We changed the RMAN retention policy to 10 days from 14 days in our setup. Is it triggered manually by delete all obsolete from Availablity->Manage Current Backups in OEM or is it triggered automatically every time RMAN backup is done?
    I hope, my question is clear.
    Please revert with the reply to my query.
    Regards
    First, I would never manage my backups in OEM.  When the crunch comes at 2:00 am, I don't want ever more moving parts to be involved in recovery.
    Second, the only thing approaching a "triggering" of deletion of backups is if your backups are in the FRA ... rman will, at the time of making a backup .. attempt to delete obsolete backups if necessary to free up space in the FRA.
    Other than that, oboslete backups are only deleted in response to a direct DELETE OBSOLETE command.  This command may optionally ( as shown by TigerDBA) include a run-time obsolesence rule, or it may depend on the standing configuration.
    Another thing to note is that backups are NOT marked as obsolete.  They are EVALUATED for obsolescence in response to a DELETE OBSOLETE or REPORT OBSOLETE command.
    And one final thing to not is that all recovery must begin with a full backup.  That would be the most recent full (or level 0 incremental) backup prior to the point in time to which you need to recover.  That means the most recent full (or level 0 incremental) backup will never be considered obsolete, regardless of how old it is.

  • RMAN fails to delete obsolete backup in OSB

    Hi All,
    I am trying to delete my obsolete backups through RMAN and I get this error:
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_cat_delete: delete failed for piece 0hmlsu6q_1_2 (Oracle Secure Backup error: user does not have sufficient rights)
    I am not clear why Oracle Secure backup throws error that the user does not have sufficient rights./.
    Below are the commands that I am using in the script:
    3> ALLOCATE CHANNEL TAPE01 DEVICE TYPE SBT_TAPE;
    4> CROSSCHECK BACKUP;
    5> CROSSCHECK ARCHIVELOG ALL;
    6> CROSSCHECK COPY;
    7> report obsolete recovery window of 60 days device type
    8> report obsolete recovery window of 7 days device type disk
    9> delete noprompt obsolete recovery window of 60 days device type SBT_TAPE;
    10> delete noprompt obsolete recovery window of 7 days device type DISK;
    Any help is appreciated..
    Thanks..

    In my case, the problem was on OSB user permition.
    On user you have to preauth. admin users to the host where database is located.
    regards..
    Virgilio

  • Rman error when i am doing backup archivelog delete input

    archive log filename=+FRA01/osondemand/archivelog/2012_02_27/thread_2_seq_15028.7182.776323223 recid=122876 stamp=77
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/27/2012 05:23:14
    RMAN-10015: error compiling PL/SQL program
    RMAN-10033: error during compilation of job step 3: ORA-00603: ORACLE server session terminated by fatal error
    ORA-04030: out of process memory when trying to allocate 272 bytes (PL/SQL DIANA,PTG: No
    10.2.04
    windows
    two node rac
    please help me with above error
    thanks for help

    Hi;
    Duplicate post:
    rman error when taking backup archivelog all delete input
    Please close your othere thread as answered and keep updating your other thread here
    Regard
    Helios

  • Rman error when taking backup archivelog all delete input

    archive log filename=+FRA01/osondemand/archivelog/2012_02_27/thread_2_seq_15028.7182.776323223 recid=122876 stamp=77
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/27/2012 05:23:14
    RMAN-10015: error compiling PL/SQL program
    RMAN-10033: error during compilation of job step 3: ORA-00603: ORACLE server session terminated by fatal error
    ORA-04030: out of process memory when trying to allocate 272 bytes (PL/SQL DIANA,PTG: No
    10.2.04
    windows
    two node rac
    please help me with above error
    thanks for help

    Hi;
    Duplicate post
    Re: rman error when i am doing backup archivelog delete input
    Regard
    Helios

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

  • RMAN-06207

    We had database which used regular hot backup scripts. I am in process of configure this database to use RMAN as backup tool.
    After first couple backup runs (with delete obsolete) I am getting this warning error:
    RMAN-06207: WARNING: 2 objects could not be deleted for DISK channel(s) d
    RMAN-06208: to mismatched status. Use CROSSCHECK command to fix
    RMAN-06210: List of Mismatched objects
    RMAN-06211: ==========================
    RMAN-06212: Object Type Filename/Handle
    RMAN-06213: --------------- ---------------------------------------------
    RMAN-06214: Datafile Copy /u10/oraback/DPDEVUG/HOT/control1DPDEVUG.ctl
    RMAN-06214: Datafile Copy /u10/oraback/DPDEVUG/HOT/control2DPDEVUG.ctl
    I executed : crosscheck archivelog all and stll getting this warning.
    Any ideas?

    You are having a problems on datafile copies.
    You need to
    crosscheck copy of controlfile;
    as far as I know.
    Sybrand Bakker
    Senior Oracle DBA

  • RMAN show archivelog deletion policy;

    RMAN> show archivelog deletion policy;
    RMAN configuration parameters are:
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    What choices i have for its deletion policy? I want to carry only 30 days archivelogs , How i can chnage that?

    Hello,
    These are the options.
    When backups of archived redo log files are taken on the standby database:
    1)Issue the following command on the primary database:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    2) Issue the following command on the standby database:
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    When backups of archived redo log files are taken on the primary database:
    1) Issue the following command on the standby database:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    2) Issue the following command on the primary database:
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    Check this url for more info
    https://dpt-info.u-strasbg.fr/doc/oracle/server.102/b14239/rman.htm
    -Sri

  • How do I setup RMAN not to delete archive log files on the source database so GoldenGate can process DDL/DML changes?

    I want to setup RMAN not to delete any archive log files that will be used by GoldenGate.   Once GoldenGate is completed with the archive log file, the archive log file can be backup and deleted by RMAN.   It's my understanding that I can issue the following command "REGISTER EXTRACT <ext_name>, LOGRETENTION" to enable to functionally.   Is this the only thing I need to do to execute to enable this functionally?

    Hello,
    Yes this is the rigth way  using clasic capture.
    Using the command : REGISTER EXTRACT Extract_name LOGRETENTION.
    Create a Oracle Streams Group Capture (Artificial)  that prevent RMAN archive deletion if these are pending to process for Golden Gate capture process.
    You can see this integration doing a SELECT * FROM DBA_CAPTURE; after execute the register command.
    Then, when RMAN try to delete a archive file pending to process for GG this warning appear AT RMAN logs:
    Error:     RMAN 8317 (RMAN-08317 RMAN-8317)
    Text:     WARNING: archived log not deleted, needed for standby or upstream capture process.
    Then , this is a good manageability feature. I think is a 11.1 GG new feature.
    Tip. To avoid RMAN backup multiples times a archive pending to process, there is a option called BACKUP archivelog not backed 1 times.
    If you remove a Capture process that is registered with the database you need to use this comand to remove the streams capture group:
    unREGISTER EXTRACT extract_name LOGRETENTION;
    Then if you query dba_capture, the artificial Streams group is deleted.
    I hope help.
    Regards
    Arturo

  • Delete mail from server when deleting from mail

    I like Mail.
    But - the ONE feature I miss from Entourage is this:
    Delete mail from server when deleting the trash
    Mail can be set to delete messages from the server -- after downloading to the local computer. OK - BUT - I read my email from 3 computers. I want to keep the messages on the server - unless I delete them after trashing - and to read them on 3 computers.
    The BEST way is to delete when I trash them -- NOT when I read them.
    Using the mail program to see all messages on the server and to then delete them one-by-one is a major PITA.
    How can I tell Apple to add this feature?
    Dick
    Dual 2.7 G5, intel iMac, 3 G4 Macs, 2 iPods   Mac OS X (10.4.6)  

    Use the "When moved from Inbox" option that should do it. If you trash it then it goes, if you move it goes... HTH
    Siberian

  • PURCHASE ORDER STATUS :When Deleting ALL ITEMS.

    Hi experts,
    I need  to make purchase order status stay  " Release Compleated " when deleting all items.
    Anyone Know How to do it?
    Or anyone Know how to use BAPI_PO_CHANGE in BAdI : ME_PROCESS_PO_CUST 
    In my project , I use Release Strategy of purchase orders, and there is a case of deleting all items.
    In this situation, purchase order status returns to "Active " and release strategy tab disappears.
    This is our problem.
    I need to make purchase order status stay  " Release Compleated " and prevent  release strategy tab disappearing.
    I tried to update the fields EREKZ(final invoice) and ELIKZ(delivery completed) in
    BAdI : ME_PROCESS_PO_CUST  Method : PROCESS_ITEM using BAPI_PO_CHANGE according to SAP Note 456691.
    But BAPI_PO_CHANGE couldn't update EREKZ because of our customize , and I couldn't find how to use
    BAPI_PO_CHANGE in the BAdI.
    Anyone know solutions to solve this problem?
    Thanks a lot.
    Regards,
    TKD

    Hi,
    please review the following information in SAP Note No. 456691 as
    copied below:
    18. Question:
    When are the header conditions updated if a purchase order item is
    deleted?
    Answer:
    If a purchase order item is deleted, the item is marked as 'statistical'
    (field EKPO-STAPO = X) and the change is reflected in the header
    conditions.
    However, if for the item the final invoice indicator(EKPO-EREKZ) or the
    inward delivery completed indicator (EKPO-ELIKZ) is set, the item is not
    marked as 'statistical' (EKPO-STAPO is not set) and thus the header
    conditions are not updated.
    I hope this helps you
    BR
    Nadia Orlandi

Maybe you are looking for