RMAN Point in Time Recovery: ORA-01194: file 1 needs more recovery to be consistent
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: RMAN Point in Time Recovery: ORA-01194: file 1 needs more recovery to be consistent

  1. #1
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    684

    Question RMAN Point in Time Recovery: ORA-01194: file 1 needs more recovery to be consistent

    trace.txtHi,
    I am restring database to a point in time. I have all backup files, however I keep getting error:

    Command:

    run{
    ALLOCATE CHANNEL c1 DEVICE TYPE disk;
    ALLOCATE CHANNEL c2 DEVICE TYPE disk;
    ALLOCATE CHANNEL c3 DEVICE TYPE disk;
    ALLOCATE CHANNEL c4 DEVICE TYPE disk;
    set until time "to_date('01/01/2014 05:00:00' , 'dd/mm/yyyy hh24:mi:ss')";
    RESTORE DATAFILE 1;
    recover database SKIP TABLESPACE WORKBENCH_DATA;
    }

    Output:

    ………
    Executing: alter database datafile 4 offline
    Executing: alter database datafile 72 offline
    Executing: alter database datafile 73 offline
    Executing: alter database datafile 38 offline
    Executing: alter database datafile 74 offline
    Executing: alter database datafile 75 offline
    starting media recovery

    archived log for thread 1 with sequence 1813 is already on disk as file /u10/FPESSP01_SITE2/datafile/1_1813_829250679.arch
    archived log for thread 1 with sequence 1814 is already on disk as file /u10/FPESSP01_SITE2/datafile/1_1814_829250679.arch
    archived log file name=/u10/FPESSP01_SITE2/datafile/1_1813_829250679.arch thread=1 sequence=1813
    archived log file name=/u10/FPESSP01_SITE2/datafile/1_1814_829250679.arch thread=1 sequence=1814
    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: '/u10/FPESSP01_SITE2/datafile/1.dbf'

    media recovery complete, elapsed time: 00:00:10
    Finished recover at 02-JAN-14
    released channel: c1
    released channel: c2
    released channel: c3
    released channel: c4

    RMAN>

    Directory has the following ARCH files, but it does not use them:


    oracle@chzrhkorap04:/u10/FPESSP01_SITE2/datafile/ [SPHPRD1] ls *.arch
    1_1808_829250679.arch 1_1812_829250679.arch 1_1816_829250679.arch 1_1820_829250679.arch 1_1824_829250679.arch
    1_1809_829250679.arch 1_1813_829250679.arch 1_1817_829250679.arch 1_1821_829250679.arch 1_1825_829250679.arch
    1_1810_829250679.arch 1_1814_829250679.arch 1_1818_829250679.arch 1_1822_829250679.arch 1_1826_829250679.arch
    1_1811_829250679.arch 1_1815_829250679.arch 1_1819_829250679.arch 1_1823_829250679.arch


    The following arch file is not corrupted:

    RMAN> catalog start with '/u10/FPESSP01_SITE2/datafile/temp/';

    searching for all files that match the pattern /u10/FPESSP01_SITE2/datafile/temp/

    List of Files Unknown to the Database
    =====================================
    File Name: /u10/FPESSP01_SITE2/datafile/temp/1_1815_829250679.arch

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

    List of Cataloged Files
    =======================
    File Name: /u10/FPESSP01_SITE2/datafile/temp/1_1815_829250679.arch



    Attached file has an some errors.
    Any advice will be very much appreciated.
    Last edited by kgb; 01-02-2014 at 09:26 AM.
    Best wishes!
    Dmitri

  2. #2
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,001
    Why are you doing "recover database SKIP TABLESPACE WORKBENCH_DATA;"? If you can't restore that table space, then you
    need to take it offline before trying to open the database. You can also try "recover database using backup control file until cancel;"
    First apply as many logs as you can, then run the command with cancel rather than auto or a log file.

    But to do a partial recovery you have to let the database know that it does not need to apply redo to the workbench_Data table space.
    If you don't recover that table space, then you need to offline drop the table space and data files, thus losing any data in that table space.
    this space intentionally left blank

  3. #3
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    684
    Hello, thank you for your reply. Actually this is a part of the script ... I reduced it after the main one produced the same error. SKIP option works like a charm the same script has been tested and proven to work. I use backup of the control file which was made at 4:59am, and point in time recovery is 5:00am. Also some of the data files were restored from the backup of the Standby Database.

    Unfortunately I need db to be restored up to 5:00 am

    test1.txt
    Best wishes!
    Dmitri

  4. #4
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    684
    I just discovered that restore to any time prior 05:25 am was failing, it looks like control file which was created at 4:59 could not be used to 5:00am restore ... Strange ... I checked time and time is identical on both machines.
    Best wishes!
    Dmitri

  5. #5
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,001
    You are always going to have an issue if the control file is newer that the most recent archive log that you apply.
    You might want to check and see if you have an older control file to restore first, then restore and recover the database.
    this space intentionally left blank

  6. #6
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    684
    Thank you for valuable notes!
    Best wishes!
    Dmitri

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width