Keep archived logs but deleting backup of db

Hey
I'm running a backup script every night that issues a "backup database plus archivelog" and saves the backup to disk. Due to disk space limitations I have to delete the obsolete backup taken the night before. However the "delete obsolete" also deletes the archived logs on disk. Is there a way to delete the obsolete backup but still keep the logs on disk?
Tried the "delete backup of database completed before 'sysdate-1' but I cant seem to get passed the promting for deletion - it has to run automatically.
Thanks for any advice..

Why don't you work with retention and than you delete the obsolete?
delete backup of database will remove the full backup of the database (datafiles, archivelog, spfile). You can create a script to delete the backup of a given list of datafiles.
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Archive Log          540    26-MAY-05          /db/ARON/fs1/archived_for_logminer/1_1.dbf
Archive Log          541    26-MAY-05          /db/ARON/fs1/archived_for_logminer/1_2.dbf
RMAN> configure retention policy to redundancy 1;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           3125   22-JUL-05        
  Backup Piece       3127   22-JUL-05          /db/ARON/BACKUP/RMAN/backup_ARON_564316052_208_1_6ggq5hsk_1_1.bck
Backup Set           3126   22-JUL-05        
  Backup Piece       3128   22-JUL-05          /db/ARON/BACKUP/RMAN/backup_ARON_564316052_207_1_6fgq5hsk_1_1.bck
Backup Set           3139   22-JUL-05        
  Backup Piece       3140   22-JUL-05          /db/ARON/BACKUP/RMAN/backup_ARON_564316097_209_1_6hgq5hu1_1_1.bck
Backup Set           3190   24-OCT-05        
  Backup Piece       3193   24-OCT-05          /db/ARON/BACKUP/RMAN/backup_ARON_572546170_212_1_6kh20n3q_1_1.bck
Backup Set           3191   24-OCT-05        
  Backup Piece       3194   24-OCT-05          /db/ARON/BACKUP/RMAN/backup_ARON_572546170_213_1_6lh20n3q_1_1.bck
Backup Set           3192   24-OCT-05        
  Backup Piece       3195   24-OCT-05          /db/ARON/BACKUP/RMAN/backup_ARON_572546180_214_1_6mh20n44_1_1.bck
Archive Log          540    26-MAY-05          /db/ARON/fs1/archived_for_logminer/1_1.dbf
Archive Log          541    26-MAY-05          /db/ARON/fs1/archived_for_logminer/1_2.dbfBye, Aron

