1 2 Previous Next 19 Replies Latest reply: Oct 3, 2013 4:58 AM by Clamarion Go to original post RSS
      • 15. Re: Restoring Cumulative Incremental level 0 and Cumulative Incremental level 1 backups on a new Host (Archivelogs not available)
        Clamarion

        @Hemant K Chitale


        I have a good news!!!!!! I was able to raestore and recover my database with almost no data loss. I ws helped by a DBA called J.P. Boileau. I didn't use the Oracle Support solution because it was too complicated to deploy. This is what I did:


        1- I first got the last SCN of my cumulative incremental level 1 backup through a list backup command.

        2-Then I used this SCN to do a set until SCN ........

        3-Finally I did a restore database; recover database; and alter database open resetlogs.


        This is the detailed output of a test simulation of this solution:


        [oracle@cumulative ~]$ . oraenv

        ORACLE_SID = [oracle] ? orcl

        ORACLE_HOME = [/home/oracle] ? /u01/app/oracle/product/11.2.0/dbhome_1

        The Oracle base has been set to /u01/app/oracle

        [oracle@cumulative ~]$ rman target /

         

         

        Recovery Manager: Release 11.2.0.3.0 - Production on Thu Oct 3 09:12:30 2013

         

         

        Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

         

         

        connected to target database (not started)

         

         

        RMAN> startup mount;

         

         

        Oracle instance started

        database mounted

         

         

        Total System Global Area     835104768 bytes

         

         

        Fixed Size                     2232960 bytes

        Variable Size                574623104 bytes

        Database Buffers             251658240 bytes

        Redo Buffers                   6590464 bytes

         

         

        RMAN> catalog start with '/u01/backup';

         

         

        Starting implicit crosscheck backup at 03-OCT-13

        using target database control file instead of recovery catalog

        allocated channel: ORA_DISK_1

        channel ORA_DISK_1: SID=133 device type=DISK

        Crosschecked 7 objects

        Finished implicit crosscheck backup at 03-OCT-13

         

         

        Starting implicit crosscheck copy at 03-OCT-13

        using channel ORA_DISK_1

        Finished implicit crosscheck copy at 03-OCT-13

         

         

        searching for all files in the recovery area

        cataloging files...

        no files cataloged

         

         

        searching for all files that match the pattern /u01/backup

         

         

        List of Files Unknown to the Database

        =====================================

        File Name: /u01/backup/autobackup/o1_mf_s_827753589_94qxm5o3_.bkp

        File Name: /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

        File Name: /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

         

         

        Do you really want to catalog the above files (enter YES or NO)? yes

        cataloging files...

        cataloging done

         

         

        List of Cataloged Files

        =======================

        File Name: /u01/backup/autobackup/o1_mf_s_827753589_94qxm5o3_.bkp

        File Name: /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

        File Name: /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

         

         

        RMAN> crosscheck backupset;

         

         

        using channel ORA_DISK_1

        crosschecked backup piece: found to be 'EXPIRED'

        backup piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd0_TAG20130930T114816_94loqk4w_.bkp RECID=1 STAMP=827495297

        crosschecked backup piece: found to be 'EXPIRED'

        backup piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495353_94losbfm_.bkp RECID=2 STAMP=827495354

        crosschecked backup piece: found to be 'EXPIRED'

        backup piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd1_TAG20130930T115510_94lp4h7v_.bkp RECID=3 STAMP=827495711

        crosschecked backup piece: found to be 'EXPIRED'

        backup piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495755_94lp5w1f_.bkp RECID=4 STAMP=827495756

        crosschecked backup piece: found to be 'EXPIRED'

        backup piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_10_02/o1_mf_s_827749047_94qs58bo_.bkp RECID=6 STAMP=827749048

        crosschecked backup piece: found to be 'EXPIRED'

        backup piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp RECID=5 STAMP=827748980

        crosschecked backup piece: found to be 'AVAILABLE'

        backup piece handle=/u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp RECID=8 STAMP=827831641

        crosschecked backup piece: found to be 'EXPIRED'

        backup piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp RECID=7 STAMP=827753553

        crosschecked backup piece: found to be 'AVAILABLE'

        backup piece handle=/u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp RECID=9 STAMP=827831641

        Crosschecked 9 objects

         

         

         

         

        RMAN> list backup;

         

         

         

         

        List of Backup Sets

        ===================

         

         

         

         

        BS Key  Type LV Size       Device Type Elapsed Time Completion Time

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

        1       Incr 0  1.06G      DISK        00:00:51     30-SEP-13     

                BP Key: 1   Status: EXPIRED  Compressed: NO  Tag: TAG20130930T114816

                Piece Name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd0_TAG20130930T114816_94loqk4w_.bkp

          List of Datafiles in backup set 1

          File LV Type Ckp SCN    Ckp Time  Name

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

          1    0  Incr 1123837    30-SEP-13 /u01/app/oracle/oradata/orcl/system01.dbf

          2    0  Incr 1123837    30-SEP-13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

          3    0  Incr 1123837    30-SEP-13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

          4    0  Incr 1123837    30-SEP-13 /u01/app/oracle/oradata/orcl/users01.dbf

          5    0  Incr 1123837    30-SEP-13 /u01/app/oracle/oradata/orcl/example01.dbf

         

         

        BS Key  Type LV Size       Device Type Elapsed Time Completion Time

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

        2       Full    9.36M      DISK        00:00:01     30-SEP-13     

                BP Key: 2   Status: EXPIRED  Compressed: NO  Tag: TAG20130930T114913

                Piece Name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495353_94losbfm_.bkp

          SPFILE Included: Modification time: 30-SEP-13

          SPFILE db_unique_name: ORCL

          Control File Included: Ckp SCN: 1123870      Ckp time: 30-SEP-13

         

         

        BS Key  Type LV Size       Device Type Elapsed Time Completion Time

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

        3       Incr 1  4.54M      DISK        00:00:39     30-SEP-13     

                BP Key: 3   Status: EXPIRED  Compressed: NO  Tag: TAG20130930T115510

                Piece Name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd1_TAG20130930T115510_94lp4h7v_.bkp

          List of Datafiles in backup set 3

          File LV Type Ckp SCN    Ckp Time  Name

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

          1    1  Incr 1124362    30-SEP-13 /u01/app/oracle/oradata/orcl/system01.dbf

          2    1  Incr 1124362    30-SEP-13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

          3    1  Incr 1124362    30-SEP-13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

          4    1  Incr 1124362    30-SEP-13 /u01/app/oracle/oradata/orcl/users01.dbf

          5    1  Incr 1124362    30-SEP-13 /u01/app/oracle/oradata/orcl/example01.dbf

         

         

        BS Key  Type LV Size       Device Type Elapsed Time Completion Time

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

        4       Full    9.36M      DISK        00:00:01     30-SEP-13     

                BP Key: 4   Status: EXPIRED  Compressed: NO  Tag: TAG20130930T115555

                Piece Name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495755_94lp5w1f_.bkp

          SPFILE Included: Modification time: 30-SEP-13

          SPFILE db_unique_name: ORCL

          Control File Included: Ckp SCN: 1124391      Ckp time: 30-SEP-13

         

         

        BS Key  Type LV Size       Device Type Elapsed Time Completion Time

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

        6       Full    9.36M      DISK        00:00:01     02-OCT-13     

                BP Key: 6   Status: EXPIRED  Compressed: NO  Tag: TAG20131002T101727

                Piece Name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_10_02/o1_mf_s_827749047_94qs58bo_.bkp

          SPFILE Included: Modification time: 02-OCT-13

          SPFILE db_unique_name: ORCL

          Control File Included: Ckp SCN: 1177698      Ckp time: 02-OCT-13

         

         

        BS Key  Type LV Size

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

        8       Incr 0  1.06G

          List of Datafiles in backup set 8

          File LV Type Ckp SCN    Ckp Time  Name

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

          1    0  Incr 1177574    02-OCT-13 /u01/app/oracle/oradata/orcl/system01.dbf

          2    0  Incr 1177574    02-OCT-13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

          3    0  Incr 1177574    02-OCT-13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

          4    0  Incr 1177574    02-OCT-13 /u01/app/oracle/oradata/orcl/users01.dbf

          5    0  Incr 1177574    02-OCT-13 /u01/app/oracle/oradata/orcl/example01.dbf

         

         

          Backup Set Copy #1 of backup set 8

          Device Type Elapsed Time Completion Time Compressed Tag

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

          DISK        00:00:00     02-OCT-13       NO         TAG20131002T101620

         

         

            List of Backup Pieces for backup set 8 Copy #1

            BP Key  Pc# Status      Piece Name

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

            5       1   EXPIRED     /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

         

         

          Backup Set Copy #2 of backup set 8

          Device Type Elapsed Time Completion Time Compressed Tag

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

          DISK        00:00:00     03-OCT-13       NO         TAG20131002T101620

         

         

            List of Backup Pieces for backup set 8 Copy #2

            BP Key  Pc# Status      Piece Name

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

            8       1   AVAILABLE   /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

         

         

        BS Key  Type LV Size

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

        9       Incr 1  9.20M

          List of Datafiles in backup set 9

          File LV Type Ckp SCN    Ckp Time  Name

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

          1    1  Incr 1182056    02-OCT-13 /u01/app/oracle/oradata/orcl/system01.dbf

          2    1  Incr 1182056    02-OCT-13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

          3    1  Incr 1182056    02-OCT-13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

          4    1  Incr 1182056    02-OCT-13 /u01/app/oracle/oradata/orcl/users01.dbf

          5    1  Incr 1182056    02-OCT-13 /u01/app/oracle/oradata/orcl/example01.dbf

         

         

          Backup Set Copy #1 of backup set 9

          Device Type Elapsed Time Completion Time Compressed Tag

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

          DISK        00:00:00     02-OCT-13       NO         TAG20131002T113233

         

         

            List of Backup Pieces for backup set 9 Copy #1

            BP Key  Pc# Status      Piece Name

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

            7       1   EXPIRED     /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

         

         

          Backup Set Copy #2 of backup set 9

          Device Type Elapsed Time Completion Time Compressed Tag

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

          DISK        00:00:00     03-OCT-13       NO         TAG20131002T113233

         

         

            List of Backup Pieces for backup set 9 Copy #2

            BP Key  Pc# Status      Piece Name

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

            9       1   AVAILABLE   /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

         

         

        RMAN> run {

        2> set until scn 1182056;

        3> restore database;

        4> recover database;

        5> }

         

         

        executing command: SET until clause

         

         

        Starting restore at 03-OCT-13

        using channel ORA_DISK_1

         

         

        channel ORA_DISK_1: starting datafile backup set restore

        channel ORA_DISK_1: specifying datafile(s) to restore from backup set

        channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf

        channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf

        channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf

        channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf

        channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf

        channel ORA_DISK_1: reading from backup piece /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

        channel ORA_DISK_1: piece handle=/u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp tag=TAG20131002T101620

        channel ORA_DISK_1: restored backup piece 1

        channel ORA_DISK_1: restore complete, elapsed time: 00:00:47

        Finished restore at 03-OCT-13

         

         

        Starting recover at 03-OCT-13

        using channel ORA_DISK_1

        channel ORA_DISK_1: starting incremental datafile backup set restore

        channel ORA_DISK_1: specifying datafile(s) to restore from backup set

        destination for restore of datafile 00001: /u01/app/oracle/oradata/orcl/system01.dbf

        destination for restore of datafile 00002: /u01/app/oracle/oradata/orcl/sysaux01.dbf

        destination for restore of datafile 00003: /u01/app/oracle/oradata/orcl/undotbs01.dbf

        destination for restore of datafile 00004: /u01/app/oracle/oradata/orcl/users01.dbf

        destination for restore of datafile 00005: /u01/app/oracle/oradata/orcl/example01.dbf

        channel ORA_DISK_1: reading from backup piece /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

        channel ORA_DISK_1: piece handle=/u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp tag=TAG20131002T113233

        channel ORA_DISK_1: restored backup piece 1

        channel ORA_DISK_1: restore complete, elapsed time: 00:00:07

         

         

        starting media recovery

        media recovery complete, elapsed time: 00:00:01

         

         

        Finished recover at 03-OCT-13

         

         

        RMAN> alter database open resetlogs;

         

         

        database opened

         

         

        RMAN>

         

        Thank you again for all your help and patience.

        Regards

        Clamarion.

        • 16. Re: Restoring Cumulative Incremental level 0 and Cumulative Incremental level 1 backups on a new Host (Archivelogs not available)
          Hemant K Chitale

          I guess that this is a simulation where you are restoring a backup of 02-Oct ?   How did you create this backup ?

           

          Your actual production issue is a backup done on or before 30-Sept ?

           

          What was the Oracle solution ?

           

           

          Hemant K Chitale


          • 17. Re: Restoring Cumulative Incremental level 0 and Cumulative Incremental level 1 backups on a new Host (Archivelogs not available)
            Clamarion

            To do the simulation, I did exactly how I generally do to backup my production database:

            rman>backup cumulative incremental level 0 database;

            Rman>backup cumulative incremental level 1 database;  (after a few hours and some changes)

             

            In my prod environment, the last cumulative incremental level 0 backup is from 26/08/2013 and the last cumulative incremental level 1 backup is from 26/09/2013 at 14:00:00 pm.

             

            The Oracle support solution is quite long and complex but I will post it for you here:

             

            ********************************************************************************************************************************************************************************************************************************************************************************************

             

            Hello Erick,

             

            In this case our only option to open this database will be using the following procedure :

             

            Warning
            ~~~~~~~
            The following instructions should only be used under the explicit direction
            of Oracle Support. These steps should only be used when all other conventional
            means of recovering the database have failed. Please note that there is no
            guarantee that this method will succeed.

             

            IF THE STEPS BELOW DO ALLOW YOU TO OPEN YOUR DATABASE THEN IT IS ESSENTIAL THAT
            THE DATABASE BE REBUILT AS IT IS NO LONGER SUPPORTED. FAILURE TO DO SO MAY LEAD
            TO DATA DICTIONARY INCONSISTENCIES, INTERNAL ERRORS AND CORRUPTIONS.

             

            ** Note: The steps here apply to Oracle 9i or higher and only and when Automatic
            Undo Management is being used. **

             

            Steps to attempt to force the database open:
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

             

            1) Backup the database while the database is closed.

             

            THE INSTRUCTIONS HERE ARE DESTRUCTIVE. YOU ARE STRONGLY ADVISED TO BACKUP THE
            DATABASE BEFORE PROCEEDING. IF YOU DO NOT DO THIS YOU MAY LOSE THE CHANCE TO
            TRY OTHER OPTIONS.

             

            2) Disable this database from EM if running. We also need to disable RAC to avoid Auto restart.

             

            3) If your datafiles are from different points in time, it is best to try to
            use system tablespace datafiles at a similar timestamp to the OLDEST files
            you have online in the database. This reduces the chance that you will get
            problems during the bootstrap phase of opening the database.

             

            4) Edit your init.ora file to change undo_management and add two parameters.

             

            * Change UNDO_MANAGEMENT=AUTO to

             

            UNDO_MANAGEMENT=MANUAL

             

            * Remove or comment out UNDO_TABLESPACE and UNDO_RETENTION.

             

            * Add

             

            CLUSTER_DATABASE=FALSE
            JOB_QUEUE_PROCESSES=0
            _ALLOW_RESETLOGS_CORRUPTION = TRUE
            _CORRUPTED_ROLLBACK_SEGMENTS =(comma separated list of Automatic Undo segments)

             

            Example:

             

            _CORRUPTED_ROLLBACK_SEGMENTS = (_SYSSMU1$, _SYSSMU2$, _SYSSMU3$, _SYSSMU4$,
            _SYSSMU5$, _SYSSMU6$, _SYSSMU7$, _SYSSMU8$, _SYSSMU9$, _SYSSMU10$)

             

            Note, sometimes the alert log will tell you what Automatic Undo segments are in
            use. Search the alert log for SYSS. If the alert log does not contain that
            information then use _SYSSMU1$ through _SYSSMU10$ as shown in the example above.

             

            From 11g onwards the names of the UNDO-segments are a little different and have an extension:

             

            _SYSSMU< nn>_< mmmmm>$) ( example _SYSSMU10_1221075320$)

             

            Be sure to include the additional numbers in the UNDO-segment name as well.

             

            In UNIX you can issue this command on SYSTEM datafile(s) to get the undo segment names:

             

            $ strings system01.dbf | grep _SYSSMU | cut -d $ -f 1 | sort -u

             

            If files are in ASM, you can use RMAN command to copy them to filesystem before using strings command, e.g. :

             

            RMAN> backup as copy datafile 1 format '/tmp/system01.dbf' ;

             

            You should run above command on all SYSTEM datafiles as undo segments may reside in more than one SYSTEM datafile.
            To list the name of SYSTEM datafiles, run below command in at least MOUNT mode:

             

            SQL> select file#, f.name from v$datafile f, v$tablespace t where f.ts#=t.ts# and t.name='SYSTEM' order by file# ;

             

            From the output of the strings command above, add a $ to end of each _SYSSMU undo segment name.

             

            * If you only have a spfile available, you can from the closed, nomount or the
            mount stage create an init.ora file as follows:

             

            SQL> CREATE PFILE FROM SPFILE;

             

            Do NOT edit the SPFILE.

             

            5) Invoke SQL*Plus, startup mount, check that correct init.ora was used and
            all datafiles are in the status of online or system.

             

            $ sqlplus "/as sysdba"

             

            SQL> startup mount pfile = (full path / file name to init.ora)
            Confirm that the hidden parameters from step 3 were used:

             

            SQL> show parameters corrupt

             

            You should see both hidden parameters listed. If not, the wrong init.ora
            may have been modified. Do not continue until "show parameters corrupt" shows
            both hidden parameters.

             

            SQL> show parameters undo

             

            You should see undo management set to manual. If not, the wrong init.ora
            may have been modified. Do not continue until "show parameters undo" shows
            undo management as manual.

             

            Check that all files you want to open with are listed as ONLINE or as SYSTEM.

             

            SQL> select name, file#, status from v$datafile where status not in
            ('SYSTEM', 'ONLINE');

             

            If any rows are returned from the query above, bring the file(s) online with:

             

            SQL> ALTER DATABASE DATAFILE file# ONLINE;

             

            and repeat until there are no files in an OFFLINE status. If any file remains or
            changes into "recover" status after you try to online the file proceed to step 5.

             

            6) Perform a fake incomplete recovery then open the database with resetlogs.

             

            SQL> recover database using backup controlfile until cancel;

             

            WHEN PROMPTED FOR AN ARCHIVELOG FILE TYPE cancel THEN PRESS ENTER.

             

            SQL> ALTER DATABASE OPEN RESETLOGS;

             

            7) If the database opens try selecting from a table. For example:

             

            SQL> SELECT SYSDATE FROM DUAL;

             

            If you get a row back the database is open and "functional". If you wish, you
            may try to select from a other tables to make sure the database is functional
            enough for the required export.

             

            With the database open and functional you should attempt to export the database
            IMMEDIATELY. Since database is unstable, don't try another shutdown/startup unless needed.
            Once you have an export the database MUST be recreated from scratch.
            This means dropping and deleting ALL datafiles and creating a new database from
            scratch.

             

            A database which has been opened in this way but not rebuilt will not be
            supported by Oracle. Any delay in exporting the contents or any attempt to
            use the system may cause irreparable damage.

             

            NOTE: BE SURE TO REVERSE / REMOVE THE INIT.ORA PARAMETERS ADDED IN STEP 3
            OTHERWISE YOU MAY ACCIDENTALLY CORRUPT ANY NEW DATABASE CREATED USING THE SAME
            INIT.ORA FILE.

             

            8) If the instance crashed in the open phase of step 5, check for trace files
            in the background dump destination. If you find a trace file, check to see if
            the trace file has an ORA-00600 [2662] or ORA-00600 [4000] error in it.
            Either of these errors may also be seen in the alert.log file.

             

            If you see the ORA-00600 [2662] or ORA-00600 [4000] error, provide Oracle Support
            Services the full error message. Oracle Support Services will provide steps to advance
            the SCN using a hidden parameter.

             

            regards
            Shahar
            OCS

             

             

             

             

            Oracle Support- Tuesday[ODM Question]

             

             

             

             

            Problem Summary
            ---------------------------------------------------
            How to recover a hot backup without archivelogs and online redologs?

             

            Problem Description
            ---------------------------------------------------
            Hi to My Oracle Support Team.

             

            I have a disaster to manage. There was a fire incident in our server room and with physically lost our server containing the Oracle databases. Luckily, I have been doing Cumulative Incremental Level 0 backups Monthly, and Cumulative Incremental Level 1 backups daily on an external Hard drive that was not affected by the fire incident. I don't have any backups of the archivelogs and the redo logs. I have the backup of the controlfile and the spfile (controlfile autobackup was configured to the external disk).

             

            Now our only option is to get a new server, install Oracle database 11g R2 software, and to restore and recover our databases on this new server.

             

            I have been running simulations on a test server but I can't recover my database.

             

            I reach to the point where I can restore the database. Since I don't have the archivelogs nor the redologs, I want to perform an incomplete recovery up to the point where the cumulative incremental level 1 backup allows me. Data loss is acceptable since the data can be re-entered into the database.

             

            How can I recover my database?
            Please I need a solution. There is total loss of business activity.

             

             

            ENKILI@APPSTECH.COM- Tuesday[Customer Problem Description]

             

             

             

             

            Customer Problem Description
            ---------------------------------------------------

             

            Problem Summary
            ---------------------------------------------------
            How to recover a hot backup without archivelogs and online redologs?

             

            Problem Description
            ---------------------------------------------------
            Hi to My Oracle Support Team.

             

            I have a disaster to manage. There was a fire incident in our server room and with physically lost our server containing the Oracle databases. Luckily, I have been doing Cumulative Incremental Level 0 backups Monthly, and Cumulative Incremental Level 1 backups daily on an external Hard drive that was not affected by the fire incident. I don't have any backups of the archivelogs and the redo logs. I have the backup of the controlfile and the spfile (controlfile autobackup was configured to the external disk).

             

            Now our only option is to get a new server, install Oracle database 11g R2 software, and to restore and recover our databases on this new server.

             

            I have been running simulations on a test server but I can't recover my database.

             

            I reach to the point where I can restore the database. Since I don't have the archivelogs nor the redologs, I want to perform an incomplete recovery up to the point where the cumulative incremental level 1 backup allows me. Data loss is acceptable since the data can be re-entered into the database.

             

            How can I recover my database?
            Please I need a solution. There is total loss of business activity.

             

            Error Codes
            ---------------------------------------------------

             


            Problem Category/Subcategory
            ---------------------------------------------------
            High Availability (Recovery Manager(RMAN), Backup & Recovery, Data Guard)/Recovery Manager[RMAN] (Backup, Recovery, Restore, Compatibility, Duplicate DB, Performance, Media Manager Interface, etc)

             

            Uploaded Files
            ---------------------------------------------------

             


            Template Question Responses
            ---------------------------------------------------
            1) ### Impact on Business ###
            The business has stopped. Users can't use the databases anymore.

             

            2) ### Release info of target DB, catalog DB, catalog schema & RMAN executable: ###
            a)-Target database 11.2.0.1 for linux 64 bits
            No catalog database is used. I am using the controlfile to store backup information.
            d)-Rman release 11.2.0.1

             

            3) ### Please provide specific details about the problem the sequence of events leading to the current situation or error. ###
            I want to be able to restore the cumulative incremental level 0 backup on the new server and apply the cumulative incremental level1 backup. I don't have any archivelogs nor online redo logs. I can afford some data loss in this case. I want to perform an incomplete recovery on the new server.

             

            4) ### Error Messages encountered: ###

             

             

            • 18. Re: Restoring Cumulative Incremental level 0 and Cumulative Incremental level 1 backups on a new Host (Archivelogs not available)
              Hemant K Chitale

              I understand Oracle Support's response.

               

              For the simulation, did you check to see if one or more archivelogs were generated between the L0 and L1 backups ?

              Did you check the messages in the alert.log for the RECOVER DATABASE phase ?

               

              Hemant K Chitale


              1 2 Previous Next