6 Replies Latest reply on Apr 30, 2010 7:09 AM by 701636

    RMAN doesnt delete Standby Archivelogs

    701636
      piece handle=arch-s7618-p1-t715652396 tag=TAG20100407T001953 comment=API Version 2.0,MMS Version 5.0.0.0
      channel ch01: backup set complete, elapsed time: 00:02:17
      RMAN-08137: WARNING: archive log not deleted as it is still needed
      archive log filename=/u06/DBFR/SUSM1C/arch_SUSM1C_1595_1_680380890.dbf thread=1 sequence=1595
      RMAN-08137: WARNING: archive log not deleted as it is still needed
      archive log filename=/u06/DBFR/SUSM1C/arch_SUSM1C_1596_1_680380890.dbf thread=1 sequence=1596



      I keep seeing this messages when I try to backup archive logs.
      Please note that this is a standby database.

      Could someone let me know why it doesn delete these ?
        • 1. Re: RMAN doesnt delete Standby Archivelogs
          758358
          Have these logs been applied to the standby by media recovery? Check v$archived_log, if they haven't been applied then RMAN wont delete them as it knows they are still needed.

          Thanks
          Paul
          • 2. Re: RMAN doesnt delete Standby Archivelogs
            701636
            SQL> select thread#, sequence#, ARCHIVED, APPLIED, STATUS from v$archived_log;

            THREAD# SEQUENCE# ARC APP S
            ---------- ---------- --- --- -
            1 1 YES NO D
            1 2 YES NO D

            :
            :
            1 1636 YES NO A
            1 1637 YES NO A



            --
            But if you check, it shows that APPLIED shows as status NO even from the 1st sequence.
            • 3. Re: RMAN doesnt delete Standby Archivelogs
              758358
              Hi

              Please see below explanation of the APPLIED column on this view:

              Indicates whether the archivelog has been applied to its corresponding standby database (YES) or not (NO). The value is always NO for local destinations.
              This column is meaningful at the physical standby site for the ARCHIVED_LOG entries with REGISTRAR='RFS' (which means this log is shipped from the primary to the standby database). If REGISTRAR='RFS' and APPLIED is NO, then the log has arrived at the standby but has not yet been applied. If REGISTRAR='RFS' and APPLIED is YES, the log has arrived and been applied at the standby database. You can use this field to identify archivelogs that can be backed up and removed from disk.

              If this column is not updated then that suggests your standby isn't applying logs?

              Thanks
              Paul
              • 4. Re: RMAN doesnt delete Standby Archivelogs
                jason_goucf
                also in your rman configuration set
                CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
                • 5. Re: RMAN doesnt delete Standby Archivelogs
                  Babu Baskar
                  Hello,

                  No need to check RMAN Configuration. As per paul execute the below query in standby database & post here
                  select thread#, sequence#, ARCHIVED, APPLIED, STATUS from v$archived_log;
                  • 6. Re: RMAN doesnt delete Standby Archivelogs
                    701636
                    Like I said in earlier update :


                    SQL> select thread#, sequence#, ARCHIVED, APPLIED, STATUS from v$archived_log;

                    THREAD# SEQUENCE# ARC APP S

                    --------------------------------------------------------------------------------
                    ---------- --- --- -
                    1 1 YES NO D
                    1 2 YES NO D

                    :
                    :
                    1 1636 YES NO A
                    1 1637 YES NO A




                    If you see then it shows right from sequence = 1

                    But most of the sequences including 1 onwards have been applied.

                    Only las few havent. Check the column STATUS which shows as DELETED.