14 Replies Latest reply on May 12, 2014 4:50 PM by sweetritz

    During DB cloning it got restored but not recovered. Why?

    sweetritz

      Hi DBA gods,

      Today I was doing a DB cloning (Oracle 10.2.0.5) from the tape backup of 1TB using RMAN scripts. After I saw the logs the below error was found

       

      Oracle Error:

      ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

      ORA-01194: file 1 needs more recovery to be consistent

      ORA-01110: data file 1: '+DAT/DBclone/datafile/system.570.89078373624'

       

      released channel: ch01

      released channel: ch02

       

      RMAN-00571: ===========================================================

      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

      RMAN-00571: ===========================================================

      RMAN-03002: failure of Duplicate Db command at 05/11/2014 13:16:29

      RMAN-03015: error occurred in stored script Memory Script

      RMAN-06053: unable to perform media recovery because of missing log

      RMAN-06025: no backup of log thread 2 seq 22338 lowscn 12017428115838 found to restore

      RMAN-06025: no backup of log thread 1 seq 22554 lowscn 12017428115841 found to restore

       

      According to the logs the DB restored but could not be recovered due to the above error. Any solution?

        • 1. Re: During DB cloning it got restored but not recovered. Why?
          sb92075

          Provide the required REDO logfile(s)

          1 person found this helpful
          • 2. Re: During DB cloning it got restored but not recovered. Why?
            Fran

            sweetritz escribió:

             

            Hi DBA gods,

            Today I was doing a DB cloning (Oracle 10.2.0.5) from the tape backup of 1TB using RMAN scripts. After I saw the logs the below error was found

             

            Oracle Error:

            ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

            ORA-01194: file 1 needs more recovery to be consistent

            ORA-01110: data file 1: '+DAT/DBclone/datafile/system.570.89078373624'

             

            released channel: ch01

            released channel: ch02

             

            RMAN-00571: ===========================================================

            RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

            RMAN-00571: ===========================================================

            RMAN-03002: failure of Duplicate Db command at 05/11/2014 13:16:29

            RMAN-03015: error occurred in stored script Memory Script

            RMAN-06053: unable to perform media recovery because of missing log

            RMAN-06025: no backup of log thread 2 seq 22338 lowscn 12017428115838 found to restore

            RMAN-06025: no backup of log thread 1 seq 22554 lowscn 12017428115841 found to restore

             

            According to the logs the DB restored but could not be recovered due to the above error. Any solution?

             

            If you don't have backup oracle can't found it. you should check if you have any backup of this logs, and if this backup has been cataloged.

             

            what scripts are you using?

            what incarnation are you using?

            could you see the missing archivelogs when you execute "list backup of archivelog all;"?

            1 person found this helpful
            • 3. Re: During DB cloning it got restored but not recovered. Why?
              sweetritz

              @sb92075 thanks a bunch for replying. But as a newbie I have no idea on how to proceed from here . How to provide req. REDO logfine and where? Any command would be helpful

              • 4. Re: During DB cloning it got restored but not recovered. Why?
                gandolf999

                You need to recover the database with archive log files that are newer than the control file that you used to do the backup.

                Can you find the archive logs that the database is looking for? if not than you will likely need to use an older controlfile for the clone.

                1 person found this helpful
                • 5. Re: During DB cloning it got restored but not recovered. Why?
                  sweetritz

                  @Fran when i give "list backup of archivelog all" it give the below output:

                  using target database control file instead of recovery catalog

                  • 6. Re: During DB cloning it got restored but not recovered. Why?
                    Fran

                    sweetritz escribió:

                     

                    @Fran when i give "list backup of archivelog all" it give the below output:

                    using target database control file instead of recovery catalog

                     

                    you should give us more information if you want ot be helped, not only the first line you got.

                    1 person found this helpful
                    • 7. Re: During DB cloning it got restored but not recovered. Why?
                      spiderwoman

                      POST RESULTS OF FOLLOWING:

                       

                      set pagesize 20000

                           set linesize 180

                           set pause off

                           set serveroutput on

                           set feedback on

                           set echo on

                           set numformat 999999999999999

                       

                           Spool recovery_info.txt

                           select substr(name, 1, 50), status from v$datafile;

                           select substr(name,1,40), recover, fuzzy, checkpoint_change# from v$datafile_header;

                           select GROUP#,substr(member,1,60) from v$logfile;

                           select * from v$recover_file;

                           select distinct status from v$backup;

                           select hxfil FILENUMBER, fhsta STATUS, fhscn SCN, FHAFS ABSSCN , fhrba_Seq SEQUENCE from x$kcvfh;

                           select distinct (fuzzy) from v$datafile_header;

                           spool off

                           exit;

                      1 person found this helpful
                      • 8. Re: During DB cloning it got restored but not recovered. Why?
                        spiderwoman

                        Have you tried "RESTORE ARCHIVELOG ALL VALIDATE" already?

                        1 person found this helpful
                        • 9. Re: During DB cloning it got restored but not recovered. Why?
                          Aman....

                          spiderwoman wrote:

                           

                          Have you tried "RESTORE ARCHIVELOG ALL VALIDATE" already?

                          Why to use that ?

                           

                          Aman....

                          1 person found this helpful
                          • 10. Re: During DB cloning it got restored but not recovered. Why?
                            Aman....

                            sweetritz wrote:

                             

                            Hi DBA gods,

                            Today I was doing a DB cloning (Oracle 10.2.0.5) from the tape backup of 1TB using RMAN scripts. After I saw the logs the below error was found

                             

                            Oracle Error:

                            ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

                            ORA-01194: file 1 needs more recovery to be consistent

                            ORA-01110: data file 1: '+DAT/DBclone/datafile/system.570.89078373624'

                             

                            released channel: ch01

                            released channel: ch02

                             

                            RMAN-00571: ===========================================================

                            RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

                            RMAN-00571: ===========================================================

                            RMAN-03002: failure of Duplicate Db command at 05/11/2014 13:16:29

                            RMAN-03015: error occurred in stored script Memory Script

                            RMAN-06053: unable to perform media recovery because of missing log

                            RMAN-06025: no backup of log thread 2 seq 22338 lowscn 12017428115838 found to restore

                            RMAN-06025: no backup of log thread 1 seq 22554 lowscn 12017428115841 found to restore

                             

                            According to the logs the DB restored but could not be recovered due to the above error. Any solution?

                            As others have already pointed out, you are most likely not having the mentioned archive log. Did you try to see that whether that log exists ?

                             

                            Aman....

                            1 person found this helpful
                            • 11. Re: During DB cloning it got restored but not recovered. Why?
                              Girish Sharma

                              Database restoration has been completed, but when RMAN is going to restore archive log it could not found it as backed up. 

                               

                              Below select statement will tell you that whether required sequence archive log has been backed up or not :

                              select status,sequence#,resetlogs_change#,deleted from v$archived_log where sequence#=22338;

                               

                              If you do not find anything then only way is :

                              RMAN> DUPLICATE TARGET DATABASE TO "clone" NOFILENAMECHECK;

                               

                              Regards

                              Girish Sharma

                              1 person found this helpful
                              • 12. Re: During DB cloning it got restored but not recovered. Why?
                                gandolf999

                                Since you are cloning a database, you should be able to look at the production server, find the

                                archive logs that are needed to finish the clone, then copy them over and apply them. If you do

                                archive log only backups, you may already have a backup of the archive logs that you need.

                                Since you are using the control file for the catalog, you will need to catalog any backups that

                                you want to apply then use RMAN to restore and apply the archive logs.

                                 

                                So either find the archive logs you need on disk, or find the backup that has the archive logs

                                that you need recover the database. Either way you will want to look at the backup script and

                                make sure that you are not backing up the control file after you finish backing up the database,

                                or don't use the newest control file that is getting backed up.

                                1 person found this helpful
                                • 13. Re: During DB cloning it got restored but not recovered. Why?
                                  Hemant K Chitale

                                  Most likely, those Logs are the first in each thread (this is a 2node RAC database) after the end of the backup that was restore.  So Oracle DOES need those Logs.

                                   

                                   

                                  Hemant K Chitale


                                  1 person found this helpful
                                  • 14. Re: During DB cloning it got restored but not recovered. Why?
                                    sweetritz

                                    Hey guys one good news ,

                                    I found the solution in the Doc ID 360962.1 from Oracle. I did the below steps from the doc and was able to successfully clone the DB.

                                    First take the SCN no. from the previous failed clone log of the DB.

                                    Now you need to set new name for datafile and that can be taken from previous log.

                                    run

                                    {

                                    set until scn 12017428115841;

                                    set newname for datafile  1 to "+dat";

                                    set newname for datafile  2 to "+dat";

                                    set newname for datafile  3 to "+dat";

                                    set newname for datafile  4 to "+dat";

                                    set newname for datafile  5 to "+dat";

                                    set newname for datafile  6 to "+dat";

                                    set newname for datafile  7 to "+dat";

                                    set newname for datafile  8 to "+dat";

                                    set newname for datafile  9 to "+dat";

                                    set newname for datafile  10 to "+dat";

                                    set newname for datafile  11 to "+dat";

                                    set newname for datafile  12 to "+dat";

                                    set newname for datafile  13 to "+dat";

                                    set newname for datafile  14 to "+dat";

                                    set newname for datafile  15 to "+dat";

                                    set newname for datafile  16 to "+dat";

                                    set newname for datafile  17 to "+dat";

                                    set newname for datafile  18 to "+dat";

                                    set newname for datafile  19 to "+dat";

                                    set newname for datafile  20 to "+dat";

                                    set newname for datafile  21 to "+dat";

                                    set newname for datafile  22 to "+dat";

                                    set newname for datafile  23 to "+dat";

                                    set newname for datafile  24 to "+dat";

                                    set newname for datafile  25 to "+dat";

                                    allocate auxiliary channel ch01 device type SBT PARMS 'BLKSIZE=1048576' MAXOPENFILES 1;

                                    allocate auxiliary channel ch02 device type SBT PARMS 'BLKSIZE=1048576' MAXOPENFILES 1;

                                    SEND 'NB_ORA_CLIENT=zeusrv-priv,NB_ORA_POLICY=zeusbkpDB,NB_ORA_SERV=zeusappsvr-priv,NB_ORA_SCHED=ZEUS';

                                    recover clone database ;

                                    }

                                    RMAN> alter clone database open resetlogs;

                                    zeus> nid target=sys/*****

                                    DBNEWID - Completed succesfully.

                                    zeus> sqlplus " /as sysdba"

                                     

                                    SQL*Plus: Release 10.2.0.5.0 - Production on Mon May 12 21:05:54 2014

                                     

                                    Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

                                     

                                    Connected to an idle instance.

                                     

                                    SQL> startup mount

                                    SQL> alter database open resetlogs;

                                    SQL> select status from v$instance;

                                     

                                    STATUS

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

                                    OPEN


                                    But even after my cloning got completed from the above steps I am still in confusion that what did above steps actually did that DB got cloned and opened?

                                    Any detailed explanation for a newbie like me? It would be great as I will learn new things in Oracle.


                                    Regards,

                                    sweetritz (Ritu)