<div>
Cool. &nbsp;I'll give that a shot. &nbsp;Thanks.<br />
<br />
And it is Windows. &nbsp;:(<br />
<br />
<br />
Kent
</div>


<div>
Creating the database service on windows is pretty easy:<br />
<br />
oradim -new -sid newdb -startmode auto -pfile 'c:\oracle\product\10.2.0\<wbr />db_1\dbs\i<wbr />nitnewdb.o<wbr />ra'<br />
<br />
Then you can continue from there as described above.<br />
<br />
Make sure you execute the command using a privileged account etc :) &nbsp;Not everyone can create a service.<br />
<br />
You are probably better off copying the backups from A to B then, if you're on Windows.<br />
<br />
Oracle services accessing remote disks is a pain. &nbsp;I had no end of troubles when I had a test machine set up using a domain account as the service owner that could access my prod backup location. &nbsp;Caused me way more trouble than it was worth so I went back to the default ownership of the service - but then the backups for this particular machine aren't incredibly large and I can copy everything I need over in 30-60 minutes usually.
</div>


<div>
Both methods are valid. &nbsp;One is a pure restore which will restore everything in the same format as the original - pathing, names, DBID ... everything.<br />
<br />
The other is a copy that lets you move things around as you do the restore and change the name etc.<br />
<br />
Depends on the exact requirements of the OP.
</div>


<div>
I'm looking for an easily repeatable process. &nbsp;I've got several dozen instances that I'm going to rehost. &nbsp;They all have the same file structure so all I really need to do is lay the instance over an existing instance and make sure that the new instance name is correct.<br />
<br />
I tried Pepe's solution. &nbsp;The (original) spfile isn't being picked up. &nbsp;The &quot;alter database mount&quot; is failing with &quot;database name {backup name} is not {instance name}&quot;.
</div>


<div>
If all you are doing is moving the databases from one machine to another and everything else is the same (same OS version, same DB version, same disk layout, same everything) you could shut the DB down, move everything over to the new server and start it up.<br />
<br />
I have done that before I seem to recall.<br />
<br />
Depends if you can stand the outage to get it done.
</div>


<div>
An outage isn't a problem.<br />
<br />
I was actually wondering if it would be easier to drop the instance and recreate it.
</div>


<div>
Just wondering how that would help here ? &nbsp;You still need to get the data, users, etc over to the new server.<br />
<br />
Doing a copy via RMAN, or copying the files from an offline backup will move everything that makes up the internals with it.<br />
<br />
If you have to create a new DB and then copy the data, you have issues with recreating all the internals - users, roles, permissions, code, etc.
</div>


<div>
I'm not sure that it would help. &nbsp;And thinking about it some more, it probably doesn't.<br />
<br />
The way our environment is set up, we've never had to do an instance restore from the RMAN backups. &nbsp;Authentication stays with the server so we've used imp/exp or impdp/expdp to move data between servers when we had to.<br />
<br />
Our business model is changing and I'm drawing a blank on the RMAN restore. &nbsp;I haven't seen it in 8 years.
</div>


<div>
Wanted to make sure you have what you needed from the above, Kdo.<br />
<br />
There have been 2 ways presented to you - a duplicate or a restore - both have different ways of handling things.<br />
<br />
The duplicate will assign a new DBID to the copied database, a restore will end up with the same DBID.<br />
<br />
I am more than willing to go through either in detail if needed - want to make sure you have not been left hanging - your last reply doesn't indicate if you need further assistance or not :)
</div>


<div>
Hi guys,<br />
<br />
I wound up choosing door number 3 -- Create a new instance and restore the containers to the instance directories.<br />
<br />
Thanks for the help!<br />
<br />
<br />
Kent
</div>


<div>
<div class="content wysiwyg-content">
I've got an RMAN backup that was taken on server A. &nbsp;I need to restore the backup to an instance on server B, keeping the database name that's already on B. &nbsp;The two servers are in different domains.<br />
<br />
This is Oracle 10g.<br />
<br />
Is there a good writeup or advise on how to do this? &nbsp;It seems that the articles that I've found don't agree on the steps and/or complexity.<br />
<br />
<br />
Thanks,<br />
Kent
</div>
</div>


I've got an RMAN backup that was taken on server A.  I need to restore the backup to an instance on server B, keeping the database name that's already on B.  The two servers are in different domains.

This is Oracle 10g.

Is there a good writeup or advise on how to do this?  It seems that the articles that I've found don't agree on the steps and/or complexity.


Thanks,
Kent

Restore RMAN backup to another server/instance

Oracle is an object-relational database management system. It supports a large number of languages and application development frameworks. Its primary languages are SQL, PL/SQL and Java, but it also includes support for C and C++. Oracle also has its own enterprise modules and application server software.