1 2 Previous Next 21 Replies Latest reply: Jul 15, 2014 2:44 AM by Nip-Oracle RSS

    RECOVER FAILS WITH RMAN-06025

    aparm

      Hi there
      We have Oracle 11.1 running on Windows Server 2003, I did a full backup (with archivelogs) of our prod database a couple of days ago, then I tried to restore/recover the database on our test server running the same version of Oracle on Windows Server 2008R2, I have mirrored the directory structure and maintained the database name, the restore completed successfully, but I go the following errors when recovering. We are using the control file rman repository, and I catalogued the backup pieces. Could somebody tell me what is happening, I see that the backup pieces are showing as expired, I did the backup on an evening and ran the rsetore overnight and then attempted the recover in the morning?

      >LIST BACKUP OF ARCHIVELOG ALL;
      List of Backup Sets
      ===================


      BS Key  Size       Device Type Elapsed Time Completion Time
      ------- ---------- ----------- ------------ ---------------
      4309    109.79G    DISK        02:11:15     26-JUN-14     
              BP Key: 4309   Status: EXPIRED  Compressed: NO  Tag: TAG20140626T162754
              Piece Name: D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\FULL_DB11G_851272076_4392_1.BKP

        List of Archived Logs in backup set 4309
        Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
        ---- ------- ---------- --------- ---------- ---------
        1    96830   18164620049 24-JUN-14 18166336246 24-JUN-14
        1    96831   18166336246 24-JUN-14 18167224906 25-JUN-14
        1    96832   18167224906 25-JUN-14 18167741652 25-JUN-14
        1    96833   18167741652 25-JUN-14 18167945195 25-JUN-14
        1    96834   18167945195 25-JUN-14 18168326275 25-JUN-14
        1    96835   18168326275 25-JUN-14 18168570885 25-JUN-14
        1    96836   18168570885 25-JUN-14 18168812046 25-JUN-14
        1    96837   18168812046 25-JUN-14 18169265456 25-JUN-14
        1    96838   18169265456 25-JUN-14 18169825523 25-JUN-14
        1    96839   18169825523 25-JUN-14 18171843502 25-JUN-14
        1    96840   18171843502 25-JUN-14 18173183113 25-JUN-14
        1    96841   18173183113 25-JUN-14 18174856406 25-JUN-14
        1    96842   18174856406 25-JUN-14 18176268309 25-JUN-14
        1    96843   18176268309 25-JUN-14 18178147632 25-JUN-14
        1    96844   18178147632 25-JUN-14 18178551086 25-JUN-14
        1    96845   18178551086 25-JUN-14 18179765282 26-JUN-14
        1    96846   18179765282 26-JUN-14 18181604180 26-JUN-14
        1    96847   18181604180 26-JUN-14 18181873948 26-JUN-14
        1    96848   18181873948 26-JUN-14 18182317526 26-JUN-14
        1    96849   18182317526 26-JUN-14 18182617691 26-JUN-14
        1    96850   18182617691 26-JUN-14 18182949779 26-JUN-14
        1    96851   18182949779 26-JUN-14 18183700870 26-JUN-14
        1    96852   18183700870 26-JUN-14 18184719078 26-JUN-14
        1    96853   18184719078 26-JUN-14 18186347564 26-JUN-14
        1    96854   18186347564 26-JUN-14 18187689411 26-JUN-14
        1    96855   18187689411 26-JUN-14 18189619632 26-JUN-14
        1    96856   18189619632 26-JUN-14 18190710435 26-JUN-14
        1    96857   18190710435 26-JUN-14 18191348424 26-JUN-14
        1    96858   18191348424 26-JUN-14 18193327612 26-JUN-14
        1    96859   18193327612 26-JUN-14 18193676969 26-JUN-14

      BS Key  Size       Device Type Elapsed Time Completion Time
      ------- ---------- ----------- ------------ ---------------
      4312    25.46G     DISK        01:46:17     28-JUN-14     
              BP Key: 4312   Status: EXPIRED  Compressed: YES  Tag: TAG20140628T072024
              Piece Name: D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\FULL_DB11G_851412025_4396_1.BKP

        List of Archived Logs in backup set 4312
        Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
        ---- ------- ---------- --------- ---------- ---------
        1    96860   18193676969 26-JUN-14 18195132908 26-JUN-14
        1    96861   18195132908 26-JUN-14 18195653501 26-JUN-14
        1    96862   18195653501 26-JUN-14 18196547459 27-JUN-14
        1    96863   18196547459 27-JUN-14 18196978257 27-JUN-14
        1    96864   18196978257 27-JUN-14 18197190770 27-JUN-14
        1    96865   18197190770 27-JUN-14 18197448243 27-JUN-14
        1    96866   18197448243 27-JUN-14 18197683988 27-JUN-14
        1    96867   18197683988 27-JUN-14 18198295392 27-JUN-14
        1    96868   18198295392 27-JUN-14 18198881348 27-JUN-14
        1    96869   18198881348 27-JUN-14 18200450596 27-JUN-14
        1    96870   18200450596 27-JUN-14 18202037378 27-JUN-14
        1    96871   18202037378 27-JUN-14 18205278051 27-JUN-14
        1    96872   18205278051 27-JUN-14 18207445496 28-JUN-14
        1    96873   18207445496 28-JUN-14 18207958577 28-JUN-14
        1    96874   18207958577 28-JUN-14 18208152761 28-JUN-14
        1    96875   18208152761 28-JUN-14 18208590017 28-JUN-14
        1    96876   18208590017 28-JUN-14 18208815314 28-JUN-14
        1    96877   18208815314 28-JUN-14 18209053741 28-JUN-14
        1    96878   18209053741 28-JUN-14 18209728627 28-JUN-14
        1    96879   18209728627 28-JUN-14 18210325373 28-JUN-14
        1    96880   18210325373 28-JUN-14 18210399038 28-JUN-14

      BS Key  Size       Device Type Elapsed Time Completion Time
      ------- ---------- ----------- ------------ ---------------
      4314    1.90G      DISK        00:07:08     28-JUN-14     
              BP Key: 4314   Status: EXPIRED  Compressed: YES  Tag: TAG20140628T115121
              Piece Name: D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\FULL_DB11G_851428281_4398_1.BKP

        List of Archived Logs in backup set 4314
        Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
        ---- ------- ---------- --------- ---------- ---------
        1    96881   18210399038 28-JUN-14 18211042579 28-JUN-14
        1    96882   18211042579 28-JUN-14 18212580295 28-JUN-14
        1    96883   18212580295 28-JUN-14 18212824896 28-JUN-14

      RMAN> RECOVER DATABASE;
      Starting restore at 29-JUN-14
      allocated channel: ORA_DISK_1
      channel ORA_DISK_1: SID=800 device type=DISK

      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03002: failure of restore command at 06/29/2014 10:38:53
      RMAN-06026: some targets not found - aborting restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96883 and starting SCN of 18212580295 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96882 and starting SCN of 18211042579 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96881 and starting SCN of 18210399038 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96880 and starting SCN of 18210325373 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96879 and starting SCN of 18209728627 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96878 and starting SCN of 18209053741 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96877 and starting SCN of 18208815314 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96876 and starting SCN of 18208590017 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96875 and starting SCN of 18208152761 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96874 and starting SCN of 18207958577 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96873 and starting SCN of 18207445496 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96872 and starting SCN of 18205278051 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96871 and starting SCN of 18202037378 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96870 and starting SCN of 18200450596 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96869 and starting SCN of 18198881348 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96868 and starting SCN of 18198295392 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96867 and starting SCN of 18197683988 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96866 and starting SCN of 18197448243 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96865 and starting SCN of 18197190770 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96864 and starting SCN of 18196978257 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96863 and starting SCN of 18196547459 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96862 and starting SCN of 18195653501 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96861 and starting SCN of 18195132908 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96860 and starting SCN of 18193676969 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96859 and starting SCN of 18193327612 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96858 and starting SCN of 18191348424 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96857 and starting SCN of 18190710435 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96856 and starting SCN of 18189619632 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96855 and starting SCN of 18187689411 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96854 and starting SCN of 18186347564 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96853 and starting SCN of 18184719078 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96852 and starting SCN of 18183700870 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96851 and starting SCN of 18182949779 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96850 and starting SCN of 18182617691 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96849 and starting SCN of 18182317526 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96848 and starting SCN of 18181873948 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96847 and starting SCN of 18181604180 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96846 and starting SCN of 18179765282 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96845 and starting SCN of 18178551086 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96844 and starting SCN of 18178147632 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96843 and starting SCN of 18176268309 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96842 and starting SCN of 18174856406 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96841 and starting SCN of 18173183113 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96840 and starting SCN of 18171843502 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96839 and starting SCN of 18169825523 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96838 and starting SCN of 18169265456 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96837 and starting SCN of 18168812046 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96836 and starting SCN of 18168570885 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96835 and starting SCN of 18168326275 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96834 and starting SCN of 18167945195 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96833 and starting SCN of 18167741652 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96832 and starting SCN of 18167224906 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96831 and starting SCN of 18166336246 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96830 and starting SCN of 18164620049 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96829 and starting SCN of 18162782625 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96828 and starting SCN of 18160870001 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96827 and starting SCN of 18160430892 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96826 and starting SCN of 18157698686 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96825 and starting SCN of 18156894951 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96824 and starting SCN of 18156659772 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96823 and starting SCN of 18156422690 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96822 and starting SCN of 18156136900 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96821 and starting SCN of 18155957994 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96820 and starting SCN of 18155253591 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96819 and starting SCN of 18154335431 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96818 and starting SCN of 18154041168 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96817 and starting SCN of 18152789368 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96816 and starting SCN of 18151668362 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96815 and starting SCN of 18148886406 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96814 and starting SCN of 18147474597 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96813 and starting SCN of 18145673744 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96812 and starting SCN of 18143968186 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96811 and starting SCN of 18143018514 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96810 and starting SCN of 18142353963 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96809 and starting SCN of 18142117207 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96808 and starting SCN of 18141880776 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96807 and starting SCN of 18141628570 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96806 and starting SCN of 18141412405 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96805 and starting SCN of 18140750347 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96804 and starting SCN of 18140060760 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96803 and starting SCN of 18139404568 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96802 and starting SCN of 18138020610 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96801 and starting SCN of 18136411385 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96800 and starting SCN of 18135934898 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96799 and starting SCN of 18135410767 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96798 and starting SCN of 18135027785 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96797 and starting SCN of 18134690422 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96796 and starting SCN of 18134374956 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96795 and starting SCN of 18134002401 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96794 and starting SCN of 18132567736 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96793 and starting SCN of 18131133886 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96792 and starting SCN of 18130836747 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96791 and starting SCN of 18129241373 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96790 and starting SCN of 18129025727 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96789 and starting SCN of 18127594184 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96788 and starting SCN of 18126559910 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96787 and starting SCN of 18126281556 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96786 and starting SCN of 18125651481 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96785 and starting SCN of 18125406978 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96784 and starting SCN of 18125163133 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96783 and starting SCN of 18124774100 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96782 and starting SCN of 18124562513 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96781 and starting SCN of 18124004113 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96780 and starting SCN of 18123197496 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96779 and starting SCN of 18122169173 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96778 and starting SCN of 18119954204 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96777 and starting SCN of 18118059532 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96776 and starting SCN of 18116455564 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96775 and starting SCN of 18114601882 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96774 and starting SCN of 18113417916 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96773 and starting SCN of 18113065612 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96772 and starting SCN of 18112786557 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96771 and starting SCN of 18112526603 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96770 and starting SCN of 18112337871 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96769 and starting SCN of 18111671534 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96768 and starting SCN of 18109547945 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96767 and starting SCN of 18109020995 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96766 and starting SCN of 18107451861 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96765 and starting SCN of 18105161709 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96764 and starting SCN of 18102930631 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96763 and starting SCN of 18101701949 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96762 and starting SCN of 18101027568 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96761 and starting SCN of 18099667566 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96760 and starting SCN of 18099195703 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96759 and starting SCN of 18098962498 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96758 and starting SCN of 18098719550 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96757 and starting SCN of 18098474661 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96756 and starting SCN of 18098270735 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96755 and starting SCN of 18097666172 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96754 and starting SCN of 18096854755 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96753 and starting SCN of 18096493239 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96752 and starting SCN of 18095393153 found to restore
      RMAN-06025: no backup of archived log for thread 1 with sequence 96751 and starting SCN of 18094669641 found to restore
      RMAN-00567: Recovery Manager could not print some error messages

        • 1. Re: RECOVER FAILS WITH RMAN-06025
          Fran

          what incarnation are you using? verify that you are in the corret incarnation and retry:

           

          RMAN> list incarnation

           

          RMAN> reset database to incarnation <X>;

           

          RMAN > catalog start with '<archivelogs_path>;

           

          RMAN> recover database <until SCN 18212580295 >;

           

          *Until SCN or whatever you want to recover.....It's just an example.

          • 2. Re: RECOVER FAILS WITH RMAN-06025
            aparm

            List of Database Incarnations

            DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time

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

            1       1       DB11G   691268520        PARENT  1          01-11-07:20:51:44;

            2       2       DB11G   691268520        CURRENT 893188     19-05-09:12:56:12;

             

            The backup pieces have all been catalogued.

             

            How do I know which SCN I want to restore to? I have a full backup with archive logs, I want to restore all the archive logs, why do I need to specify an SCN? The full backup does that include everything to the point where the backup completed, by way of the archive logs?

            • 3. Re: RECOVER FAILS WITH RMAN-06025
              MahmoudHa

              Hi,

              Your backup of archivelog files appear to be expired please check if the files exists and if yes do a crosscheck to actualize the catalog.

              • 4. Re: RECOVER FAILS WITH RMAN-06025
                Fran

                it isn't necessary choose any SCN, it was an example. If you omit SCN oracle will try to recover until the last archivelog.

                when you execute "crosscheck archivelog all", what happends? did you try the steps i told you with incarnation 1? (recatalog archivelogs after crosscheck archivelog all or change incarnation)

                • 5. Re: RECOVER FAILS WITH RMAN-06025
                  aparm

                  The files do exist, I did a full backup which finished finished about 12pm, I did a restore overnight and the following morning I attempted the recover, so how could they have expired?

                  • 6. Re: RECOVER FAILS WITH RMAN-06025
                    Fran

                    aparm escribió:

                     

                    The files do exist, I did a full backup which finished finished about 12pm, I did a restore overnight and the following morning I attempted the recover, so how could they have expired?

                    ok.... files exists.... but oracle know it?

                    RMAN-06026: some targets not found - aborting restore

                    RMAN-06025: no backup of archived log for thread 1 with sequence

                    why?

                    Status: EXPIRED 


                    guess no....

                     

                    1) Verify your backups exist in 'D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\xxxxxxx"

                    2) change incarnation

                    3) re-catalog backup

                    4) verify that backups are now availble for oracle, not expired

                    5) recover database from backup

                    • 7. Re: RECOVER FAILS WITH RMAN-06025
                      aparm

                      How do I unexpire a backup?

                      • 8. Re: RECOVER FAILS WITH RMAN-06025
                        Fran

                        are they in the correct path? they exists? then use "crosscheck":

                        CROSSCHECK

                         

                        are you doing anything that we are telling you? or just question?

                        • 9. Re: RECOVER FAILS WITH RMAN-06025
                          aparm

                          The thing is I have done all these things, I will do another crosscheck, but when you say correct path, what do you mean? they are where I put them, and catalogued them, the same location as where my datafile backup exists, and it managed to find that?

                          • 10. Re: RECOVER FAILS WITH RMAN-06025
                            Srini Chavali-Oracle

                            Moved to the RMAN forum - pl post future questions in appropriate forum

                            • 11. Re: RECOVER FAILS WITH RMAN-06025
                              Fran

                              i can't see what you are seeing, i'm not there so i don't know what are you doing or not. So please, post each step and its result.

                               

                              Post and follow this steps:

                               

                              1) in ms-dos

                              -cd D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\

                              - dir

                              2) list incarnation;

                              3) reset database to incarnation 1;

                              4) rman> catalog start with 'D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\';

                              *if exist in step 1

                              5) crosscheck archivelog all;

                              *you should see archivelogs as AVAILABLE not as EXPIRED

                              6) run{

                              allocate channel c1 device type disk format 'D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\';

                              recover database;

                              }

                               

                              • 12. Re: RECOVER FAILS WITH RMAN-06025
                                aparm

                                I have a little success with your help, thanks, but I am still coming across errors, can you explain, why is it looking for sequence 96884?

                                 

                                >dir
                                Directory of D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY

                                01/07/2014  13:22    <DIR>          .
                                01/07/2014  13:22    <DIR>          ..
                                28/06/2014  09:06    27,337,264,640 FULL_DB11G_851412025_4396_1.BKP
                                28/06/2014  11:58     2,035,111,936 FULL_DB11G_851428281_4398_1.BKP
                                               2 File(s) 29,372,376,576 bytes
                                               2 Dir(s)  77,778,026,496 bytes free

                                 

                                RMAN>list incarnation;
                                using target database control file instead of recovery catalog

                                List of Database Incarnations
                                DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
                                ------- ------- -------- ---------------- --- ---------- ----------
                                1       1       DB11G   691268520        PARENT  1          01-NOV-07
                                2       2       DB11G   691268520        CURRENT 893188     19-MAY-09

                                 

                                RMAN>crosscheck archivelog all;
                                allocated channel: ORA_DISK_1
                                channel ORA_DISK_1: SID=800 device type=DISK
                                specification does not match any archived log in the recovery catalog

                                RMAN>crosscheck backup
                                using channel ORA_DISK_1
                                crosschecked backup piece: found to be 'AVAILABLE'
                                backup piece handle=D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\FULL_DB11G_851412025_4396_1.BKP RECID=4312 STAMP=851412025
                                crosschecked backup piece: found to be 'AVAILABLE'
                                backup piece handle=D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\FULL_DB11G_851428281_4398_1.BKP RECID=4314 STAMP=851428282
                                Crosschecked 2 objects

                                 

                                RMAN>list backup
                                using target database control file instead of recovery catalog

                                List of Backup Sets
                                ===================


                                BS Key  Size       Device Type Elapsed Time Completion Time
                                ------- ---------- ----------- ------------ ---------------
                                4312    25.46G     DISK        01:46:17     28-JUN-14     
                                        BP Key: 4312   Status: AVAILABLE  Compressed: YES  Tag: TAG20140628T072024
                                        Piece Name: D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\FULL_DB11G_851412025_4396_1.BKP

                                  List of Archived Logs in backup set 4312
                                  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
                                  ---- ------- ---------- --------- ---------- ---------
                                  1    96860   18193676969 26-JUN-14 18195132908 26-JUN-14
                                  1    96861   18195132908 26-JUN-14 18195653501 26-JUN-14
                                  1    96862   18195653501 26-JUN-14 18196547459 27-JUN-14
                                  1    96863   18196547459 27-JUN-14 18196978257 27-JUN-14
                                  1    96864   18196978257 27-JUN-14 18197190770 27-JUN-14
                                  1    96865   18197190770 27-JUN-14 18197448243 27-JUN-14
                                  1    96866   18197448243 27-JUN-14 18197683988 27-JUN-14
                                  1    96867   18197683988 27-JUN-14 18198295392 27-JUN-14
                                  1    96868   18198295392 27-JUN-14 18198881348 27-JUN-14
                                  1    96869   18198881348 27-JUN-14 18200450596 27-JUN-14
                                  1    96870   18200450596 27-JUN-14 18202037378 27-JUN-14
                                  1    96871   18202037378 27-JUN-14 18205278051 27-JUN-14
                                  1    96872   18205278051 27-JUN-14 18207445496 28-JUN-14
                                  1    96873   18207445496 28-JUN-14 18207958577 28-JUN-14
                                  1    96874   18207958577 28-JUN-14 18208152761 28-JUN-14
                                  1    96875   18208152761 28-JUN-14 18208590017 28-JUN-14
                                  1    96876   18208590017 28-JUN-14 18208815314 28-JUN-14
                                  1    96877   18208815314 28-JUN-14 18209053741 28-JUN-14
                                  1    96878   18209053741 28-JUN-14 18209728627 28-JUN-14
                                  1    96879   18209728627 28-JUN-14 18210325373 28-JUN-14
                                  1    96880   18210325373 28-JUN-14 18210399038 28-JUN-14

                                BS Key  Size       Device Type Elapsed Time Completion Time
                                ------- ---------- ----------- ------------ ---------------
                                4314    1.90G      DISK        00:07:08     28-JUN-14     
                                        BP Key: 4314   Status: AVAILABLE  Compressed: YES  Tag: TAG20140628T115121
                                        Piece Name: D:\MANUAL_BACKUPS\DB11G\ARCHIVAL_BACKUP\WEEKLY\FULL_DB11G_851428281_4398_1.BKP

                                  List of Archived Logs in backup set 4314
                                  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
                                  ---- ------- ---------- --------- ---------- ---------
                                  1    96881   18210399038 28-JUN-14 18211042579 28-JUN-14
                                  1    96882   18211042579 28-JUN-14 18212580295 28-JUN-14
                                  1    96883   18212580295 28-JUN-14 18212824896 28-JUN-14


                                RMAN>recover database;
                                Starting recover at 01-JUL-14
                                using channel ORA_DISK_1

                                starting media recovery

                                unable to find archived log
                                archived log thread=1 sequence=96884
                                RMAN-00571: ===========================================================
                                RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
                                RMAN-00571: ===========================================================
                                RMAN-03002: failure of recover command at 07/01/2014 17:30:25
                                RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 96884 and starting SCN of 18212824896

                                • 13. Re: RECOVER FAILS WITH RMAN-06025
                                  Levi Pereira

                                  RMAN>recover database;
                                  Starting recover at 01-JUL-14
                                  using channel ORA_DISK_1

                                  starting media recovery

                                  unable to find archived log

                                   

                                  Did you know what do this command?

                                   

                                  It will try restore database until 'SYSDATE' (i.e current date/time).

                                  So you will need all archivelogs from 28-06-2014 11:51:21 (I got this on TAG TAG20140628T115121) until SYSDATE.

                                   

                                  If you don't need to restore database until current date/time.


                                  Specify a Timestamp to Recover, until time where archivelogs exists.

                                  e.g

                                  RMAN> Run {

                                  set until time "TO_DATE('28-07-2014 11:50:00', 'DD-MM-YYYY HH24:MI:SS')";

                                  recover database;

                                  }

                                   

                                  Tip: Before start RMAN set NLS_DATE_FORMAT variable on "Command Prompt"

                                  SET NLS_DATE_FORMAT=DD-MM-YYYY HH24:MI:SS

                                  • 14. Re: RECOVER FAILS WITH RMAN-06025
                                    aparm

                                    Ok I have used run set time as above, but I still get the following error

                                     

                                    connected to target database: DB11G (DBID=691268520, not open)

                                    RMAN> 2> 3> 4> 5> 6> 7>
                                    executing command: SET until clause
                                    using target database control file instead of recovery catalog

                                    Starting recover at 01-07-2014 21:05:54
                                    allocated channel: ORA_DISK_1
                                    channel ORA_DISK_1: SID=785 device type=DISK

                                    starting media recovery

                                    unable to find archived log
                                    archived log thread=1 sequence=96884
                                    RMAN-00571: ===========================================================
                                    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
                                    RMAN-00571: ===========================================================
                                    RMAN-03002: failure of recover command at 07/01/2014 21:06:23
                                    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 96884 and starting SCN of 18212824896

                                     

                                    ... and I still get this if I use recover database until scn 18212824896, I don't understand it?

                                    1 2 Previous Next