This discussion is archived
4 Replies Latest reply: Aug 26, 2013 6:11 AM by UserAL1178M RSS

RMAN Hot backup Restore in new Server

Shaik Newbie
Currently Being Moderated

Hi,

 

Our Current Environment:

Source: Current Production

Database: 11.1.0.7

OS: Windows server 2003 R2

 

Target Environemnt:

Database 11.2.0.1

OS:windows server 2008 R2

 

Here my scenario is  need to take RMAN Hot backup in Prod Instance and need to restore in New Server with smae SID which is going to use as Prod instance.

 

Please suggest the detailed steps in order to achive the goal.

Waiting for your thoughts.

 

 

Thanks

Shaik


  • 1. Re: RMAN Hot backup Restore in new Server
    Hemant K Chitale Oracle ACE
    Currently Being Moderated

    You cannot use the DUPLICATE command to duplicate an 11.1 database to an 11.2 environment.

     

    You will have to use the standard BACKUP DATABASE and RESTORE DATABASE  and RECOVER DATABASE (using ArchiveLogs) to first restore the database as an 11.1 database and then upgrade it to 11.2 using catupgrd.sql

     

     

    Hemant K Chitale


  • 2. Re: RMAN Hot backup Restore in new Server
    Jakub 1 Newbie
    Currently Being Moderated

    @HemantKChitale You have absolutely right.

    sorry for bad advice

  • 3. Re: RMAN Hot backup Restore in new Server
    EdStevens Guru
    Currently Being Moderated

    Shaik wrote:

     

    Hi,

     

    Our Current Environment:

    Source: Current Production

    Database: 11.1.0.7

    OS: Windows server 2003 R2

     

    Target Environemnt:

    Database 11.2.0.1

    OS:windows server 2008 R2

     

    Here my scenario is  need to take RMAN Hot backup in Prod Instance and need to restore in New Server with smae SID which is going to use as Prod instance.

     

    Please suggest the detailed steps in order to achive the goal.

    Waiting for your thoughts.

     

     

    Thanks

    Shaik

     

     

    "restore in New Server with smae SID which is going to use as Prod instance"

     

    I would caution against that.  Having a test and a prod database with the same names is a catastrophe looking for an opportunity to happen.  

    Why do you think you need for the prod and test databases to be named the same?

  • 4. Re: RMAN Hot backup Restore in new Server
    UserAL1178M Explorer
    Currently Being Moderated

    RMAN can make it easy to restore a database to a new host.

     

    Notice that: Using RMAN RESTORE and RECOVER commands to move a database permanently to another host, will keep the original database identifier (DBID) and will therefore cause a conflict in the RMAN repository, because the restored database with the same DBID will be considered the current target database.

     

    Below you may find the steps:

     

    Preparing the New Host

    1. Record the DBID of the source database.
    2. Copy the initialization parameter file from the source database to the new host.
    3. Make sure that all source database backups are available to the new host. Do not connect to the recovery catalog.

     

    Restoring and Recovering on the New Host

    1. Configure environment variables on the new host.
    2. Connect to the new target database with NOCATALOG.
    3. Set the DBID.
    4. Start the instance with NOMOUNT.
    5. Restore the SPFILE from backup.
    6. Shut down the new instance.
    7. Edit the PFILE.
    8. Start the instance with NOMOUNT (again).
    9. Create an RMAN RUN block to restore the control file.
    10. Create an RMAN RUN block to restore and recover the database.
    11. Open the database with RESETLOGS.

     

    Regards,

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points