Restore and Rename a database from RMAN backupsets

[mc...@hotmail.com]

10.2.0.1 EE on RHEL 4

Anyone know a way of restoring a database to a different database name
from RMAN backupsets.....?

I could do a duplicate database by connecting to the target database
but I want to avoid this.

Or I could restore the backup to the original name on the new server
and then rename it (via a recreation of the controlfile) afterwards.

But I'd like to combine the 2 steps into one, any ideas..?

Thanks

Matt

[tim2...@gmail.com]

I am not sure of your requirements totally but have you looked at the
documentation it pretty much spells everything out step by step.

Creating a Duplicate Databsae on a Local or Remote Host:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb005.htm#i1008537

BEHOLD there is actually a heading:
"Using RMAN DUPLICATE With SET NEWNAME: Example"

Is there a particular part of the procedure you can not or do not want
to do?

Regards
Tim

[mc...@hotmail.com]

> Is there a particular part of the procedure you can not or do not want
> to do?
>

Yeah - I wanted to avoid connecting to the production database. Is it
possible to do a 'duplicate database' without connecting to a TARGET
DB...?

The target and auxilliary are in remote locations, and connectivity
between them is limited.

Matt

[Michael Austin]

Why do you think you will be connecting to the prod db? Take a look at:
http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb001.htm

"You can use the RMAN DUPLICATE command to create a duplicate database
***from backups*** of the target database (primary database) while
retaining the original target database. The duplicate database can be
identical to the target database or contain only a subset of the
tablespaces in the target database. The target site and the duplicate
site can be on separate hosts or on the same host."

[mc...@hotmail.com]

> Why do you think you will be connecting to the prod db? Take a look at:http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/r...
>

Because in order for the DUPLICATE command to work you have to be
connected to the TARGET database 'and' the AUXILLIARY database. This
by definition means that you will connect to our production DB. The
duplicate command will then recover the datafiles from the most recent
RMAN backup and then attempt to apply redo up to the last archivelog
that the production database has archived.

I was interested in knowing if it was possible to achieve this
"without" having to connect to the TARGET database at all.....(for
example if the backup sets are available but connectivity between
duplicate site and target site is not available).

[Frank van Bortel]

mc...@hotmail.com wrote:
>> Why do you think you will be connecting to the prod db? Take a look at:http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/r...
>>
>
> Because in order for the DUPLICATE command to work you have to be
> connected to the TARGET database 'and' the AUXILLIARY database. This
> by definition means that you will connect to our production DB. The
> duplicate command will then recover the datafiles from the most recent
> RMAN backup and then attempt to apply redo up to the last archivelog
> that the production database has archived.

Not if you tell it not to. But it needs to know
what backups actually exist, and those are in the control file
of the... yup! original instance.

>
> I was interested in knowing if it was possible to achieve this
> "without" having to connect to the TARGET database at all.....(for
> example if the backup sets are available but connectivity between
> duplicate site and target site is not available).

Sure you can.

All you have to do is upgrade ( to 11G). You'll at least
want to apply some patches...

FvB