Re: Recreate Redologs on different host

Hi again Stalin!

I hadn't seen this message of yours before posting my question about changing the redo log locations after incomplete recovery yesterday ;-)

Regarding your question: with RMAN, log_file_name_convert (as well as db_file_name_convert) are supported only for duplication (not for restore & recovery) - their use with standby databases is another matter I haven't dealt with for a long time.

db_file_name_convert could avoid the use of "set newname"/"switch datafile" during restore/recovery... :-(

Jerome

On 8/25/05, Stalin <stalinsk_at_gmail.com> wrote:
> I'd been testing incomplete recoveries with different scenario's using
> RMAN and everything was working out fine until today where i hit a
> snag on recreating redologs on different host. I was testing a typical
> DR scenario where the production database machine is hosed for some
> reasons and i'd to restore the database up to the recent logs archived
> on to different host.
>
> Location of controlfiles, redologs, datafiles and archivelogs are
> different from the production machine. Below are the steps i followed
> leaving out the obvious ones.
>
> -- set dbid, restored spfile. modify relevant parameters like
> control_files, _xdump, log_archive_dest etc with new location. Also
> included log_file_name_convert for redologs.
> -- restore controlfile, mount the database
> run {
> -- set newname for all datafiles
> -- set until sequence to latest_archived+1
> -- restore database
> -- switch datafile all
> -- recover database
> }
> -- media recovery complete.
> -- open database with resetlogs -- error's with ORA-00344: unable to
> re-create online log.
>
> For some reason the location stills maps to the path where production
> logs were placed. Shouldn't log_file_name_convert change the
> production location to new one i gave in spfile.
>
> Feedback appreciated.
>
> Regards,
> Stalin
>
> Ver: 9205
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l