Re: RMAN DB recover re-applying archive log *URGENT*

You could probably have saved yourself some trouble by perusing the manual - think of it as the Hitchhikers Guide to the Database. (Don't Panic)

>From the recovery manual:

(Raj, are you there? Notice the use of Perl in the docs. ;)

Uncataloging and Cataloging Archived Logs: Example

In this example, you first move all archived logs to a temporary directory and then uncatalog them:

HOST 'mv $ORACLE_HOME/oradata/trgt/arch/* /tmp/arch'; CHANGE COPY OF ARCHIVELOG ALL UNCATALOG; EXIT;  From the UNIX command shell you use Perl to create a command file that contains a CATALOG command for each archived log:

% perl5 -e '@files=</tmp/arch/*>; foreach (@files) \ ? {print "CATALOG ARCHIVELOG '$_'\;\n";}' > $HOME/rman.cmd

 Finally, you start RMAN and run the command file to catalog the relocated logs:

% rman TARGET / @$HOME/rman.cmd

On 7/12/05, rjsearle_at_gmail.com <rjsearle_at_gmail.com> wrote:
>
> Hi list,
> we are recovering a database from an old backup. the most recent backup
> failed but after we got the archived logs from the tapes.
> We also restored the RMAN catalog from the earlier backup.
> So we began recovering the database and it stopped as we had archived
> logs that were not known to RMAN.
> We have restored the latest version of the RMAN catalog and are about to
> recommence recovering the DB. I think RMAN will try to "reapply" the older
> archived logs. Is this correct? will this work?
> Thanks
> Russell
>

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

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