Similar Messages

  • Recovery window retention policy deletes archive logs before a backup?

    Hi All,
    Oracle 11G on Windows 2008 R2
    This afternoon, I changed my RMAN retention policy from 'RETENTION POLICY REDUNDANCY 3' to RETENTION POLICY RECOVERY WINDOW OF 3 DAYS'
    However, i checked tonight and after my daily backup ran, all the archive logs prior to the backup had been deleted! Thus meaning i dont think i can restore to any point in time, prior to my daily backup. All the .arc logs were there after the backup. So i tried another test and kicked off the daily backup again. During the backup process, the archive logs got deleted again! Now i don't have any archive logs..
    Is this proper behaviour of RETENTION POLICY RECOVERY WINDOW?? I thought it would keep all the files needed for me to restore to any point in time for the previous 3 days. When i used REDUNDANCY, with my daily backups, it kept 3 days worth of backups+ archive logs so i could restore point-in-time to any point. How can i use RECOVERY WINDOW so that i can actually restore to any point-in-time for the 3 days??
    I wanted to change to RECOVERY WINDOW since i read that by using REDUNDANCY it only keeps X copies of a backup (so if i ran the backup 3 times in a day, i would only have those 3).
    Thanks in advance.

    Hi All,
    Here is the SHOW ALL output:
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name MMSPRD7 are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
    D TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\DATABASE\ORA11G\DATABASE\SNCFM
    MSPRD7.ORA'; # default
    Here is the RMAN script:
    Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 20 23:03:12 2014
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: XXX (DBID=)
    RMAN> CROSSCHECK ARCHIVELOG ALL;
    2> CROSSCHECK BACKUPSET;
    3> CROSSCHECK BACKUP;
    4> CROSSCHECK COPY;
    5> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
    6> DELETE NOPROMPT EXPIRED BACKUPSET;
    7> DELETE NOPROMPT OBSOLETE;
    8> BACKUP CURRENT CONTROLFILE;
    9> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT;
    Also, not sure if you needed the whole RMAN output, but here is the deletion part:
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 3 days
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           1392   15-JAN-14        
      Backup Piece       1392   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP
    Backup Set           1393   15-JAN-14        
      Backup Piece       1393   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP
    Backup Set           1397   16-JAN-14        
      Backup Piece       1397   16-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP
    Backup Set           1400   17-JAN-14        
      Backup Piece       1400   17-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP
    deleted backup piece
    backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP RECID=1392 STAMP=836938856
    deleted backup piece
    backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP RECID=1393 STAMP=836940124
    deleted backup piece
    backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP RECID=1397 STAMP=837025228
    deleted backup piece
    backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP RECID=1400 STAMP=837111700
    Deleted 4 objects

  • Backup archive log with delete all input clause

    Our database is 10.2.0.3 RAC db and database server is window 2003.
    Our RMAN catalog db was down for a couple of weeks. During this two weeks period we use control file instead. But when I compare the log files before using control file and after going back to catalog db I found the following differences. I also pasted backup script below. It looks like that after we reuse the catalog db it is able to delete all archive logs as soon as it is backed up. The only change I can think of is one of the archive log destination is changed from F:\archive to G:\archive. This db has a physical standby db which is not up to date. Can you help me to figure out why this differences in the backup process since I am kind of worried if we bring the standby db up to date we will not be able to ship the archive log since they are deleted from the backup process. Thank you so much for your help. Shirley
    10> resync catalog;
    11> #change archivelog all crosscheck;
    12> crosscheck archivelog all;
    13>
    14> #Backup Database and archive log files.
    15> backup as compressed backupset
    16> incremental level 0 format 'F:\backup\%d_LVL0_%T_%u_s%s_p%p' filesperset 5 tag 'INDRAC'
    17> database plus archivelog format 'F:\backup\%d_LVL0_%T_%u_s%s_p%p'
    18> filesperset 10 tag 'INDRAC'
    19> delete all input;
    Before using control file:
    channel ORA_DISK_2: finished piece 1 at 24-MAY-08
    piece handle=F:\BACKUP\PRODRAC_LVL0_20080524_04JH7588_S41988_P1 tag=INDRAC comment=NONE
    channel ORA_DISK_2: backup set complete, elapsed time: 00:04:17
    RMAN-08137: WARNING: archive log not deleted as it is still needed
    archive log filename=F:\ARCHIVE\PRODRAC_004_04966_0575926036.ARC thread=4 sequence=4966
    RMAN-08137: WARNING: archive log not deleted as it is still needed
    archive log filename=E:\ARCHIVE\PRODRAC_004_04966_0575926036.ARC thread=4 sequence=4966
    RMAN-08137: WARNING: archive log not deleted as it is still needed
    archive log filename=F:\ARCHIVE\PRODRAC_004_04967_0575926036.ARC thread=4 sequence=4967
    RMAN-08137: WARNING: archive log not deleted as it is still needed
    archive log filename=E:\ARCHIVE\PRODRAC_004_04967_0575926036.ARC thread=4 sequence=4967
    After went back to catalog:
    channel ORA_DISK_2: backup set complete, elapsed time: 00:02:47
    channel ORA_DISK_2: deleting archive log(s)
    archive log filename=G:\ARCHIVE\PRODRAC_004_05760_0575926036.ARC recid=51689 stamp=660017344
    archive log filename=E:\ARCHIVE\PRODRAC_004_05760_0575926036.ARC recid=51688 stamp=660017344
    archive log filename=G:\ARCHIVE\PRODRAC_004_05761_0575926036.ARC recid=51697 stamp=660032069
    archive log filename=E:\ARCHIVE\PRODRAC_004_05761_0575926036.ARC recid=51696 stamp=660032069
    archive log filename=E:\ARCHIVE\PRODRAC_004_05762_0575926036.ARC recid=51704 stamp=660051690
    archive log filename=G:\ARCHIVE\PRODRAC_004_05762_0575926036.ARC recid=51705 stamp=660051690
    archive log filename=E:\ARCHIVE\PRODRAC_004_05763_0575926036.ARC recid=51710 stamp=660061718
    archive log filename=G:\ARCHIVE\PRODRAC_004_05763_0575926036.ARC recid=51711 stamp=660061718
    archive log filename=E:\ARCHIVE\PRODRAC_004_05764_0575926036.ARC recid=51716 stamp=660069980
    archive log filename=G:\ARCHIVE\PRODRAC_004_05764_0575926036.ARC recid=51717 stamp=660069980
    archive log filename=E:\ARCHIVE\PRODRAC_004_05765_0575926036.ARC recid=51720 stamp=660081117
    archive log filename=G:\ARCHIVE\PRODRAC_004_05765_0575926036.ARC recid=51721 stamp=660081117
    archive log filename=G:\ARCHIVE\PRODRAC_004_05766_0575926036.ARC recid=51723 stamp=660087215
    archive log filename=E:\ARCHIVE\PRODRAC_004_05766_0575926036.ARC recid=51722 stamp=660087214
    channel ORA_DISK_1: finished piece 1 at 14-JUL-08
    piece handle=F:\BACKUP\PRODRAC_LVL0_20080714_1MJLG8GQ_S45110_P1 tag=INDRAC comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:04:43

    Shirley,
    If there was no change to the E: then the logs should have been kept (RMAN-8137) unless they were possibly aged out of the controlfile (unlikely since it defaults to 65K) or have been applied already. (The F: logs would have been marked as EXPIRED at the next crosscheck). Check to see which are EXPIRED:
    RMAN> list expired archivelog all;
    To see the earliest log:
    select sequence# from v$log_history where rownum <2;
    Have you checked the V$MANAGED_STANDBY to insure they were not already applied? Given that your latest rman log shows logs being deleted with no RMAN-8137 raised would indicate that they are not needed for the standby.

  • Archive Log vs Full Backup Concept

    Hi,
    I just need some clarification on how backups and archive logs work. Lets say starting at 1PM I have archive logs 1,2,3,4,5 and then I perform a full backup at 6PM.
    Then I resume generating archive logs at 6PM to get logs 6,7,8,9,10. I then stop at 11PM.
    If my understanding is correct, the archive logs should allow me to restore oracle to a point in time anywhere between 1PM and 11PM. But if I only have the full backup then I can only restore to a single point, which is 6PM. Is my understanding correct?
    Do the archive logs only get applied to the datafiles when the backup occurs or only when a restore occurs? It doesn't seem like the archive logs get applied on the fly.
    Thanks in advance.

    thelok wrote:
    Thanks for the great explanation! So I can do a point in time restore from any time since the datafiles have last been written (or from when I have the last set of backed up datafiles plus the archive logs). From what you are saying, I can force the datafiles to be written from the redo logs (by doing a checkpoint with "alter set archive log current" or "backup database plus archivelog"), and then I can delete all the archive logs that have a SCN less than the checkpoint SCN on the datafiles. Is this true? This would be for the purposes of preserving disk space.Hi,
    See this example. I hope this explain your doubt.
    # My current date is 06-11-2011 17:15
    # I not have backup of this database
    # My retention policy is to have 1 backup
    # I start listing  archive logs.
    RMAN> list archivelog all;
    using target database control file instead of recovery catalog
    List of Archived Log Copies
    Key     Thrd Seq     S Low Time            Name
    29      1    8       A 29-10-2011 12:01:58 +HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837
    30      1    9       A 31-10-2011 23:00:30 +HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025
    31      1    10      A 03-11-2011 23:00:23 +HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105
    32      1    11      A 04-11-2011 23:28:23 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065
    33      1    12      A 05-11-2011 23:28:49 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349
    ## See I have archive logs from time "29-10-2011 12:01:58" until "05-11-2011 23:28:49" but I dont have any backup of database.
    # So I perfom backup of database including archive logs.
    RMAN> backup database plus archivelog delete input;
    Starting backup at 06-11-2011 17:15:21
    ## Note above RMAN forcing archive current log, this archivelog generated will be usable only for previous backup.
    ## Is not my case... I don't have backup of database.
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=159 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8 recid=29 stamp=766018840
    input archive log thread=1 sequence=9 recid=30 stamp=766278027
    input archive log thread=1 sequence=10 recid=31 stamp=766366111
    input archive log thread=1 sequence=11 recid=32 stamp=766516067
    input archive log thread=1 sequence=12 recid=33 stamp=766516350
    input archive log thread=1 sequence=13 recid=34 stamp=766516521
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:23
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:15:38
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 tag=TAG20111106T171521 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837 recid=29 stamp=766018840
    archive log filename=+HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025 recid=30 stamp=766278027
    archive log filename=+HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105 recid=31 stamp=766366111
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065 recid=32 stamp=766516067
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349 recid=33 stamp=766516350
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_13.414.766516521 recid=34 stamp=766516521
    Finished backup at 06-11-2011 17:15:38
    ## RMAN finish backup of Archivelog and Start Backup of Database
    ## My backup start at "06-11-2011 17:15:38"
    Starting backup at 06-11-2011 17:15:38
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=+HR/dbhr/datafile/system.386.765556627
    input datafile fno=00003 name=+HR/dbhr/datafile/sysaux.396.765556627
    input datafile fno=00002 name=+HR/dbhr/datafile/undotbs1.393.765556627
    input datafile fno=00004 name=+HR/dbhr/datafile/users.397.765557979
    input datafile fno=00005 name=+BFILES/dbhr/datafile/bfiles.257.765542997
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:39
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:03
    piece handle=+FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539 tag=TAG20111106T171539 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:24
    Finished backup at 06-11-2011 17:16:03
    ## And finish at "06-11-2011 17:16:03", so I can recovery my database from this time.
    ## I will need archivelogs (transactions) which was generated during backup of database.
    ## Note during backup some blocks are copied others not. The SCN is inconsistent state.
    ## To make it consistent I need apply archivelog which have all transactions recorded.
    ## Starting another backup of archived log generated during backup.
    Starting backup at 06-11-2011 17:16:04
    ## So automatically RMAN force another "checkpoint" after backup finished,
    ## forcing archive current log, because this archivelog have all transactions to bring database in a consistent state.
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=14 recid=35 stamp=766516564
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:16:05
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:06
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565 tag=TAG20111106T171604 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_14.414.766516565 recid=35 stamp=766516564
    Finished backup at 06-11-2011 17:16:06
    ## Note: I can recover my database from time "06-11-2011 17:16:03" (finished backup full)
    ##  until "06-11-2011 17:16:04" (last archivelog generated) that is my recover window in this scenary.
    ## Listing Backup I have:
    ## Archive Logs in backupset before backup full start - *BP Key: 40*
    ## Backup Full database in backupset - *BP Key: 41*
    ##  Archive Logs in backupset after backup full stop - *BP Key: 42*
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    40      196.73M    DISK        00:00:15     06-11-2011 17:15:37
            *BP Key: 40*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171521
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
      List of Archived Logs in backup set 40
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    8       766216     29-10-2011 12:01:58 855033     31-10-2011 23:00:30
      1    9       855033     31-10-2011 23:00:30 896458     03-11-2011 23:00:23
      1    10      896458     03-11-2011 23:00:23 937172     04-11-2011 23:28:23
      1    11      937172     04-11-2011 23:28:23 976938     05-11-2011 23:28:49
      1    12      976938     05-11-2011 23:28:49 1023057    06-11-2011 17:12:28
      1    13      1023057    06-11-2011 17:12:28 1023411    06-11-2011 17:15:21
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    41      Full    565.66M    DISK        00:00:18     06-11-2011 17:15:57
            *BP Key: 41*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171539
            Piece Name: +FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539
      List of Datafiles in backup set 41
      File LV Type Ckp SCN    Ckp Time            Name
      1       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/system.386.765556627
      2       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/undotbs1.393.765556627
      3       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/sysaux.396.765556627
      4       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/users.397.765557979
      5       Full 1023422    06-11-2011 17:15:39 +BFILES/dbhr/datafile/bfiles.257.765542997
    BS Key  Size       Device Type Elapsed Time Completion Time
    42      3.00K      DISK        00:00:02     06-11-2011 17:16:06
            *BP Key: 42*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171604
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565
      List of Archived Logs in backup set 42
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    14      1023411    06-11-2011 17:15:21 1023433    06-11-2011 17:16:04
    ## Here make sense what I trying explain
    ## As I don't have backup of database before of my Last backup, all archivelogs generated before of my backup full is useless.
    ## Deleting what are obsolete in my env, RMAN choose backupset 40 (i.e all archived logs generated before my backup full)
    RMAN> delete obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    *Backup Set           40*     06-11-2011 17:15:37
      Backup Piece       40     06-11-2011 17:15:37 +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted backup piece
    backup piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 recid=40 stamp=766516523
    Deleted 1 objectsIn the above example, I could before starting the backup run "delete archivelog all" because they would not be needed, but to show the example I follow this unnecessary way. (backup archivelog and delete after)
    Regards,
    Levi Pereira
    Edited by: Levi Pereira on Nov 7, 2011 1:02 AM

  • RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
    Check the below queries.
    Primary:-
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    Standby:-
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
    HTH.

  • WARNING: archive log not deleted as it is still needed

    Our Oralce Database is a single node database of version 10.1.0.
    Dataguard/Standby is not configured.....we are executing the following command for archivelog backup
    run
    allocate channel c1 device type sbt;
    backup archivelog all delete input;
    This script is successfull in backingup all the archvied log files however it is not deleteing the input files. Instead it gives the warning....
    "WARNING: archive log not deleted as it is still needed"
    What could be the problem?

    If you do a Metalink seach on "WARNING: archive log not deleted as it is still needed." you'll find a couple of documents that explain the issue.
    The short answer is that RMAN has backed up logs which have not yet shipped to standby, so it won't delete them, cause they're still needed till they're successfully shipped to standby.
    -Mark

  • Current archive log got deleted, how to recover using previous archive log?

    Hi
    My current log sequence #819 and it is got deleted and no choice to get it back and I have previous archived logs with sequences #814 to 818.
    When I starting my database it is showing that use 'MUST USE RESETLOGS OR NORESETLOGS option for database open then I used the command
    SQL> ALTER DATABASE OPEN RESETLOGS;
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: 'E:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF'
    SQL> alter database recover;
    alter database recover
    ERROR at line 1:
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> alter database recover using backup controlfile;
    alter database recover using backup controlfile
    ERROR at line 1:
    ORA-00279: change 8433746 generated at 01/15/2013 19:51:59 needed for thread 1
    ORA-00289: suggestion :
    E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_01_16\O1_MF_1_819_
    %U_.ARC
    ORA-00280: change 8433746 for thread 1 is in sequence #819
    now I don't have the archive log with sequence 819, I have recover from 818. please tell me how to do it?

    You probably should post to the correct forum too: Recovery Manager (RMAN)
    cheers

  • Archive log backupset deletion

    Hi all,
    DB version is 10.2.0.4 Have recently changed the retention policy from backup from 2 to 1. After changing the redundancy to 1 Datafile backup sets are getting deleted after backup and all archivelog backupsets remain in the backup location. How do i delete those archivelog backupsets during backup.
    thanks,
    baskar.l

    baskar.l wrote:
    Hi all,
    DB version is 10.2.0.4 Have recently changed the retention policy from backup from 2 to 1. After changing the redundancy to 1 Datafile backup sets are getting deleted after backup and all archivelog backupsets remain in the backup location. How do i delete those archivelog backupsets during backup.
    thanks,
    baskar.lSince these are backups of archivelogs, their final determination of 'obsolete' has to be measured against the backupsets of the datafiles. Are you also taking regular backups of the datafiles?
    for instance, you set retention policy to redundancy of 1. You take a full, Incremental 0 backup. Then you take an incremental level 1 backup. Then you take another incremental level 1 backup. Then you take a backup of your archivelogs. THen you take another backup of archive logs. And another. At this point, nothing is obsolete, because it is all still required to perform a recovery from that one and only full backup.

  • A Group of Archive Logs Will Not Backup

    I restored a database to a different server, and while that was happening I copied some logarchives out of the production logarchive directory. After the restore completed, but before I put those logarchives back into that directory, I ran CHANGE ARCHIVELOG ALL CROSSCHECK on the production server to sync the catalog with the database. That was a mistake to do that yet. I then put the logarchives back into the production logarchive directory and tried to run a logarchive backup. I should have put these files back before running crosscheck. Now I receive this error:
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
    How can I backup these production logarchives that I copied back into the logarchive directory?
    Thank you.

    Database version? To know that makes it easier to advice, because since RMAN was introduced in 8.0 there were some changes.
    In 10g and higher use 'catalog archivelog...'.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
    Werner

  • Restoring archive log after cold backup

    Hello forums users,
    I read many thing on this topic but I didn't find the good answer.
    I performed a cold backup each sunday.
    My database is in ARCHIVE LOG mode.
    Is it possible to restore ARCHIVE LOG files after restoring COLD backup?
    Sunday : cold backup
    Monday : new archive log have been created since cold backup
    Tuesday : same as Monday
    Wednesday : I would like to restore to Monday 22:00 for example
    Can I restore cold backup + apply archive log until Monday 22:00 ?
    Regards,
    Guillaume

    recover database using backup controlfile until cancel|time|logseq|scn
    will do this and prompt you for the archivelogs.
    Known as 'incomplete recovery'
    Hth
    Sybrand Bakker
    Senior Oracle DBA

  • RMAN-08137: WARNING: archived log not deleted as it is still needed

    I am trying to delete archive logs older than 7 days in streams environment.
    1) we dont have a standby database
    2) checkpoint_retention_time = 7
    Please help me with this.
    Regards,
    Mike

    SQL> set serveroutput on
    DECLARE
    hScn number := 0;
    lScn number := 0;
    sScn number;
    ascn number;
    alog varchar2(1000);
    begin
    select min(start_scn), min(applied_scn) into sScn, ascn
    from dba_capture;
    DBMS_OUTPUT.ENABLE(2000);
    for cr in (select distinct(a.ckpt_scn)
    from system.logmnr_restart_ckpt$ a
    where a.ckpt_scn <= ascn and a.valid = 1
    and exists (select * from system.logmnr_log$ l
    where a.ckpt_scn between l.first_change# and l.next_change#)
    order by a.ckpt_scn desc)
    loop
    if (hScn = 0) then
    hScn := cr.ckpt_scn;
    else
    lScn := cr.ckpt_scn;
    exit;
    end if;
    end loop;
    if lScn = 0 then
    lScn := sScn;
    end if;
    dbms_output.put_line('Capture will restart from SCN ' || lScn ||' in the following file:');
    for cr in (select name, first_time
    from DBA_REGISTERED_ARCHIVED_LOG
    where lScn between first_scn and next_scn order by thread#)
    loop
    dbms_output.put_line(cr.name||' ('||cr.first_time||')');
    end loop;
    end;
    After i ran the above script from metalink i got the below output.
    When I have run the above code that is given in metalink to check the minimum archive logs required to restart streams i got the below ouput.
    Capture will restart from SCN 55313283790in the following file:
    +FLASH/ORCL/archivelog/2011_02_22/thread_1_seq_842.346.443519740 (11-MAR-11)*
    +FLASH/ORCL/archivelog/2011_02_22/thread_2_seq_832.189.440690538 (11-MAR-11)*
    Does this mean that I will not be able to delete the archive logs from 11-mar-11 ?
    Regards,
    Mike

  • RMAN-08138: WARNING: archived log not deleted - must create more backups

    I ran:
    1. CROSSCHECK ARCHIVELOG ALL
    2. DELETE EXPIRED ARCHIVELOG ALL
    I am getting this error. I am trying to free my arciver after an ORA-00257 error.
    Can anyone help me out?

    Basically this error means you are trying to delete archivelogs still needed for recovery (according to your retention policy). Develop a strategy which backs up the archivelogs in regular intervals, after a successful backup delete the archivelogs from disk, for example:
    backup archivelog all delete all input;
    Werner

  • Archive Complete, but delete job not scheduled. Issue with Archives now

    As someone tried at work to schedule archive/delete process, we are finding issues now.
    We have job scheduled for Archive but not delete. The job is archiving the messages, Meanwhile because of the growing disk space, folks deleted the archive files.
    Now Archive is Complete, but with out Deletion.
    So how do we start from scratch again
    Also if I understood correctly after deleting the infostructure the session goes into error/red light since we can no longer build the related data from the archives due to the missing infostructures right?

    Dear friend of XI,
    I fully understand the issue; sure you cannot use RSXMB_DELETE_ARCHIVED_MESSAGES as the archive files have been deleted.
    Tha paradigma of archving is that once the write phase is complete the deletion phse must complete at any rate. As this is impossible for the deleted archive files there is no way in the standard to erase the incomplete archive runs from management overview in SARA. In case you would like to clear the entries in SARA please open an OSS message such that SAP can take a look into the affected system and evaluate an individual solution for you.
    irrespective of whether you clear the management entries in SARA you can simply run another archive session. Please note that the interfaces action (field ITFACTION) reflects the action to be taken for an indivirual message. It does not depict a state, in particular it does not mean that the message has been archived already. The interface action is determined right when the mesage enters the Integration Server. Contrary, the information on whether the message has been archived alteady (or still needs to) is stored in a different statuis field.
    Best regards,
    Harald Keimer

  • RMAN not able to restore archive logs from net backup

    Hello Everybody,
    While trying to restore a datafile and then recover the database, RMAN failed with the following error stack.
    RMAN-03002: failure of recover command at 12/05/2007 09:19:24
    ORA-19870: error reading backup piece arch-s110-p1
    ORA-19615: some files not found in backup set
    ORA-19614: archivelog thread 1 sequence 231 not found in backup set
    ORA-19614: archivelog thread 1 sequence 230 not found in backup set
    ORA-19614: archivelog thread 1 sequence 229 not found in backup set
    But when I do a crosscheck the status is shown as Available. We are using net backup as MML.
    Could you please suggest any alternatives to solve this issue.
    Regards
    Satish V Chandran

    Give some other location than /tmp and see if it works.

  • KEEPING the ACTOR but DELETING the attached SCRIPT on ENTERFRAME

    Hi, new in this forum.
    Lets put it that way...On frame 50, I've got on the score 25
    buttons that are handled by 25 different(but similar) property
    scripts. These buttons could be enabled(checked) or unchecked. Now,
    when i'm going on frame 100, I compile in a linear list all the
    sprites that have been clicked. Then, using those sprite numbers,
    i'm trying to keep the actor(button) on the scene(score) on their
    checkep state, but i want that the checked buttons would be now
    impossible to click for the user. (like once you've clicked and
    pass the frame 101, the state of the button won't change even if
    you click on it.
    Please find here an example of a script that is attached to a
    button in the Attached Code.
    Thank you for helping me...kind of a big headache for
    me.

    Sorry, don't have time to read through all your code, but
    what you want
    to do sounds pretty simple. If I understand you correctly,
    simply set a
    global variable in frame 100 to tell the other sprites
    they're no longer
    active. Something like this for your frame script:
    global gclickable
    on exitFrame me
    gclickable = false
    end
    Then in each button have it look for that same global
    variable.
    Something like this:
    global gclickable
    on mouseUp me
    if gclickable = true then
    do whatever you want here
    end if
    end
    Then you'd just need to remember to set gclickable to true up
    near frame
    50 so that the buttons would actually do something when you
    wanted them to.
    Hope that helps.

Maybe you are looking for