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
Our Current Environment:
Source: Current Production
OS: Windows server 2003 R2
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.
"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?
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
- Record the DBID of the source database.
- Copy the initialization parameter file from the source database to the new host.
- 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
- Configure environment variables on the new host.
- Connect to the new target database with NOCATALOG.
- Set the DBID.
- Start the instance with NOMOUNT.
- Restore the SPFILE from backup.
- Shut down the new instance.
- Edit the PFILE.
- Start the instance with NOMOUNT (again).
- Create an RMAN RUN block to restore the control file.
- Create an RMAN RUN block to restore and recover the database.
- Open the database with RESETLOGS.