DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: Restoring the Control File When Using a Recovery Catalog

  1. #1
    Join Date
    Jul 2006
    Posts
    195

    Restoring the Control File When Using a Recovery Catalog

    I am looking at the following link

    http://download.oracle.com/docs/cd/B...1.htm#RCMRF149

    And see this example (see below). If your restoring a control file from a backup dont you need to open the DB with resetlogs option since you will be out of sync. Is this documentation wrong or am I missing something?


    RUN
    { # SET DBID is not necessary when connected to a recovery catalog
    STARTUP FORCE NOMOUNT;
    RESTORE CONTROLFILE;
    ALTER DATABASE MOUNT;
    }

    When I issue this statement after the control files are restored I get the
    following error:

    SQL> alter database open RESETLOGS;
    alter database open RESETLOGS
    *
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/data/aux/system01.dbf'


    Can somebody explain what is missing in the above example for this work.

    Thanks

  2. #2
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    obviously the control file you restored from backup will have different SCN number (old) than the data files (recent). That's the reason you are prompted for recovery.

    you need to re-create the control file and open with RESETLOGS or
    you need to restore the whole database from the same backup and recover.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  3. #3
    Join Date
    Jul 2006
    Posts
    195
    As you can see that is why I tried doing opening the database with resetlogs optiomn and I received the errror.

    I'm looking for the missing step, should this have been done within the RMAN script?

  4. #4
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    can be do with RMAN.

    you need to add RESTORE DATABASE command also in the block. After the DB restore you can open with RESETLOGS. Because at this point of time SCN will be in syc for control file as well as for data files.

    before attempting restore please make sure of the paths (if i remember correct you have already done this earlier).

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

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